Migrate
Move from UptimeRobot to TigerUp
TigerUp's importer reads your UptimeRobot account with a read-only API key, shows what each monitor and alert contact becomes (or why it can't come across), and creates only what you choose.
Four steps
- Create a TigerUp account and organization. The free plan imports up to 5 monitors; upgrade to Pro for 50. Monitors and channels beyond your plan's limits are skipped and listed, so you can upgrade and import the rest.
- Copy UptimeRobot's read-only API key from Integrations & API → API. It can read your monitors and contacts and change nothing.
- Open Monitors → Import from UptimeRobot as an admin or owner, paste the key and review the preview. Nothing is created yet.
- Choose what to import and confirm. Importing again later skips anything already imported.
The key is sent to UptimeRobot only, used for the import and dropped: TigerUp never stores or logs it.
After the import
- HTTPS monitors get SSL certificate expiry alerts, and monitors on a domain get domain expiry alerts, with no setup. Turn them off per monitor if you don't want them.
- Secret header values, such as API keys and bearer tokens, are encrypted at rest and never shown again.
- Checks run from one region.
- Status pages aren't imported; create them in TigerUp and add the imported monitors.
What comes across
- HTTP(s) monitors
- HTTP monitors with the same URL and method (GET, HEAD, POST, PUT, PATCH or DELETE), custom headers and raw POST body. Paused monitors stay paused.
- Keyword monitors
- Keyword monitors. UptimeRobot says when to alert, TigerUp says when the monitor is up, so “alert when the keyword exists” becomes “up when the page doesn't contain it”, and the reverse. Case sensitivity is kept.
- Port monitors
- TCP monitors on the same host and port, including the standard ports for HTTP, HTTPS, FTP, SMTP, POP3 and IMAP.
- Check intervals
- The nearest of 30 seconds, 1, 2, 5, 10, 15, 30 or 60 minutes, raised to your plan's minimum if UptimeRobot checked more often. The preview shows each change.
- Email, Slack and webhook alert contacts
- Notification channels of the same kind. Email channels need a verified TigerUp email address. Webhooks get a new signing secret.
What's skipped, with the reason shown in the preview
- Ping and heartbeat monitors, which TigerUp doesn't run.
- Monitors that send OPTIONS requests or key-value POST data. Recreate a key-value POST with a raw body.
- Monitors that use HTTP authentication: the importer never reads the password. Recreate them with an Authorization header, which TigerUp encrypts at rest.
- Monitors whose URL or host points at a private or local address.
- Alert contact types other than email, Slack and webhooks, such as SMS or PagerDuty.
- Status pages, and which contacts alert for which monitor: TigerUp channels alert for every monitor in the organization.
Comparing first? TigerUp vs UptimeRobot
UptimeRobot, Better Stack and Pingdom are trademarks of their respective owners. TigerUp is not affiliated with, endorsed by or sponsored by them. Competitor details come from their public pricing pages and documentation on the dates shown, and may have changed since.