Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.incident.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Context

When migrating from Atlassian StatusPage to incident.io’s status page, you’ll want to ensure your existing subscribers continue receiving updates. Understanding which subscriber types can be migrated automatically and which require manual intervention is important for planning your migration.

​
Answer

During the Atlassian StatusPage migration process, incident.io automatically handles certain types of subscribers while others require manual action:

​
Automatically Migrated

  • Email Subscribers: All email subscribers are automatically migrated when you click “Go Live” in the migration wizard

​
Not Supported/Requires Manual Action

  • Webhook Subscribers: Webhook subscriptions are not currently supported. You may wish to consider exposing the widget API to customers in this case if they want to programatically retrieve the status of your status page.
  • Slack Subscribers: Slack subscribers cannot be migrated. Slack doesn’t allow a new app to take ownership of subscriptions created by another app (in this case, Atlassian Statuspage), so existing Slack channel subscriptions from your old status page won’t carry over.

​
How to Migrate

  1. Enable the status page integration in incident.io
  2. Access the Atlassian status page migration wizard
  3. Follow the migration steps until you reach the “Go Live” stage
  4. Click “Go Live” to automatically migrate supported subscribers
For a detailed walkthrough of the complete migration process, refer to our migration guide.