Migrating Your Monitors from UptimeRobot in 60 Seconds

Switching uptime monitoring providers usually fails at the same hurdle: getting your monitors out. UptimeRobot has no configuration export - the CSV button covers logs and incidents, not your monitor list. So most people facing a migration open two browser tabs and start re-typing URLs.

You don't have to. Vantaj imports your entire UptimeRobot account with a single read-only API key - every monitor type, including heartbeats - in about the time it takes to read this paragraph. Here's the whole flow:

Step 1: Create a read-only API key (20 seconds)

In UptimeRobot, open Integrations & API from the dashboard sidebar. Under API, create a Read-Only API Key.

Two things worth knowing:

• It's available on the free plan. UptimeRobot includes API access on every tier, so there's no paywall between you and your own data.
• Read-only means read-only. The key can list your monitors but can't modify or delete anything. Your UptimeRobot account is untouched by the migration - you can keep it running in parallel as long as you like.

Step 2: Paste it into Vantaj (10 seconds)

In Vantaj, go to Settings → Import Monitors and choose Quick import from UptimeRobot. Paste the key and click Fetch monitors.

Vantaj calls the UptimeRobot API on your behalf, pages through your full monitor list, and shows everything it found. The key is used for that one request and never stored.

Step 3: Review and import (30 seconds)

Every importable monitor is pre-selected. The preview shows what each one becomes:

The details come over too - and the edge cases are handled the way you'd hope:

• Keyword logic is translated correctly. UptimeRobot's "alert when keyword exists" becomes Vantaj's response must not contain; "alert when not exists" becomes must contain. Your error-page detection keeps working without you thinking about it.
• Check intervals are snapped to the nearest Vantaj interval, respecting your plan's minimum.
• HTTP basic auth credentials carry over.
• Paused monitors stay paused.
• Duplicates are caught. Anything already monitored in Vantaj (matched by URL) is flagged and deselected, so re-running the import never creates copies.

Click Import, and checks start immediately from multiple regions.

The two things that don't migrate

Honesty section. Two things stay behind, for reasons outside anyone's importer:

Historical uptime data. UptimeRobot's API doesn't expose history in an importable form. Your Vantaj graphs start at import time. If unbroken records matter to you, keep the UptimeRobot account alive (it's free) as a read-only archive, or run both in parallel through the transition.

Alert contacts. Notification channels work too differently across providers to map automatically. In Vantaj you set up channels once - Slack, PagerDuty, Telegram, webhooks, email - under Alerts & Notifications, and they apply to every monitor, imported or not. For most teams this is a five-minute job.

One follow-up for heartbeat users

Imported heartbeat monitors get a new Vantaj ping URL. Your cron jobs are still pinging UptimeRobot until you update them - swap the URL in your crontab or CI config, and consider running both for a day so there's no gap in dead-man's-switch coverage.

Why we built this

Nobody in the uptime monitoring space offers a real self-serve importer. The competition's answer to "how do I migrate?" ranges from "email us your monitor list" to "here's our Terraform provider." We think switching tools should take a minute, not an afternoon - and that the same courtesy should apply in both directions, which is why the importer asks for a read-only key and leaves your old account intact.

Migrating from Pingdom, Better Stack, StatusCake, or somewhere else? Tell us via Settings → Share Feedback - UptimeRobot is the first source, not the last.

Ready to try it? Create a free Vantaj account - 20 monitors free, no credit card - and see the full import guide in the docs.