Import from UptimeRobot
Vantaj can import your entire UptimeRobot account - HTTP(s), keyword, ping, port, and heartbeat monitors - with a single read-only API key. No CSV exports, no re-typing URLs, no downtime in your coverage.
Import from UptimeRobot
HTTP, keyword, ping, port, and heartbeat monitors are all supported.
- In UptimeRobot, open Integrations & API
- Create a Read-Only API Key (available on every plan, including free)
- Paste it below - it's used once to read your monitor list, and never stored
Before you start
You need an UptimeRobot Read-Only API Key. It's available on every UptimeRobot plan, including the free one:
- Log in to UptimeRobot and open Integrations & API from the dashboard
- Under API, click Create API key and choose Read-Only API Key
- Copy the key (it starts with
ur)
A read-only key can only list your monitors - it can't modify or delete anything in your UptimeRobot account. Vantaj uses it once to read your monitor list and never stores it.
Running the import
- In Vantaj, go to Settings → Import Monitors and pick Quick import from UptimeRobot
- Paste your API key and click Fetch monitors
- Review the list - everything importable is selected by default. Monitors that already exist in Vantaj (matched by URL) are flagged and deselected so you don't create duplicates
- Click Import - monitors are created and checks start immediately
Monitors that were paused in UptimeRobot are imported as paused in Vantaj. Everything is imported into your currently active project.
What carries over
| UptimeRobot | Vantaj | Notes |
|---|---|---|
| HTTP(s) monitor | HTTP(s) monitor | URL and name carry over as-is |
| Keyword monitor | HTTP(s) monitor with a response assertion | "Alert when exists" becomes must not contain; "alert when not exists" becomes must contain |
| Ping monitor | Ping (ICMP) monitor | |
| Port monitor | Port (TCP) monitor | Well-known ports (HTTPS, FTP, SMTP, POP3, IMAP) and custom ports are both mapped |
| Heartbeat monitor | Heartbeat | See the note below about ping URLs |
| Check interval | Check interval | Snapped to the nearest Vantaj interval, respecting your plan's minimum |
| HTTP basic auth | HTTP basic auth | Username and password carry over when your key exposes them |
| Paused state | Paused state | Paused monitors stay paused |
What doesn't carry over
- Historical uptime data - UptimeRobot's API doesn't provide it in an importable form. Your Vantaj history starts at import time.
- Alert contacts - notification channels work differently across providers. Set up your channels once under Alerts & Notifications and they apply to all monitors, imported or not.
- Status pages - rebuild these in a few clicks under Status Pages.
Heartbeats: update your cron jobs
Imported heartbeat monitors get a new Vantaj ping URL. Your cron jobs and background workers are still pinging UptimeRobot until you update them:
- Open Heartbeats in Vantaj and copy each monitor's ping URL
- Replace the old UptimeRobot URL in your crontab, CI config, or scheduler
- Keep both providers running in parallel for a day if you want zero gaps
Plan limits
Imports count toward your plan's monitor limit, shared across uptime monitors, heartbeats, and domains. If your selection exceeds the remaining allowance, the importer tells you before anything is created - deselect a few monitors or upgrade your plan first.
Check intervals below your plan's minimum are raised to the closest allowed value (e.g. a 60-second interval becomes 5 minutes on the free plan).
Migrating from another provider?
UptimeRobot is the first source with one-click import - more are on the way. If you're moving from Pingdom, Better Stack, StatusCake, or anywhere else, tell us via Settings → Share Feedback and we'll prioritise it. In the meantime, the REST API makes scripted bulk imports straightforward.