Importing monitors from UptimeRobot, Pingdom or CSV
The import wizard (Settings → Import Monitors, or the Import button on the Monitors page) copies your existing checks over from UptimeRobot or Pingdom — or from any other tool via CSV. Every import follows the same three steps:
- Connect — paste a read-only API key/token, or paste/upload a CSV.
- Preview — we fetch your monitors server-side and show a table of exactly what will be created: name, type, target, interval, and whether each row is importable (with the reason when it isn't).
- Import — tick the rows you want, choose a project, confirm you own or are authorized to monitor every selected target, and import.
Your API key is used once, server-side, to read the monitor list. It is never stored and never logged. Imported monitors start in Pending and run their first check on the next scheduler tick.
Importing from UptimeRobot
Grab your read-only Main API key from UptimeRobot → My Settings → API Settings (the read-only key is enough — we never write to your account).
What maps to what:
| UptimeRobot type | Becomes | Notes |
|---|---|---|
| HTTP(s) | Uptime | Expects a 2xx/3xx status, GET, same URL. |
| Keyword | Keyword | The alert direction is translated: UptimeRobot's "alert when keyword exists" becomes keyword should be absent, and "alert when keyword not exists" becomes keyword should be present. Case sensitivity carries over. |
| Port | Port | Well-known port types (HTTP, HTTPS, FTP, SMTP, POP3, IMAP) map to their standard ports; custom ports carry over. |
| Heartbeat | Heartbeat | A new ping URL is issued — vendor ping URLs can't be carried over. The new URL is shown on the import summary; update each cron job to call it. |
| Ping | Skipped | CompleteStatus doesn't run ICMP ping checks yet. Recreate these as uptime (HTTP) or port checks. |
Importing from Pingdom
Create an API token in Pingdom under Settings → Pingdom API (read access is enough).
| Pingdom type | Becomes | Notes |
|---|---|---|
| HTTP | Uptime | Scheme, host, port and path are rebuilt from the check's settings. |
| HTTP with "should contain" | Keyword | Should contain becomes keyword should be present; should not contain becomes keyword should be absent. |
| TCP | Port | Host and port carry over. |
| DNS | Skipped | Pingdom DNS checks assert an expected IP; CompleteStatus DNS monitors watch for record changes against a baseline instead. Recreate manually as a DNS change monitor if that fits your intent. |
| Ping | Skipped | No ICMP checks yet — recreate as uptime or port checks. |
| Others (SMTP, POP3, IMAP, UDP, transaction) | Skipped | No CompleteStatus equivalent yet. |
Importing from CSV (any other tool)
Export from your current tool and shape the rows as:
name,type,target,interval
Homepage,uptime,https://example.com,300
Cert,cert,example.com,86400
Postgres,port,db.example.com:5432,60
Nightly backup,heartbeat,backup-job,86400
- type — one of
uptime(aliaseshttp,https),cert(aliasssl),port(aliastcp, target must behost:port),dns,domain,headers,heartbeat. - interval — seconds; anything between our options rounds up to the next available interval.
- A header row is detected and skipped; quoted fields work.
keywordrows are skipped (the CSV has no column for the keyword itself) — add those manually.
Intervals, plan limits and ownership
- Intervals round up. If your old tool checked every 2 minutes, the import picks every 5 — never faster than what you had. Intervals below your plan's minimum are raised to the plan minimum.
- Plan limits are enforced. If you select more monitors than your plan has room for, the wizard tells you how many fit ("Only X of Y selected monitors fit your plan") and nothing is imported until you deselect some or upgrade.
- Names stay unique. Monitor names are unique within your organization; a colliding import is suffixed — "My Site" becomes "My Site (2)".
- Ownership attestation. The single checkbox on the preview step covers every selected row and is stored per monitor with a timestamp and your user, the same as creating a monitor by hand.
After the import
Imported monitors appear on the Monitors page grouped by site, start checking within a minute, and can be edited like any hand-made monitor. Remember to add alert channels and attach alert rules — alert routing is not imported from the other tool.