TL;DR
Atlassian is shutting down OpsGenie on April 5, 2027, and will delete all non-migrated data after the deadline. If you need a standalone replacement with familiar on-call and alerting workflows, Spike is the closest match at $7/user/month, and OpsGenie users get 50% off their first six months.
The OpsGenie shutdown timeline
Atlassian has set two critical dates for the OpsGenie end of life:
| Date | What Happens |
|---|---|
| June 4, 2025 | New sales stopped. No new purchases, trials, or plan changes for existing users |
| April 5, 2027 | Full shutdown. All access ends and Atlassian deletes non-migrated data |
The platform is now in maintenance-only mode. That means no new features, no new integrations, and limited bug fixes. If something breaks between now and April 2027, your support options are minimal.
You can still renew your current subscription until the shutdown date, but you cannot upgrade, downgrade, or change plans in any way.
What happens to your OpsGenie data
When the shutdown date hits, Atlassian will delete all data from accounts that have not completed migration. That includes your on-call schedules, escalation policies, alert history, user configurations, and integration settings.
Here is what you can export before the deadline:
- Escalation policies, on-call schedules, and user lists through OpsGenie’s REST API
- Alert history through the API and the built-in export settings
- Team configurations and routing rules through the API
Here is what you cannot export directly:
- Integrations: They rely on API keys and webhook URLs tied to your specific OpsGenie account. Each integration needs to be manually reconfigured in whatever platform you move to.
- Slack configurations: The Slack app connection is specific to OpsGenie and cannot be transferred. You will need to set up Slack integration from scratch in your new tool.
- Notification preferences: Individual user notification rules do not export. Each team member will need to reconfigure their personal alert preferences.
Start this process early. Exporting data under deadline pressure is how teams lose configurations they assumed were backed up.
Key point: Atlassian deletes all non-migrated OpsGenie data after April 5, 2027. Integrations, Slack configurations, and user notification preferences cannot be exported and must be manually reconfigured in your new platform.
But why is Atlassian shutting down OpsGenie?
Atlassian acquired OpsGenie in 2018 for $295 million. At the time, it was a clean addition to the Atlassian portfolio alongside Jira and Confluence.
Since then, Atlassian’s strategy has shifted toward consolidation. Rather than maintaining standalone products, they want everything folded into Jira Service Management. OpsGenie as a standalone alerting and on-call platform no longer fits that roadmap.
The move makes business sense for Atlassian, but it leaves thousands of DevOps and SRE teams with a forced migration.
What Atlassian recommends: Jira Service Management
Atlassian’s official migration path is Jira Service Management (JSM). They position JSM as the natural successor to OpsGenie because it includes on-call scheduling, alerting, and incident management features.
For some teams, JSM genuinely makes sense. If you already run Jira, Confluence, and other Atlassian products, JSM slots into your existing ecosystem without adding another vendor.
But JSM is not a lateral move from OpsGenie for most teams. There are real tradeoffs to consider before committing:
- Higher pricing: OpsGenie Standard was $11.55/user/month. JSM Standard is $20/agent/month and Premium is $51.42/agent/month. Teams that only need on-call and alerting end up paying for a full ITSM platform they may never use.
- More complex setup: The interface is significantly more nested than OpsGenie. Adding something simple like contact methods is also not obvious. And setting up alert channels takes more steps than it should.
- No built-in status pages: JSM requires a separate Statuspage.io subscription ($29-$109/month) for external incident communication. Several OpsGenie alternatives include status pages in their base plans at no extra cost.
- Deeper ecosystem lock-in: Moving to JSM ties more of your incident management stack to a single vendor. If you ever need to switch again, the migration will be more complex than the one you are facing now.
| Factor | OpsGenie (was) | JSM |
|---|---|---|
| Starting Price | $11.55/user/month | ~$20/agent/month |
| Primary Focus | Alerting and on-call | Full ITSM platform |
| Status Page | Not included (Statuspage.io add-on) | Not included (Statuspage.io add-on) |
| Setup Complexity | Simple, focused | Nested, multi-layered |
Key point: JSM works well for teams already invested in Atlassian’s ecosystem. For teams that just need alerting, on-call scheduling, and incident management, it is more complex and more expensive than what they had with OpsGenie.
OpsGenie alternatives worth considering
If JSM does not feel like the right fit, there are several standalone incident management platforms that match OpsGenie’s core workflows more closely. Here is a quick comparison:
| Tool | Best For | Starting Price |
|---|---|---|
| Spike | Teams migrating from OpsGenie who want a familiar setup, built-in status pages, and straightforward pricing | $7/user/month |
| PagerDuty | Enterprise teams that need deep ITSM integrations and have the budget to support premium add-ons | $25/user/month |
| Incident.io | Slack-heavy teams that want incident response to stay in chat | $19/user/month |
| Squadcast | Teams that want dual alert control, and are comfortable with SolarWinds as the parent company | $20/user/month |
| Zenduty | Teams that need affordable alerting, and can work without team-level alert control or a built-in status page | $6/user/month |
| xMatters | Enterprise teams with complex ITSM and automation requirements | $9/user/month |
| Splunk OnCall | Teams already running Splunk for observability | Custom pricing |
For a deeper evaluation of each platform with hands-on testing notes, pricing breakdowns, and pros and cons, read the full OpsGenie alternatives comparison.
Key point: Spike is the best OpsGenie alternative for DevOps and SRE teams that want familiar on-call and alerting workflows without the complexity of JSM. It starts at $7/user/month and gives OpsGenie teams 50% off their first six months.
The clock is running
OpsGenie is not going dark tomorrow, but April 2027 will arrive faster than most teams expect. The real risk is not the shutdown date itself, it’s the gradual decay between now and then. Integrations that break and do not get fixed. Support tickets that go unanswered. A platform in slow decline while your team depends on it for incident response.
The teams that will feel this least are the ones that start their audit now, pick a replacement before the deadline pressure builds, and migrate on their own terms. Waiting until late 2026 means migrating under stress, with fewer options and less time to test.
If you are ready to move, Spike offers 50% off first six months for OpsGenie teams.
FAQs
Can I still sign up for OpsGenie today?
No. Atlassian stopped new sales on June 4, 2025. OpsGenie is no longer available for new signups, trials, or purchases.
Will Atlassian extend the shutdown deadline beyond April 5, 2027?
Atlassian has not indicated any plans to extend the deadline. Given that new sales have already stopped, the April 2027 date appears final. Planning your migration around the confirmed date is the safest approach.
What happens if I do nothing before the shutdown?
Atlassian will delete your account and all associated data on April 5, 2027. You will lose your on-call schedules, escalation policies, alert history, user configurations, and integration settings with no way to recover them.
Can I still renew my OpsGenie subscription?
Yes, existing users can renew their current plan until the April 2027 shutdown. However, you cannot upgrade, downgrade, or change plans in any way. Renewals only extend access on your current tier.
Does OpsGenie still offer a free plan?
Yes, the free plan for up to 5 users still exists for current users. However, since new signups are no longer possible, the free plan is only accessible to teams already on it.
Will OpsGenie integrations stop working before the shutdown?
Not necessarily, but maintenance mode means broken integrations are unlikely to be repaired. If a monitoring tool changes its API and the OpsGenie integration breaks as a result, Atlassian will not fix it. Existing integrations that work today should continue working until the shutdown, but there are no guarantees.
Is my OpsGenie data safe until April 2027?
Atlassian has committed to maintaining data access until the shutdown date. However, sitting on data until the last minute is risky. Export your configurations and alert history well before the deadline rather than relying on continued access right up to April 5, 2027.
Do I need to formally cancel OpsGenie after migrating?
Yes. Once you have fully migrated to a new platform, cancel your OpsGenie subscription to stop being charged. Atlassian will not automatically cancel subscriptions when you stop using the platform.
What if my team is mid-contract with OpsGenie?
If you are on an annual contract, you are paid through the end of that term regardless. Contact Atlassian support about early termination options if your contract extends close to or beyond the April 2027 shutdown. Some teams choose to let the contract run while migrating in parallel.
Can Atlassian support help with the migration to a non-Atlassian tool?
No. Atlassian’s support for the migration process is focused on moving users to JSM. If you choose a different tool, you are responsible for the migration. Most standalone platforms like Spike have their own migration support teams that can help with the transition.
Which OpsGenie alternative is best?
Spike is the best OpsGenie alternative for most DevOps and SRE teams. It matches OpsGenie’s on-call scheduling, escalation policies, and alert workflows while adding built-in status pages and broader alert channels. It starts at $7/user/month, and OpsGenie users get 50% off their first six months.