Migrating from Another Provider

If you’re switching from another status page or uptime-monitoring product, you don’t have to recreate everything by hand. The import wizard pulls your existing components, incidents, maintenance history, and monitors in from your old provider in a few steps.

This is a one-time import, not a live sync — once it finishes, your data lives here and no longer stays connected to your old provider in any way.

Where to Find It

Open your status page, then either:

• Go to Settings → Components and click Migrate from another provider, or
• Right after creating a new status page, click Import your data on the banner shown on the next screen.

Both take you to the same import wizard.

What Gets Imported

Instatus, StatusPage.io, Hyperping, Phare, status.io, and Hund bring in your components and incidents (with their full update timeline); all but Phare also bring in maintenance windows (Phare’s API has no maintenance-window concept). Instatus, Hyperping, Phare, and OhDear can also import your uptime monitors, alongside monitors-only UptimeRobot and Uptime.com. OhDear has no incident or maintenance concept at all — its status-page “updates” don’t map cleanly onto ours, so only components and monitors come across; if any of your OhDear monitors have SSL certificate or DNSBL blocklist checks enabled, you can optionally also bring those in as account-wide monitoring tools (see below).

Step 1: Choose Your Provider

Pick the provider you’re migrating from. Providers with no status-page-content concept (UptimeRobot, Uptime.com) are marked monitors only — selecting one skips straight to the monitor-specific parts of the wizard.

Step 2: Connect Your Account

Enter your provider’s API key. Some providers also need a page ID or subdomain — the field only appears if your chosen provider requires it.

Your API key is never stored. It’s held in memory only for the duration of this wizard and is discarded the moment your import finishes (or if you close the tab). There’s no persistent connection to your old account — this is a one-time pull, not an ongoing integration.

Click Validate & continue. This makes the cheapest possible authenticated call to confirm your credentials work — nothing is imported yet.

Step 3: Preview

Before anything is written, you’ll see exactly what will be imported: counts of components, incidents, maintenance windows, and monitors.

If the import would put you over your plan’s limits (for example, more components than your plan allows), you’ll see a clear warning instead of a partial import — upgrade your plan or reduce what you’re bringing over before continuing.

There’s also an optional toggle: Also import historical uptime data for monitors. This is off by default since it can be a lot of data. If you turn it on, history is capped by how far back your plan retains uptime data — older points are discarded.

If you’re migrating from OhDear and any of your monitors have an SSL certificate or DNSBL blocklist check enabled, you’ll also see Also import N SSL checks and M DNSBL checks as monitoring tools. This is off by default. Checking it creates matching entries under Tools → SSL Monitoring and Tools → DNSBL Monitoring — these are account-wide tools, not tied to this specific status page.

If Your Page Already Has Data

If the status page you’re importing into already has components, incidents, maintenance windows, or monitors on it, you’ll see a warning before you continue — importing on top of existing data adds alongside it and may create duplicates (for example, two components both named “API”).

If you’d rather start clean, check Delete existing data on this page before importing. This reveals a confirmation field — type the status page’s exact name to enable Start import.

This is permanent. Deleting existing data cannot be undone. Only the entity types your chosen provider actually imports are affected — for example, importing from UptimeRobot only ever offers to delete existing monitors, never your components, incidents, or maintenance windows.

Step 4: Import & Progress

Once you click Start import, the import runs in the background — you can safely close the tab or navigate away, and it keeps going. The page polls for progress and shows a live per-type count as components, incidents, maintenance windows, and monitors are created.

When it finishes, you’ll see a summary of what was imported, and a link to your updated status page.

Troubleshooting

“Could not authenticate with [provider]”

• Double-check your API key — it’s easy to copy a truncated or expired key
• If your provider needs a page ID or subdomain, make sure you entered the right one — this is usually visible in your old provider’s dashboard URL or account settings

Import stuck at “Importing your data…” for a long time

• Large accounts (hundreds of incidents with full update history) can take a few minutes — this is normal
• If it’s been stuck much longer than that (for example, after a period where our platform may have restarted), a background check automatically detects and flags interrupted imports within about 20 minutes
• Either way, it’s always safe to just re-run the wizard: anything already imported is automatically detected and skipped, so re-running never creates duplicates

“This import has more components than your plan allows”

• Either upgrade your plan first, or delete some existing components to make room, then re-run the import — anything already imported is skipped automatically, so re-running only picks up what’s left

What’s Next?

• Add components to your page
• Connect a custom domain
• Set up subscriber notifications