Last updated
Atlassian ended new sales of Opsgenie on June 4, 2025 and ends support on April 5, 2027. On April 5, 2027, Atlassian shuts off access to Opsgenie and deletes any customer data that has not been moved to Jira Service Management. Teams can migrate to Jira Service Management with Atlassian's tool, or export their data and move to another on-call platform before that date.
Timeline
| Date | What happens | Source |
|---|---|---|
| March 4, 2025 | Atlassian announces that Opsgenie will no longer be available for purchase. | Opsgenie licensing ↗ |
| April 5, 2025 | Opsgenie chat support is replaced with a support request system. | Support coverage ↗ |
| June 4, 2025 | End of sale. No new purchases or sign-ups, directly or through partners and resellers. Plan upgrades and downgrades end. Existing customers can still add seats; renewals are allowed if the term concludes before April 5, 2027. | Opsgenie licensing ↗ |
| Migration date + 120 days | For sites migrated to Jira Service Management, Opsgenie stays available in parallel for 120 days, then shuts down automatically if it was not turned off manually. | Turning off Opsgenie ↗ |
| April 5, 2027 | End of support. Access is shut off, the product is no longer accessible, data not moved to Jira Service Management is deleted, the Opsgenie REST APIs stop working, and Opsgenie-specific support ends. | Opsgenie licensing ↗ · Turning off Opsgenie ↗ · Support coverage ↗ |
Dates and quoted wording come from Atlassian's own pages, checked . Atlassian can update these pages; verify the source before you plan around a date.
Atlassian's official wording
From the Opsgenie licensing page ↗:
“Opsgenie end of support - effective April 5th, 2027: On this date, access to Opsgenie will be shut off, the product will no longer be accessible, and any customer data in Opsgenie that has not been moved to Jira Service Management will be deleted.”
From the support article What happens when Opsgenie is turned off? ↗:
“Opsgenie REST APIs will continue to work until April 5, 2027. However we recommend updating all API endpoints before Opsgenie is turned off avoid any disruptions.”
What happens when Opsgenie is turned off
Atlassian's support documentation lists these effects:
- Users lose all access to Opsgenie and cannot log in or retrieve any data.
- The Opsgenie mobile app is deactivated.
- Any remaining Opsgenie-based integrations stop working.
- Features left behind in Opsgenie — Atlassian names deprecated notification policies, incident rules, Opsgenie actions, and older integrations such as Crashlytics — become permanently unavailable.
- Turning Opsgenie off is permanent and cannot be undone.
What happens to your data
- Migrated to Jira Service Management: alerts, on-call schedules, escalation policies, incident history, audit logs and activity history, and migrated configurations and integrations remain available there (source ↗).
- Not migrated: deleted at end of support on April 5, 2027 (source ↗). Atlassian's migration FAQ notes that customers who choose not to move can still download their Opsgenie data directly (source ↗) — do that before the deadline.
- Alert retention after a move to Jira Service Management follows the plan: Free 1 month, Standard 1 year, Premium 3 years, Enterprise 5 years. Atlassian notes this differs from the Opsgenie Enterprise plan, where data was retained indefinitely (source ↗).
Your options
| Option | What it involves | Things to check |
|---|---|---|
| Move to Jira Service Management | Atlassian's automated migration on a date you schedule, with 120 days of parallel Opsgenie access to validate the setup. | Features Atlassian lists as left behind; per-agent JSM pricing; alert retention by plan. |
| Move to another on-call tool | Export Opsgenie configuration and history, rebuild or import schedules and escalations, repoint every alert source. | Import tooling, Opsgenie API compatibility, per-user pricing, mobile paging. |
| Export and archive only | Download the data you need to keep, whichever destination you choose. | Alerts, incidents, and audit logs needed for compliance or post-incident reviews. |
We compare the main destinations, including what each does better, on Opsgenie alternatives and OpsPing vs Jira Service Management.
A checklist before April 5, 2027
- Inventory everything that sends to Opsgenie: monitoring integrations, API scripts, heartbeats, and
@opsgenie.netemail integrations. - Export the history you need to keep — alerts, incidents, and audit logs — since unmigrated data is deleted.
- Record per-user notification rules, alert policies, and forwarding rules; these are the settings most likely to need manual work.
- Pick the destination and run it in parallel with Opsgenie for at least one on-call cycle.
- Test a firing and a resolution through every alert source before you move the rotation.
If you are considering OpsPing
OpsPing is an on-call paging platform with an Opsgenie-compatible alert API (a documented subset, using the GenieKey header syntax) and an Opsgenie importer for users, teams, services, schedules and overrides, escalation policies, heartbeats, and integrations. Plans are Free, Team at $8 per responder per month, and Business at $15. The importer dry run is free; applying an import requires Team or Business. The step-by-step process is in How to switch from Opsgenie.
FAQ
Is Opsgenie being shut down?
Yes. Atlassian stopped selling Opsgenie on June 4, 2025, and end of support is April 5, 2027. Atlassian states that on that date access to Opsgenie will be shut off, the product will no longer be accessible, and any customer data in Opsgenie that has not been moved to Jira Service Management will be deleted.
Can I still buy Opsgenie?
Not as a new customer. Since June 4, 2025, new purchases and sign-ups are closed, including through partners and resellers, and plan upgrades and downgrades are no longer available. Existing customers can still buy additional seats, and renewals are allowed as long as the subscription term ends before April 5, 2027.
Will the Opsgenie API keep working until the shutdown?
Atlassian says the Opsgenie REST APIs will continue to work until April 5, 2027, and recommends updating API endpoints before Opsgenie is turned off. If you migrate to Jira Service Management, Opsgenie shuts down automatically 120 days after your migration date unless you turn it off sooner.
What happens to my Opsgenie data?
After shutdown you lose all access and users cannot log in or retrieve data. Only data migrated to Jira Service Management remains available there. Anything else is deleted, so export alert history, incident records, and audit logs you need to keep before April 5, 2027.
Do I have to move to Jira Service Management?
No. Jira Service Management is Atlassian's designated destination and has an automated migration. You can also export your data and move to a different on-call tool; Atlassian notes that customers who choose not to move can download their Opsgenie data directly.
Sources
- Atlassian — Opsgenie Licensing ↗ (end-of-sale and end-of-support dates and wording)
- Atlassian Support — What happens when Opsgenie is turned off? ↗
- Atlassian Support — Support coverage after migration ↗
- Atlassian — Migrate Opsgenie ↗ (migration FAQ, 120-day parallel access)
All sources accessed .
Opsgenie® is a trademark of Atlassian. OpsPing is not affiliated with, sponsored, or endorsed by Atlassian.