Introduction
Atlassian has given Opsgenie a definite end: new sales stopped on June 4, 2025; existing customers can keep using it until support ends on April 5, 2027, after which Opsgenie access shuts off and customer data that has not been moved out will be deleted (see the Atlassian Opsgenie Licensing FAQ).
For teams still running on Opsgenie, the real question is not “should we keep using Opsgenie” — it is where your schedules and escalation policies live next.
Stay inside Atlassian
Migrate into Jira Service Management (JSM) or Compass with Atlassian’s official in-app tool — ticketing and alerting from one vendor, with the lowest migration friction
Move to an independent on-call platform
Flashduty as the example: schedules, escalation, and incident collaboration run independently of JSM packaging, licenses are billed per active responder, with native Feishu/DingTalk/WeCom support
The feature and pricing information on this page is current as of September 2026; refer to each vendor’s official website for the latest updates.
Sunset Timeline and the Official Migration Path
Key Dates
Atlassian’s Official Migration Path
Atlassian steers teams toward Jira Service Management (incident management) or Compass (alerting/on-call) through an in-app migration tool. Key constraints:- Migration must be initiated by an Opsgenie Owner (who typically also needs site-admin rights);
- The migration date must be scheduled at least 7 days in advance;
- After a completed JSM migration, Opsgenie remains available for a 120-day review period before being permanently shut down;
- Most configuration syncs automatically, but destination-plan differences and some configuration require manual follow-up — for example, alert actions, incident rules, Responder roles, and Stakeholder filters do not migrate automatically and must be reviewed and rebuilt in the destination product.
Product Feature Comparison
On-call
On-call solves “getting the alert to the right person”: reduce noise first, then notify according to scheduling and escalation policies.Schedule Management
Dispatch & Escalation
Notification Channels
Alert Noise Reduction
Response
Response solves “closing the loop quickly once the right person is found”: a single timeline, a single war room—handling, collaboration, and postmortems that never lose context.Status Pages
AI Capabilities
Platform & Integrations
Pricing Comparison
Billing Model Difference Example
Take a 100-person engineering team where 15 people routinely handle incidents:Migration Path Comparison
Path One: Migrate into Jira Service Management (Stay in Atlassian)
Best for organizations already standardized on the Atlassian suite. The official in-app tool syncs most configuration into the selected JSM plan, but note:- Automation configuration such as alert actions and incident rules does not migrate automatically and must be rebuilt with Jira Automation;
- Fields like Responder roles and Stakeholder filters need post-migration review;
- Chat integrations must be reconfigured with new authentication;
- The migration date must be scheduled at least 7 days ahead, with a 120-day review period after completion.
Path Two: Cut Over to Flashduty (Independent On-call)
Best for teams that want their on-call practice to run independently of JSM packaging. Please be aware: there is no one-click importer from Opsgenie to Flashduty — Flashduty specialists help you plan the cutover, and your team deliberately rebuilds schedules, escalation policies, services, routing, and integrations. In return, your alerting platform no longer depends on Atlassian packaging or seat-based billing.Recommended Migration Steps
1
Audit your existing configuration
Inventory schedules and rotation rules, escalation policies, integration endpoints, alert routing rules, and notification templates
2
Rebuild the core path in the destination
Connect one real alert source first; configure schedules and escalation policies; run SMS, phone, IM, escalation, and closure end to end
3
Run in parallel and verify
Keep the old and new response paths running side by side for a while; test acknowledgement and escalation with real responders
4
Cut over and decommission
Once the workflow is proven, agree on a cutover window; export the data you need to keep before the end-of-support date, when unmigrated data will be deleted
How to Choose
Choose Flashduty if
- You need a durable on-call / incident-response home outside Atlassian’s merge path
- You want licenses billed only for members who actually handle incidents, with notification recipients at zero cost
- Your daily collaboration lives in Feishu, DingTalk, or WeCom and needs native support (including on-premises versions)
- You want built-in status pages, war rooms, AI postmortems, and AI SRE autonomous troubleshooting
- You need private deployment
Stay on the Atlassian path if
- Your organization is already standardized on Jira, Confluence, and Jira Service Management
- You want Atlassian’s automated in-app migration with the lowest friction
- You value ticketing and alerting from one vendor more than an independent on-call product
Summary
Opsgenie was an excellent alerting and on-call product, but its lifecycle is now on a countdown. For existing users, April 5, 2027 is a firm planning boundary: migration is not a question of whether, but of where to.
- If your organization already runs on the Atlassian suite, JSM is the official, lowest-friction path;
- If you want to use this migration to rebuild an independent, durable on-call practice — licenses billed per responder, native China IM collaboration, built-in status pages and AI capabilities — Flashduty is worth a full evaluation.