What moves over
- MonitorsAvailableImport your monitors with the import wizard (Settings → Import from another tool): connect UptimeRobot with an API key or upload its CSV export, connect Better Stack or Pingdom with an API token, or upload a Freshping CSV or JSON export. You see a preview before anything is created.
- On-call schedules and escalationsAvailableImport Opsgenie schedules (rotations and overrides), escalation policies and heartbeats with an API key, after a preview. Heartbeats get new SutramX ping URLs to swap into your jobs; phone numbers come across only if you tick them, and are only used after each person confirms by email. Integrations, routing rules and alert policies are listed in a follow-up checklist with their SutramX equivalents. On-call schedules are included on Pro.
- Alert channelsAvailableEmail, Slack, Microsoft Teams, Discord, Telegram, Google Chat, Mattermost, webhooks, PagerDuty and Opsgenie, so you can keep paging through Opsgenie while you move.
- Status pagesAvailableRecreate your status page, check it, then point your status domain at SutramX.
What each importer brings over
- UptimeRobotConnect a read-only API key, or upload the CSV export of your monitors. Both bring your monitors; only the API key also brings the alert contact emails, because the CSV export does not include them.
- FreshpingUpload the CSV or JSON export of your checks. Monitors come across with the alert emails listed in the file.
- Better StackConnect an Uptime API token (a team token with read access is enough). Monitors and heartbeats come across; Better Stack's API does not expose alert addresses, so no contacts are imported.
- PingdomConnect an API token with read access. Checks come across with their alerting contact emails.
HTTP and keyword checks become HTTP monitors (with a required or forbidden keyword), HTTP checks that use POST, PUT, PATCH, DELETE or a request body become API monitors, and ping, TCP port, UDP and heartbeat checks map to their SutramX equivalents. SMTP, POP3 and IMAP checks become port checks on the same port. Names, URLs, timeouts, expected status codes, headers and paused state are kept, and each monitor is tagged with the tool it came from. DNS checks, and browser or transaction checks, are not imported; the preview tells you which checks those are so you can recreate them by hand.
Preview first, no duplicates
Every import starts with a preview of exactly what will be created, and nothing changes until you confirm. Each check is marked Will import, Already imported, Already exists, Not supported (with the reason) or Over plan limit, and you can untick any check you do not want. The preview also notes every adjustment, for example an interval raised to the fastest your plan allows. A preview is valid for 24 hours, and export files can be up to 2 MB.
Email contacts linked to a check become that monitor's alert recipients (up to 20 per monitor), and each new address must confirm once before it receives alerts. SMS, Slack and webhook contacts are listed but not imported: Slack needs a fresh authorisation and webhooks need to be verified, so you add them again in SutramX. The full mapping is in the import guide.
A safe switch, step by step
- Create a free SutramX account and add your most important monitors first.
- Connect your alert channels and, if you used Opsgenie, import your schedules, escalation policies and heartbeats, and point your heartbeat jobs at their new URLs.
- Run SutramX alongside your current tool for a week and compare what each one catches.
- Move your status page domain, then switch off the old tool.
Coming from a specific tool?
Step-by-step import guides: switch from Freshping and switch from UptimeRobot.
- Moving from UptimeRobot
- Moving from Freshping
- Moving from Better Stack
- Moving from Pingdom
- Moving from Opsgenie
Frequently asked questions
Does importing change anything in my old monitoring tool?
No. SutramX only reads your checks. An API key or token is used once to read them and is not stored, so your old tool keeps running exactly as before while you compare the two.
What happens if I run the import twice?
Nothing is duplicated. Checks you imported before show as Already imported and are left unchanged, and a check whose URL, or host and port, already has a monitor in the workspace shows as Already exists. Only new checks are created.
Do imported monitors count towards my plan?
Yes. They use your plan's monitor slots, intervals are raised to your plan's fastest allowed interval, and locations are matched to the ones your plan includes. Checks that do not fit are marked Over plan limit in the preview; upgrade and preview again to bring in the rest.
Will my cron job heartbeats keep working?
Heartbeats are imported, but each one gets a new SutramX heartbeat URL. Update your jobs to call the new URL; SutramX does not watch the old tool's URL.
Can I import on-call schedules from Opsgenie?
Yes. Opsgenie schedules, rotations and escalation policies can be imported and reviewed before they go live.
Large migration, or need a hand? Contact us with your current setup and we will help you move it.