OpsGenie is shutting down.
Your data gets deleted April 2027.
Atlassian announced end-of-life December 3, 2024. New purchases stopped June 2025. Full shutdown is April 5, 2027. If you have not migrated by then, your schedules, policies, and alert history are deleted.
The shutdown timeline
All dates from Atlassian's official announcements.
Atlassian announces OpsGenie end-of-life
The blog post was buried in product news. OpsGenie is being folded into Jira Service Management. The standalone product is done.
End of sale
No new purchases, no new trials, no partner sales. If you did not already have an OpsGenie subscription, you cannot get one.
JSM-bundled OpsGenie access removed
Teams who had OpsGenie through a JSM bundle lose access. Only standalone OpsGenie subscriptions keep working.
Full shutdown. Data deleted.
OpsGenie stops working. Unmigrated data is deleted. Schedules, policies, alert history. All of it.
What goes wrong when you migrate to JSM
Atlassian wants you on Jira Service Management. Here is what teams who migrated actually say.
Your alert history gets deleted
OpsGenie Enterprise kept data forever. JSM auto-deletes older alerts after a retention window. Once gone, gone. Teams that need historical alerts for compliance or postmortem trends lose that data.
The migration takes weeks, not days
Atlassian calls it automated. Teams who went through it say 4-8 weeks for simple setups. 8-16 weeks if you have 20+ integrations and layered rotations. Every team we talked to underestimated by 2-3x.
Granular permissions disappear
OpsGenie lets you control who can edit which on-call schedule. JSM does not have the same permission model. Custom roles that do not map cleanly get downgraded to "User." You fix them one by one.
Slack integration gets worse
OpsGenie's Slack integration was basic but it worked. JSM's Slack support is noisier and harder to filter. One team on Reddit described building "a patchwork of custom bots" to get back to where they were.
The mobile app is gone
OpsGenie's mobile app is being phased out. You switch to the Jira app. Atlassian recommends uninstalling OpsGenie to avoid duplicate push notifications. Your on-call engineers need to learn a new app mid-rotation.
No Terraform migration path
The OpsGenie Terraform provider (terraform-provider-opsgenie) has no JSM equivalent. Atlassian has published zero IaC migration guidance. If your on-call config is managed as code, you are rebuilding it from scratch.
Sources: Atlassian Community forums, Reddit /r/sysadmin, InfoQ, Rootly, ServiceRocket, Seibert Group. Migration timelines from teams who have completed the process.
You do not have to go to JSM
The shutdown is mandatory. Staying in the Atlassian ecosystem is not.
If you chose OpsGenie because it was simple and standalone, JSM is the opposite of what you wanted.
JSM bundles service desk, asset management, change management, and ITSM into one product. Your engineers need on-call schedules and incident management. That is it. The shutdown is forcing a decision. Use it to pick the tool your team actually needs, not the one Atlassian wants to upsell you into.
Runframe vs OpsGenie
What each product does today, and what happens after April 2027.
| Feature | Runframe | OpsGenie |
|---|---|---|
| Product Status | Active development | Shutdown April 2027 |
| Incident Management | ||
| On-Call Scheduling | ||
| Escalation Policies | ||
| Slack-native Workflow | Full lifecycle in Slack | Notifications only |
| Postmortems | Auto-generated from timeline | |
| Standalone Product | Being killed | |
| Alert Data Retention | Retained | JSM auto-deletes |
| Terraform / IaC Support | API-first | Provider abandoned |
| Pricing | $15/user/mo | End of sale (JSM: $17-46/agent/mo) |
| Setup Time | < 10 minutes | N/A (cannot purchase) |
| Free Tier | Up to 5 users | N/A |
OpsGenie end-of-sale June 4, 2025. JSM pricing from Atlassian documentation as of Q1 2026.
Where each tool is better
We are not going to pretend we win on everything.
Where Runframe wins
- The product is alive. Independent roadmap, shipping weekly, not being sunset.
- Incidents run in Slack. Slash commands, buttons, severity changes. No browser tab.
- Set up in under 10 minutes. No Atlassian tenant to configure.
- $15/user/mo flat. You are not paying for a service desk you will never open.
- Your incident data stays for as long as you have an account.
- Postmortems are auto-generated from the incident timeline when you resolve.
- Full API for managing config programmatically.
Where OpsGenie wins (while it lasts)
- Phone and SMS paging. Runframe does Slack DM and email. No voice calls.
- More third-party integrations. OpsGenie had years to build them.
- Better fit if your team is deep in Jira, Confluence, and Statuspage.
- More enterprise reference customers, though the product is now end-of-life.
OpsGenie shutdown: common questions
OpsGenie has an expiration date. Your incident process does not.
Free for up to 5 users. No credit card. Set up in under 10 minutes.