Migrate from Statuspage

From your Statuspage dashboard, open Subscribers in the left sidebar and click Export subscribers. Choose which subscriber types to include (email, SMS, or webhook) and pick CSV or JSON; Statuspage emails you the file rather than starting a download in the browser. Slack subscribers are not included in this export; Statuspage's own documentation says they cannot be exported at all.

RealUptime only has an email subscriber concept today, so the email-type export is the one that matters here. Keep the CSV: it is already in the exact format Statuspage's own bulk importer uses, which is what the next step relies on.

Create a status page under your RealUptime dashboard, add components for the services you tracked on Statuspage, and add a monitor for each one so the page has something of its own to measure rather than only a hand-set state. If Statuspage 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). RealUptime recognizes Statuspage's own export/import format natively -- type,value,... per row, no header row expected -- so the file does not need reformatting first. Only email rows import;sms and webhook rows come back flagged as unsupported, since RealUptime has no SMS or webhook subscriber concept. Statuspage's per-row "skip confirmation" column and its component codes are both read and ignored: component codes do not map onto this page's own components, so those rows are queued page-wide with a note saying so, never silently dropped.

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.