Import from UptimeRobot or Better Stack
Moving from UptimeRobot or Better Stack? Paste an API key and Heedery shows what it can bring over. You pick what to import; nothing changes on the other side.
On this page
Run an import
- 1.Go to Settings then Import and pick the service under Import from.
- 2.Paste the key. For UptimeRobot, the read-only API key is enough. For Better Stack, use a team’s Uptime API token.
- 3.Press Preview the import. Untick anything you do not want.
- 4.Press Import. The summary says what was created and what was skipped, and why.

Owners and admins can import. The key is not stored or logged. Running it again is safe: monitors you already have show as Already monitored here.
What comes over
UptimeRobot · Better Stack
- Monitors
- HTTP, keyword, API, ping, port, UDP, DNS and heartbeats from UptimeRobot; monitors and heartbeats from Better Stack. Paused ones stay paused.
- Alert contacts
- From UptimeRobot: email addresses become extra alert recipients on the same monitors; Slack, Teams, Discord, webhooks and Zapier become channels; Telegram is connected again here, in a click. Better Stack’s API does not share them.
- Status pages
- From both, only the ones you tick. Each monitor goes on one page; a monitor on none of them stays off every page here. Custom domains and logos stay behind.
- Not imported
- UptimeRobot visual comparisons, SMS, voice and app contacts, and maintenance windows; Better Stack Playwright checks. Rebuild a Playwright check as a browser flow.
Your plan’s limits
The preview applies your plan before anything is created:
- Intervals shorter than your plan allows are raised to its minimum.
- Monitors past your plan’s count are marked as over the limit.
- Channels your plan does not include are marked.
- Password-protected pages become private only on a plan with private pages. Otherwise the preview warns they would be public.
NoteAfter the import, check the alert settings of a few sites. See Alerts and channels.
Still stuck? Write to us.