Migrate from Uptime Kuma

On Uptime Kuma 1.x, open Settings, Backup and use Export. You get a JSON file with your monitor list. Kuma warns that it also holds notification tokens; the importer reads only the monitor list and ignores the rest, but store the file carefully all the same.

Uptime Kuma 2.0 dropped the backup and restore feature, so on 2.x there is no JSON file to export. What 2.x does publish is a Prometheus page at /metrics, and every monitor appears there with its name, type, URL, hostname and port. Create a key under Settings, API Keys, open /metrics with any username and the key as the password, and save the page as a text file. It does not include check intervals, so those start at every minute and you adjust them afterwards.

In your dashboard, open Import from another service and upload the file under Import from Uptime Kuma. The preview shows every monitor in the file: what it becomes here, its target and its interval. Monitors that cannot come across are listed with their Kuma type and a reason. Pick the ones you want and choose Import selected. Imports count against your plan's monitors, 10 on Free, and the preview says how many more fit.

A Kuma push monitor becomes a heartbeat here. Kuma's push token is Kuma's credential, so the importer never reads it, and each heartbeat gets a new ping URL, listed once on the result screen. Change each job's push line to its new URL. A heartbeat that has never been pinged waits for its first ping and alerts nobody, so you can roll the URLs out at your own pace.

RealUptime checks from public regions, so a monitor pointed at a private or LAN address (a router, a NAS, a container on an internal network) is refused at import and named on the result screen. For machines inside your network, install the server agent, which reports outward and needs no open port. Or keep Kuma for the inside of the network and use RealUptime only for the thing Kuma cannot do for itself, which is notice when Kuma or its host goes down: see watching Uptime Kuma from outside.