PathOctober 2026
How to migrate from UptimeRobot to Pathly
Read-only key, preview, import: your UptimeRobot monitors become Pings, port Pings and scheduled jobs. What carries over and what does not.
You monitor your sites, or your clients’ sites, with UptimeRobot and want to try Pathly without typing everything again. UptimeRobot tells you whether the server responds. Flow tells you whether the customer can pay. The import reads your account with a read-only key, shows you what it will do, then creates the Pings. The screenshots below come from a demo account.
1. Copy the read-only key
In UptimeRobot, open Integrations & API and copy the read-only API key. It can read your monitors, not change them. The main key works too, but nothing here needs it. A monitor-specific key only sees one monitor: Pathly rejects it rather than silently importing a single site.
In Pathly, open Observe, click Add at the top right then Import, and paste the key in the “From UptimeRobot” part. It is used to read your account during the preview and the import. It is neither stored nor written to logs.
2. Read the preview
“Preview what will be imported” runs a preview. Nothing is created. It counts the sites to create and the sites already monitored in Pathly, and lists two things: monitors not imported, with the reason, and sites imported with an adjustment. If your plan is too small, it shows the site where the import would stop.
| UptimeRobot monitor | In Pathly |
|---|---|
| HTTP(S) | Ping, same address, same interval or the plan’s minimum |
| Keyword “must exist” | Ping with expected text, case-sensitive |
| Keyword “alert if present” | Ping, without the keyword |
| Port | TCP port Ping, except port 25 |
| Heartbeat | Scheduled job, same period, new address |
| Paused | Paused, not counted in the plan |
| Group | Client picked for the import (the API does not give the group’s name) |
| Protected page, POST request | Not imported |
| ICMP ping | Not imported |
3. Run the import
The Import button creates what the preview announced, with names, addresses and intervals. Each item gets the “uptimerobot” tag, so one filter finds it. Paused monitors arrive paused. For each heartbeat, Pathly shows the new address to call once: replace UptimeRobot’s one in your job. You can run the import again later: what is already there is skipped, nothing is duplicated.
What is not imported
- ICMP ping monitors. Pathly monitors web addresses, ports and DNS records, not machines by ping.
- A port 25 monitor. Our hosting provider blocks outgoing traffic on that port: monitor port 587 or 465 of the mail server instead.
- Password-protected pages and POST requests. Pathly does not take credentials from another tool.
- Alert contacts, status pages, maintenance windows, group names and history. They stay in UptimeRobot.
- Custom HTTP headers and status codes. The Ping expects a 200, and the preview flags each site concerned.
4. After the import
Set up alerts: email works as soon as you sign up, and Slack, Teams, Discord, PagerDuty, Opsgenie and webhooks are included in paid plans. Keep UptimeRobot running alongside while you compare. Then add a Flow on the journey that matters, the checkout, the quote form or the login: that is what an address monitor cannot see.
- Does the import change my UptimeRobot account?
- No. With the read-only key, Pathly can only read your monitors. Nothing is paused or deleted in UptimeRobot.
- Are my one-minute or 30-second intervals kept?
- They are if your Pathly plan allows them. Otherwise the interval is raised to the plan’s minimum, and the preview notes it for each site concerned. Minimums are on the Pricing page.
- What about an account with hundreds of monitors?
- The import reads every page of the account. If your plan is not enough, the preview shows where the import would stop. You change plan, run it again, and sites already imported are skipped.