Migrating from UptimeRobot to Lemwatch

UptimeRobot has no documented CSV export, but its public API does the job: POST getMonitors on https://api.uptimerobot.com/v2/getMonitors returns every monitor on your account as JSON, which you can paste straight into a bulk import.

Exporting your monitors

Use the v2 REST API: POST https://api.uptimerobot.com/v2/getMonitors with your API key. UptimeRobot's docs note getMonitors is the one endpoint that also accepts the api_key as a URL parameter, so you can pull the list from a browser tab if you do not want to write a script. A newer v3 API is published at uptimerobot.com/api/v3.

Exporting your history

getMonitors can return response-time points and log entries when you pass the matching parameters, but UptimeRobot documents no dedicated CSV or bulk history export endpoint. Treat historical charts as staying behind — pull what you need via the API before you cancel.

Things that catch people out

• UptimeRobot's pricing page lists 12-month data retention as a paid-plan feature, so the history you can pull depends on the tier you are on the day you export — do the export before you downgrade.
• Because there is no CSV button, the export is API-only: budget ten minutes for a script or an API-key URL fetch rather than expecting a download link in the dashboard.
• Alert contacts are attached to monitors inside UptimeRobot, so getMonitors gives you the URLs but you still rebuild alert routing by hand in the new tool.

Export mechanics verified on 2026-08-04 against UptimeRobot's own documentation.