Migrate from Cachet

In your dashboard, open Import from another service and paste the address of your Cachet page. Cachet 2.x answers /api/v1/components and /api/v1/components/groups to any visitor, without an API token, so you do not hand over a key. Every enabled component comes across in Cachet's order, inside a component group of the same name, all operational. A component your page already has is left as it is, so running it twice adds nothing twice.

In Cachet, a component changes state when a person sets it or a script calls the API. On RealUptime a component follows a check, and RealUptime Monitor runs those checks from four regions on Free, eight on Pro, all ten on Business. Add an HTTP, keyword, TCP, DNS or heartbeat check for each imported component and attach it; anything no check can measure stays a manual component with a state you set. Free covers 10 monitors.

Cachet's subscriber list is behind an admin token, so the importer does not read it. Export the addresses from your Cachet dashboard or database as a one-email-per-row CSV and upload it to your status page's subscriber importer (Pro and Business). You attest that these people subscribed to your old page, and each address gets one confirmation email before it receives anything else, so nobody is silently re-subscribed.

Past incidents stay in Cachet. An incident on RealUptime belongs to a check that observed it, and creating one now would email every subscriber about an outage that is long over. If you need the record, keep the old page read-only for a while or link to it from your new page.

When the new page looks right, point your status domain at it (custom domains are on Pro and above) and switch the Cachet server off. That is one fewer PHP application, database and queue worker to patch.