# Move from UptimeRobot to up4

> Match UptimeRobot’s terms to up4’s, bring your monitors over with the CSV import, see what does not carry over and run both tools side by side before you switch alerts.

Source: https://upfour.io/docs/moving/uptimerobot

You will have your UptimeRobot monitors running in up4 while UptimeRobot keeps running, so you can compare both before you switch your alerts.

- **Who:** Anyone who can create monitors in your Company
- **Time:** One sitting, then 48 to 72 hours side by side

You need your UptimeRobot login or API token and the people or channels that should receive alerts. In that one sitting you move a first batch.

## Match UptimeRobot’s words to up4’s

| UptimeRobot | up4 | What to know |
| --- | --- | --- |
| Monitor (HTTP, Keyword, Ping, Port) | **Monitors** | up4 has HTTP, ping, TCP and DNS checks. A keyword is a setting on an HTTP monitor. |
| Heartbeat monitor | **Scheduled jobs** | Your job checks in with up4 instead of the other way round. |
| Notification channel | **Alert channels** | You connect each channel again. |
| Maintenance Window | **Maintenance window** | A setting on each monitor. |
| Status Page | **Status pages** | You build it again in up4. |
| Tags | **Tags** | Imported as text in the monitor’s metadata. |
| Location | **Check regions** | Europe, North America, Asia and Australia. |

## Export your monitors and import them

UptimeRobot’s help center lists bulk actions for monitors; none of them exports the list. It describes a bulk upload with a downloadable template, and the [UptimeRobot API](https://uptimerobot.com/api/v3) lists monitors with **GET /monitors**. So you either call the API or copy your monitors into a file yourself.

**In up4:** Monitoring › Paste many URLs · [Open in up4](https://app.upfour.io/monitors/new/batch)

## Steps

### 1. Collect your monitors

List them through the API, or copy them from your dashboard. You need one row per monitor with its address, name and interval.

### 2. Save them as a CSV file

Keep a header row. Commas, semicolons and tabs all work; save as UTF-8\. UptimeRobot’s help names the template columns Type, URL/IP, Interval, Friendly Name, the keyword columns, Port and Tags. Check the header text in your own template.

```
Friendly Name,URL/IP,Interval,Tags
Main website,https://example.com,300,production
```

### 3. Open Import websites

Choose **Choose CSV file** or paste the file. up4 accepts up to 500 rows and 2 MB at a time.

### 4. Check Map columns

up4 recognizes some headers by themselves. Every other column shows **Choose field…** until you pick a field or **Ignore this column**.

| UptimeRobot column | In up4 |
| --- | --- |
| Friendly Name | Recognized automatically as **Name**. |
| Interval | Recognized automatically; seconds are fine. |
| Tags | Recognized automatically as **Tags**. |
| URL/IP | Not recognized because of the slash. Choose **URL / target**. |
| Keyword value | Choose **Required keyword**. |
| Type, keyword type, Port | Choose **Ignore this column**, then add TCP, ping or DNS monitors under **Advanced setup**. |

### 5. Choose Preview import, then create

The preview creates nothing. Read each row, fix or exclude errors, and tick **Create paused for setup review** if you want to look first. Existing targets are skipped as duplicates.

## How you know it worked

**View imported monitors** lists exactly the monitors you created. A monitor reads as pending until its first check result arrives.

## See what does not carry over

- **History.** Check results, uptime figures and incidents stay in UptimeRobot. up4 starts measuring with its first check.
- **Notification channels.** Connect each channel once in up4\. The import only assigns channels that already exist.
- **Heartbeat monitors.** The import creates monitors only. Create each **Scheduled jobs** entry and put its new ping URL into your job.
- **Status pages.** Build them again. If you hold a list of subscriber addresses, **Upload previous subscribers** takes a CSV, TSV or TXT file with one address per line, up to 10,000 addresses. It is available after your first top-up or with a subscription, and up4 invites each address.
- **Maintenance Windows.** Set them again on the monitors.

## What up4 does not do here

up4 does not read your UptimeRobot account and has no one-click migration. You bring the file; up4 shows a preview before it creates anything.

## Expect these differences

- **Confirmation.** up4 does not alert on one failed check. A change of state needs 3 consistent observations: the first differing check plus 2 instant re-checks. Read your UptimeRobot settings before you compare alert timing.
- **Intervals.** UptimeRobot’s bulk-upload template lists 60 to 86,400 seconds. up4 accepts intervals from 10 seconds.
- **Price per check.** Every check type costs €9 per million checks. One monitor checked every minute from one region comes to €0.39 a month. Each extra region repeats the checks. See [What costs money](https://upfour.io/docs/how/what-costs-money.md).

## Run both tools side by side

1. Pilot three to five websites that matter, with one alert channel.
2. Leave UptimeRobot running. 48 to 72 hours is a rule of thumb, not a requirement.
3. Import the rest of your list.
4. Send a test alert per channel and confirm it arrived. Then turn off the alerts in UptimeRobot; its bulk actions include **Pause and Start**.

The [switching overview](https://upfour.io/switch) has the same plan in short.

## Take your monitors back out

Open **Monitor tools** in the monitor list and choose **Export monitors (CSV)**. The file imports again into this or another up4 account. Passwords, request headers and proxy settings are not included. To use the file elsewhere, keep the name, address and interval columns and rename them to that tool’s template.

## If something is off

- The preview button stays disabled: every column must be mapped or set to **Ignore this column**, and each field only once.
- A row shows an interval error: use whole seconds, or 60s, 5m or 1h.
- More fixes are in [the import guide](https://upfour.io/docs/import#troubleshooting).