Migrating from Checkly to Lemwatch

Checkly is the easiest of the group to leave cleanly: GET /v1/check lists every check, and GET on the check-results resource returns the recorded run results, so both config and history come out through documented endpoints.

Exporting your monitors

Call GET /v1/check ('List all checks') on the Checkly API. Because Checkly checks are code-first, the response includes the script or request definition, not just a URL — so you keep the actual test logic, not a summary of it.

Exporting your history

Checkly documents a list-all-check-results endpoint under its API reference, so historical run results can be pulled programmatically rather than screenshotted.

Things that catch people out

• Checkly checks are Playwright scripts, so they do not port one-to-one into a URL-based uptime tool — decide which are genuine uptime checks and which are browser flows before you migrate.
• Checks live under Checkly's own project/group structure; the API returns those group IDs, so keep the raw JSON if you need to rebuild the grouping in the new tool.
• If you run Checkly through its CLI in CI, the source of truth is your repo rather than the dashboard — remove those pipeline steps as part of the switch or they keep recreating checks.

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