How to Migrate From UptimeRobot to PingBase

Most teams outgrow UptimeRobot the same way: you hit the 5-minute check interval limit, the status page branding is locked behind a paid tier, or you just need more than basic HTTP monitoring. The migration itself is painless — this guide walks through every step.

---

Before you start: export from UptimeRobot

Pull a full export before touching anything:

1. Log into UptimeRobot and go to My Settings
2. Find Export Data and download the CSV
3. Open it and note every URL, check type, keyword condition, and alert contact

This becomes your migration checklist. Don't start recreating things until you have this in hand.

---

Step 1: Create your PingBase account

1. Go to app.pingba.se/register
2. Sign up with email or GitHub — no credit card required
3. Verify your email and log in

The free plan covers 5 monitors with 1-minute checks. If you have more monitors in UptimeRobot, you'll want to plan which ones are most critical to migrate first.

---

Step 2: Recreate your monitors

PingBase supports bulk import via CSV. For larger setups:

1. In PingBase, go to Monitors → Import
2. Download the import template
3. Map your UptimeRobot export data to the PingBase columns
4. Upload and import

For smaller setups (under 10 monitors), adding them manually is often faster. Here's how UptimeRobot fields map to PingBase:

For keyword monitors (where UptimeRobot checks that a specific string appears or doesn't appear on the page), use PingBase's response body contains / response body does not contain fields in the HTTP monitor settings.

---

Step 3: Set up alert channels

Go to Settings → Alert Channels and recreate each integration:

Email

Add each email address as a separate alert channel. You can assign different channels to different monitors — useful if one person owns the API and another owns the payments flow.

Slack

Create an Incoming Webhook in your Slack workspace, copy the URL, and paste it into PingBase's Slack channel setup. Send a test to confirm it lands in the right channel.

Telegram

Go to Alert Channels → Add Telegram. The setup is identical to UptimeRobot's Telegram integration — create a bot via BotFather, get your chat ID, and paste both into PingBase.

Webhooks

If you had UptimeRobot webhooks pointing at custom systems, add them as webhook channels in PingBase. The payload format is slightly different — see the PingBase API docs for the exact schema.

Once your channels are ready, go to each monitor and assign which channels should notify for that monitor.

---

Step 4: Recreate your status page

1. Go to Status Pages → Create Status Page
2. Name it and set the slug (e.g., status.yourcompany.com)
3. Add monitors and optionally group them by category (Website, API, Infrastructure)
4. Set visibility: public or private (password-protected)

To point your own domain at it, add a CNAME in your DNS:

status  CNAME  pages.pingba.se

SSL is provisioned automatically within a couple of minutes. Unlike UptimeRobot, custom domains are available on all PingBase plans including free.

---

Step 5: Invite your team

If you have team members in UptimeRobot, add them under Settings → Team Members. Enter their email addresses — they'll receive an invite to join your workspace with access to all monitors and the status page.

---

Step 6: Run both in parallel for 48 hours

Before canceling UptimeRobot, run both services side by side for two days:

• Verify PingBase is checking all the right URLs at the right intervals
• Trigger a test alert from each monitor to confirm channels are working
• Check that your status page is displaying correctly
• Cross-reference the monitor lists to make sure nothing was missed

After 48 hours without issues, update any internal documentation that links to your UptimeRobot status page, then cancel your UptimeRobot subscription.

---

What you gain in the switch