Migrate from Instatus

From your Instatus dashboard, open the Subscribers tab, switch to Email, and export that list as CSV. SMS subscribers export the same way from the SMS tab, but RealUptime has no SMS subscriber concept today, so only the email file matters for this migration. Keep the file: the next step uses it as-is.

Create a status page under your RealUptime dashboard, add components for the services you tracked in Instatus, and add a monitor for each one. Each monitor runs from every region your plan includes and the page shows all of them together, rather than the single rotating location Instatus's own docs describe. If Instatus served your page from a custom domain, add the same domain here (Growth and Scale plans); RealUptime provisions the TLS certificate automatically once the CNAME points here.

Upload the CSV from step one directly into the status page's subscriber importer (Growth and Scale plans). Instatus's export is not Statuspage's specific type,value,... format, so it goes through RealUptime's generic path instead: one email address per row, with an optional header row and an optional second column naming which of this page's components to scope the subscription to. If your Instatus export carries extra columns, trim it down to the email column (plus components, if you want to set them) before uploading.

Say this plainly, because it is the honest tradeoff of moving a list without everyone re-opting in by hand: every imported address is queued unconfirmed and gets exactly one email asking them to confirm before they receive anything else. This is not a silent bulk re-subscribe. Nobody starts receiving incident mail because you attested a CSV; they start receiving it because they clicked confirm. An address that never confirms is purged automatically after 30 days. You attest, per import, that these addresses already subscribed to your previous page -- RealUptime records that attestation rather than independently verifying it, the same as any other customer-asserted compliance fact.