Getting Started

Migrating from UptimeRobot

Move every UptimeRobot monitor to Everguardly in about two minutes — using your API key or a CSV export. Type, interval, and status mapping explained.

Updated 2026-05-25 · 2 min read

Most agencies arrive at Everguardly from UptimeRobot. The reasons are usually the same: SSL and domain expiry aren't first-class, per-client routing requires workarounds, and the renewal calendar doesn't exist. The good news is the migration itself takes about two minutes — here's how.

Two paths exist

The API key path is faster and preserves more metadata. The CSV path is the fallback for users who can't access the API settings, usually because someone else owns the UptimeRobot account.

Path 1 — API key (recommended)

  1. Sign in to uptimerobot.com.
  2. Click My Settings in the left sidebar.
  3. Scroll to API Settings. Reveal your Main API Key (or a Read-Only API Key — both work), copy it.
  4. In Everguardly open Dashboard → Import from UptimeRobot, pick API key, paste, click Connect.

Within a few seconds you'll see every HTTP(S) monitor in your account in a preview table.

Path 2 — CSV

From the UptimeRobot dashboard click Export → CSV. Open the file (or paste the contents) into the wizard's CSV step. We accept both the standard UptimeRobot export (Monitor Friendly Name, Monitor URL, …) and a simplified format with FriendlyName, URL, Type, Interval, Status columns.

Type mapping

UptimeRobot has five monitor types: HTTP(s), Keyword, Ping, Port, Heartbeat. Everguardly V1 ingests HTTP(S) monitors only. The other types appear in the preview greyed out with a reason — we don't drop them silently. Keyword, port, and heartbeat support are planned for V2.

Interval mapping

UptimeRobot exports intervals in seconds (API) or minutes (CSV). We snap to the nearest allowed Everguardly interval: 60s, 5m, 15m, or 1h. A 30-second UR monitor becomes a 1-minute Everguardly monitor; a 6-minute UR monitor becomes a 5-minute monitor.

Bulk client assignment

The preview step has an "Assign all to client" dropdown. Pick an existing client, create a new one inline, or leave unassigned. You can also paste a bulk tag string (e.g. imported, uptime-robot) that gets applied to every imported monitor — handy for finding "everything I just imported" later.

Duplicate URLs

If a URL already exists for your account, we skip the row and report it in the post-import summary. You can re-run the wizard safely; nothing gets duplicated.

After the import

Three things to do next:

  1. Pick alert channels in Settings → Channels.
  2. Open the Renewal Calendar to see when each domain and certificate expires.
  3. Assign a public status page to clients that need one (Clients → Edit → status page toggle).

What doesn't import yet

Keyword monitors, port monitors, the public status page (you'll set this up fresh in Everguardly, mapping clients to public slugs), and alert contacts. You'll re-create channels via Settings → Channels — takes two minutes and you'll usually consolidate from ten contacts to two or three real channels.

What you get that UptimeRobot doesn't have

Domain expiry tracking via RDAP runs automatically on every monitor you import, SSL expiry tracking likewise, the renewal calendar across every client is populated as soon as the worker's hourly tick completes, and per-client routing kicks in the moment you assign default channels to a client.

It's undo-friendly

Deleting an imported monitor is two clicks; the original UptimeRobot account is untouched until you choose to cancel.

Need something this doesn't cover? Email hello@everguardly.com — we'll write the doc.