Migrate from Checkly

In Checkly, open User Settings, API keys and create a key. It carries your own role, so a viewer role is enough. RealUptime's importer sends it once, as a Bearer token, to Checkly's own GET https://api.checklyhq.com/v1/accounts to find your accounts, then to GET /v1/checks for each one, and reads back each check's name, type, URL and frequency. The key is used for that one read and is not saved anywhere.

On the dashboard's Import page, choose Checkly and paste the key. You get a preview of every check before anything is created. URL monitors and API checks that send a GET import directly, with their frequency, including sub-minute ones. API checks that send a body, and every other check type, stay in the preview, flagged as not imported, so nothing silently disappears.

A Checkly heartbeat becomes a RealUptime heartbeat: create one with the same schedule and point the job's ping at its address. TCP and DNS monitors map to the same check types here, ICMP to a ping check, and an API check that sends a body to a one-step multistep check. Browser checks are where the products differ most: RealUptime's browser check, on Business, runs a closed set of seven steps, not a Playwright script, so a long scripted flow needs rebuilding or stays where it is. The table below maps every Checkly check type.