Migrate from Better Stack to Hyperping

Your Better Stack setup likely mixes monitors, heartbeats, on-call rotations, and a status page, and each piece has a direct home in Hyperping. Follow this guide to rebuild them in order, run both tools in parallel, and switch off only once the alerts match.

Concept mapping

Better Stack and Hyperping share most concepts, often under the same name. Use this table to translate your current setup before you start.

Migration steps

1. Inventory your Better Stack setup

   List your monitors with URL, frequency, and regions, and export them as CSV or through the API. Note your heartbeats with their expected periods and grace times.

   Write down each on-call calendar and escalation policy as it exists today: you'll mirror them in a later step.

2. Recreate your monitors in Hyperping

   For fewer than 20 monitors, recreating them by hand in the dashboard is usually the fastest path. See Create a monitor.

   For a larger fleet, loop over your exported list with the API, or manage everything as code with the Terraform provider:

   cURLTerraform

   Copy

   curl -X POST https://api.hyperping.io/v1/monitors \
     -H "Authorization: Bearer ${API_TOKEN}" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Website",
       "url": "https://acme.com",
       "protocol": "http",
       "check_frequency": 30,
       "regions": ["paris", "frankfurt", "amsterdam", "london"]
     }'

   Response201 Created

   {
     "name": "Website",
     "url": "https://acme.com",
     "paused": false,
     "regions": ["paris", "frankfurt", "amsterdam", "london"],
     "http_method": "GET",
     "check_frequency": 30,
     "protocol": "http",
     "follow_redirects": true,
     "expected_status_code": "2xx",
     "uuid": "mon_3GhAQMYGEQuyUH",
     "status": "up",
     "alerts_wait": 0
   }

   Recreate each heartbeat as a healthcheck: your job gets a ping URL, and Hyperping alerts you when the ping stops arriving on schedule.

3. Rebuild on-call and escalations

   Recreate your rotations as on-call schedules, then wire them into escalation policies that define who gets paged and how long to wait before escalating.

   Connect your notification channels for email, SMS, Slack, webhooks, and more.

4. Run both tools in parallel

   Keep Better Stack running alongside Hyperping for a few days. Every incident should now be caught twice.

   Compare the alerts on both sides: a difference points to a missed monitor, a wrong interval, or a threshold worth tuning.

5. Point your status page and switch off Better Stack

   Publish your Hyperping status page, move your custom domain, and invite your subscribers.

   Once the parallel run is clean, pause your Better Stack monitors and close the account.

What you'll gain

• One focused tool: monitoring, status pages, on-call schedules, and escalation policies in a single product built around uptime.
• 18 monitoring regions: checks run from up to 18 locations worldwide, and failures are confirmed from other regions before an alert fires.
• Flat pricing: plans are based on monitors, not seats, so on-call rotations don't grow your bill.

Migration resources

Next steps