Migrate from Statuspage to Kener

Take it out

1. 1

   Step 1

   Export subscribers while the page is still up

   Atlassian's support page says a page admin opens Subscribers, then Export subscribers. Pick email, SMS, or webhook, then CSV or JSON. The file is emailed to you. Slack subscribers cannot be exported. Keep the file off any shared drive you do not control.

2. 2

   Step 2

   Save components and incidents from the API

   Statuspage's API lists components at /v1/pages/{page_id}/components and incidents at /v1/pages/{page_id}/incidents. The developer docs use https://api.statuspage.io/v1/ and an API key. There is no single backup file. An Atlassian community answer describes the subscriber export plus the API as the practical copy.

3. 3

   Step 3

   Write down the domain and the component list

   Note the custom domain and which components matter. Component subscriptions do not become a Kener setting. Do not change DNS until a test email has arrived.

Put it in

1. 1

   Step 1

   Start Kener and set the public URL

   Kener's README says to clone the repo and run Docker Compose, which includes Redis. Set KENER_SECRET_KEY and ORIGIN before the first start. ORIGIN is the public URL, without a path. If you skip Docker, the README asks for Node.js 24.14 or newer and Redis. Open that URL and confirm the page loads before you point the real domain at it.

2. 2

   Step 2

   Recreate components as monitors

   Add a monitor for each Statuspage component you still want on the page. The docs include monitor groups if the old page was split into sections. Leave the monitors you do not want hidden, because Kener's subscription doc says incident mail goes out when the incident is global or it affects a monitor that is not hidden.

3. 3

   Step 3

   Turn on email, then send one test

   The subscriptions doc says an admin enables subscriptions, and email is SMTP or Resend. A person subscribes on the public page with an email address and a one-time code, then picks incidents, maintenance, or both. Post one incident update. The doc says an update queues mail, including a comment posted to /api/v4/incidents/{incident_id}/comments. Stop if that test message does not arrive.

4. 4

   Step 4

   Ask people to subscribe again

   The docs checked describe that public subscribe flow. They do not describe loading a Statuspage CSV. Use the export as the list of people to tell. Do not mark the old page read-only until one of them has subscribed and received a test.

What you lose

• Slack subscribers and SMS

  Slack subscribers cannot be exported. SMS numbers can be in the export. Kener's subscription page is email, with a one-time code. It does not describe SMS subscribers.

• Named metrics

  Statuspage metric points do not move. Kener's README describes uptime trends from monitors, not a chart you name yourself.

• Incident history and SSO

  Old incidents stay in the API export. They do not appear on the new page unless you write the ones you still want public. Atlassian Guard sign-in for your team does not become a Kener login.

• The subscriber file is not an import

  A CSV proves who was subscribed. It does not create those subscriptions. Each person confirms an email address on the new page.