What happens when Opsgenie is turned off?
Turning of Opsgenie means, users will no longer have access to Opsgenie’s features, or data. All alerting and on-call workflows must be fully migrated to Jira Service Management or Compass before this occurs.
Turning off Opsgenie is permanent and CANNOT be undone. Before you manually turn off Opsgenie, make sure you’ve completed all necessary actions in your migration guide. Opsgenie will also shut down automatically 120 days after your migration date if you don’t turn it of manually.
Whether Opsgenie is manually turned off by site admins or automatically shut down by Atlassian, we’ll notify all users.
What happens when Opsgenie is turned off?
After Opsgenie is shut down:
You’ll lose all access to your Opsgenie. Your users won’t be able to log in or retrieve any data.
Opsgenie mobile app will be deactivated. All users should switch to the Jira mobile app before shutdown.
Any features left behind in Opsgenie (e.g., deprecated notification policies, incident rules, Opsgenie actions, and older integrations like Crashlytics) will be permanently unavailable. Ensure alternatives are configured in Jira Service Management or Compass before the shutdown.
Any remaining Opsgenie-based integrations will stop working.
Opsgenie REST APIs will continue to work until April 5, 2027. However we recomment updating all API endpoints before Opsgenie is turned off avoid any disruptions.
What data is retained after Opsgenie is turned off?
Once Opsgenie is switched off, only migrated data will be available in Jira Service Management or Compass.
Alerts, on-call schedules, and escalation policies.
Incident history (only in Jira Service Management).
Audit logs and activity history (if applicable to the destination product).
Configurations and integrations that were migrated.
All other data that wasn’t migrated will be permanently deleted.
この内容はお役に立ちましたか?