Atlassian ended new Opsgenie sales on June 4, 2025 and shuts Opsgenie off on April 5, 2027, deleting any data not moved to Jira Service Management. As of November 2, 2026 that is 154 days away. A migration to Jira Service Management starts a 120-day parallel window, but the April 5, 2027 cut-off still applies, so the planning dates that matter now are December 6, 2026 (the last migration date with a full 120-day overlap) and March 29, 2027 (the practical last day to schedule). We worked out both dates from Atlassian's rules.
This page is the dated reference. For what the shutdown means for your data and the paths teams are taking, see Opsgenie end of life: dates, data, and your options.
Timeline
| Date | Milestone | What it means | Source |
|---|---|---|---|
| 2018 | Atlassian acquires Opsgenie. | Background: Atlassian says it has been embedding Opsgenie's functionality into its platform since then. | Atlassian blog ↗ |
| 2020 | Atlassian launches Jira Service Management. | The product Atlassian now names as Opsgenie's destination. | Atlassian blog ↗ |
| March 3, 2025 | Atlassian publishes The Evolution of IT Operations and Opsgenie. | Announces the full transition of Opsgenie's capabilities into Jira Service Management and the two key dates below. Migration to Jira Service Management opens “starting today.” | Atlassian blog ↗ |
| March 4, 2025 | Atlassian's licensing page dates the announcement. | “On March 4, 2025 Atlassian announced that Opsgenie would no longer be available for purchase, effective June 4, 2025.” | Opsgenie licensing ↗ |
| April 5, 2025 | Opsgenie chat support ends. | 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 ends before April 5, 2027. | Opsgenie licensing ↗ |
| May 13, 2026 | Compass closes to new customers. | Atlassian is phasing out Compass and moving its catalog and scorecards to DX. Relevant if you planned to land Opsgenie data in Compass. | Atlassian Community ↗ |
| December 6, 2026 | Last migration date that still gets the full 120-day parallel window (OpsPing calculation). | Atlassian keeps Opsgenie running for 120 days after your migration date, but never past April 5, 2027. A migration on December 6, 2026 lands exactly on April 5, 2027; any later migration date gets a shorter overlap. This is our arithmetic from Atlassian's two rules, not a date Atlassian publishes. | What to expect ↗ · Licensing ↗ |
| March 29, 2027 | Practical last day to schedule a migration (OpsPing calculation). | Atlassian requires the migration date to be at least seven days in the future and allows dates up until April 5, 2027. Scheduling on March 29, 2027 is the last day a seven-day lead time fits. Leave margin: you can reschedule only once, and cancellations need 24 hours' notice. | What to expect ↗ |
| Migration date + 120 days | Automatic shutdown of a migrated site. | After a migration to Jira Service Management, Opsgenie stays available in parallel for 120 days, then shuts down automatically unless you turn it off sooner. Turning it off is permanent. | Turning off Opsgenie ↗ · What to expect ↗ |
| April 5, 2027 | End of support. | Access is shut off and the product is no longer accessible. Data not moved to Jira Service Management is deleted. The Opsgenie REST APIs stop working, the mobile app is deactivated, remaining Opsgenie-based integrations stop, and Opsgenie-specific support ends. | Licensing ↗ · Turning off Opsgenie ↗ · Support coverage ↗ |
| December 31, 2027 | Compass access ends. | Atlassian plans to end Compass support on this date. Alerts and operations functionality in Compass must move to Jira Service Management, because DX does not support it. | Atlassian Community ↗ · Migrate from Compass to DX ↗ |
Rows marked OpsPing calculation are our arithmetic from Atlassian's published rules, not dates Atlassian publishes. Every other date and quote comes from the linked Atlassian page, checked November 2, 2026. Atlassian can update these pages; check the source before you plan around a date.
Migration scheduling rules
From Atlassian's support article What to expect from Opsgenie migration ↗ and the related scheduling guide:
- Who can schedule. The person scheduling must be an Opsgenie Owner and a site admin of the Atlassian site, and the organization needs a billing admin, who must approve the new billing before the migration runs (Atlassian ↗).
- Lead time and deadline. The migration date must be at least seven days in the future and can be scheduled up until April 5, 2027.
- Changes. Once scheduled, the date can be rescheduled only once. A migration can be cancelled before billing approval, and cancellations must be made at least 24 hours before the scheduled date.
- Billing timing. Atlassian suggests monthly-plan customers schedule near their renewal date to avoid paying twice; annual-plan customers can schedule anytime.
- Rollout. The migration tool is rolling out in phases, and accounts not yet on an Atlassian account or the new billing system may not be able to schedule yet (Atlassian ↗).
- Recommended plan. Atlassian maps Opsgenie Free to Jira Service Management Free, Essentials to Standard, Standard to Premium, and Enterprise to Premium or Enterprise (Atlassian ↗). Stakeholders are migrated only to Premium or Enterprise.
What changes on April 5, 2027
- Users lose all access to Opsgenie and cannot log in or retrieve data (Atlassian ↗).
- The Opsgenie mobile app is deactivated; Atlassian tells users to switch to the Jira mobile app before shutdown.
- The Opsgenie REST APIs stop working, and any remaining Opsgenie-based integrations stop.
- Features left behind in Opsgenie, which Atlassian lists as deprecated notification policies, incident rules, Opsgenie actions and older integrations such as Crashlytics, become permanently unavailable.
- Only data migrated to Jira Service Management remains. Alert retention there follows the plan: Free 1 month, Standard 1 year, Premium 3 years, Enterprise 5 years (Atlassian ↗).
If you are not moving to Jira Service Management
Atlassian's migration FAQ says customers who choose not to move by the deadline can still download their Opsgenie data directly (Atlassian ↗). Plan the export before April 5, 2027, and keep your monitoring tools pointed at Opsgenie until the replacement has handled a real firing and resolution from every source.
OpsPing is one option for teams that want to keep the Opsgenie alert API: most senders change only the API URL to https://api.opsping.com and the GenieKey key. The supported subset and its gaps are on the Opsgenie-compatible API page, and the step-by-step plan is in How to switch from Opsgenie. Migration help is async by email at [email protected], with calls by appointment.
FAQ
When does Opsgenie shut down?
On April 5, 2027, Atlassian's end-of-support date. Atlassian says that on that date access to Opsgenie will be shut off, the product will no longer be accessible, and any customer data that has not been moved to Jira Service Management will be deleted. Sites that migrate to Jira Service Management earlier are shut down automatically 120 days after their migration date unless they are turned off sooner.
What is the last day to migrate from Opsgenie to Jira Service Management?
Atlassian lets you pick a migration date up until April 5, 2027, and the date must be at least seven days in the future when you schedule it. By our arithmetic that makes March 29, 2027 the practical last day to schedule. You can reschedule only once, so leave margin.
Do I still get 120 days of parallel access if I migrate late?
Not necessarily. The 120-day window starts on your migration date, but Opsgenie is shut off for everyone on April 5, 2027. By our calculation, December 6, 2026 is the last migration date whose 120 days end on or before April 5, 2027; later migration dates get a shorter overlap.
Does the Opsgenie API keep working until the shutdown?
Atlassian says the Opsgenie REST APIs continue to work until April 5, 2027, and recommends updating all API endpoints before Opsgenie is turned off. A site that is turned off early, manually or by the 120-day rule, loses access then.
Is Compass an alternative destination for Opsgenie data?
Not for the long term. Compass closed to new customers on May 13, 2026 and Atlassian plans to end access on December 31, 2027. Atlassian's Compass-to-DX guide says alerts and operations functionality must be migrated to Jira Service Management, because DX does not support it.
Sources
- Atlassian — Opsgenie Licensing ↗ (announcement date, end of sale, end of support)
- Atlassian — The Evolution of IT Operations and Opsgenie ↗ (published March 3, 2025)
- Atlassian Support — What to expect from Opsgenie migration? ↗ (scheduling rules, 120-day window)
- Atlassian Support — Why you can’t schedule your Opsgenie migration? ↗
- Atlassian Support — What happens when Opsgenie is turned off? ↗
- Atlassian Support — Support coverage after migration ↗ (chat support change, retention by plan)
- Atlassian Support — What are my options for migrating from Opsgenie? ↗
- Atlassian — Migrate Opsgenie ↗ (migration FAQ)
- Atlassian Community — The Next Chapter for Compass ↗ and Atlassian Support — Migrate from Compass to DX ↗
All sources accessed November 2, 2026. Opsgenie®, Jira Service Management and Compass are trademarks of Atlassian. OpsPing is not affiliated with, sponsored, or endorsed by Atlassian.