Opsgenie is shutting down. Atlassian stopped selling Opsgenie to new customers on June 4, 2025, and support ends completely on April 5, 2027. After that date, alerts stop routing, on-call schedules stop working, and your Opsgenie data is deleted. If your team still relies on Opsgenie for paging and on-call management, you need to pick a replacement and migrate before that deadline.
Short answer: you have four realistic destinations. Atlassian wants you to move to Jira Service Management. Enterprise teams often shortlist PagerDuty. Incident-focused teams look at incident.io or Rootly. Teams that live in Slack or Microsoft Teams and mainly need rotations, schedules, escalations, and paging can replace Opsgenie with Pagerly at a fraction of the cost, because Pagerly is priced per team instead of per user. Whatever you choose, start now: a clean migration takes 4 to 8 weeks for most teams, and the last quarter before the deadline will be crowded with everyone else doing the same thing.
| Destination | Best for | Pricing model | Migration effort |
|---|---|---|---|
| Jira Service Management | Teams deep in the Atlassian stack that want the official path | Per agent, per month | Low (automated by Atlassian) but feature gaps exist |
| PagerDuty | Large enterprises with complex event routing | Per user, about $21/user/month billed annually | Medium to high |
| incident.io / Rootly | Teams that want full incident management, not just paging | Per user or per responder | Medium |
| Pagerly | Slack-first and Teams-first teams that want rotations, escalations, and paging without per-user pricing | Per team, from $19/month | Low |
The Opsgenie end of life follows three fixed dates, confirmed on Atlassian's official migration page:
Two things make this deadline more urgent than it looks. First, Atlassian's automated migration path only covers moves into Jira Service Management or Compass. If you are going anywhere else, the export and rebuild work is entirely on you. Second, enterprise procurement and security review cycles routinely eat 2 to 3 months before any technical work starts. Teams that begin evaluating in mid 2026 are on a comfortable schedule. Teams that start in early 2027 are not.
This is not a soft deprecation where the product keeps limping along. When support ends:
For a team running production services, staying past the deadline is equivalent to turning off paging. That is why every migration plan in this guide ends with a parallel-run phase and a hard cutover date well before April 2027.
Before comparing vendors, inventory what you actually use. Most teams discover they use far less of Opsgenie than they pay for. Export or document each of the following:
The Opsgenie API can export most of this programmatically. Budget one afternoon for a full export and store it somewhere durable regardless of which destination you pick.
Atlassian has folded Opsgenie's alerting and on-call features into Jira Service Management and provides an automated migration for existing customers. If your engineering organization already runs on Jira and Confluence, this is the lowest-friction move, and your Opsgenie configuration transfers largely intact.
Pros: automated migration, single Atlassian bill, alerting sits next to your tickets.
Cons: JSM is a full IT service management suite, so teams that only used Opsgenie for paging inherit a much heavier product. Pricing is per agent, and several Opsgenie features map imperfectly. Community reports of migration friction are common enough that Atlassian maintains a dedicated migration support program.
Best for: organizations standardized on Atlassian that want the official, supported path.
PagerDuty is the incumbent in incident response, with the deepest event intelligence, event orchestration, and analytics in the market. It is also the most expensive mainstream option: the Professional plan runs about $21 per user per month billed annually, and the features most teams actually want (like advanced event orchestration) push you toward higher tiers.
Pros: mature, battle tested, 700+ integrations, strong enterprise controls.
Cons: per-user pricing gets expensive fast, and many Opsgenie refugees report paying 2x to 3x their old bill. See our full breakdown of why teams are leaving PagerDuty in 2026.
Best for: large enterprises with complex routing needs and the budget to match.
These platforms treat paging as one part of a broader incident management workflow: declaring incidents, assigning roles, running timelines, and generating postmortems. Both have added native on-call and paging in recent years specifically to catch Opsgenie migrations.
Pros: excellent Slack-based incident workflows, modern UX, strong postmortem tooling.
Cons: per-user pricing again, and the incident management surface may be more than a team that just needs rotations and paging wants to adopt. We compare these in detail in incident.io vs Opsgenie and Opsgenie vs Rootly.
Best for: teams whose real pain is incident coordination, not just alerting.
Pagerly takes a different approach: instead of being another dashboard you log into, it runs on-call management inside Slack and Microsoft Teams, where your responders already are. You get round-robin rotations, on-call schedules synced to Slack user groups, escalation policies, paging by SMS and voice call, incident workflows, and two-way sync with Jira and other tools.
The pricing model is the structural difference. Pagerly charges per team, not per user: the Basic plan is $19 per month per team and the Starter plan, which includes external integrations and user group sync, is $39 per month per team, with paging calls at $4 per user per month for the users who need them. A 25-person engineering organization that would pay roughly $2,835 per year on Opsgenie Standard (at its long-standing $9.45 per user per month price) can run Pagerly Starter for $390 per year on annual billing, a saving of about 86 percent before paging add-ons. Full details are on the Pagerly pricing page.
Pros: per-team pricing, native Slack and Teams experience, fast setup, covers the core Opsgenie use cases (rotations, escalations, paging, alert routing).
Cons: not aimed at enterprises that need deep event intelligence, noise reduction at massive alert volume, or on-premise deployment.
Best for: small and mid-sized teams that live in Slack or Teams and want to stop paying per seat for paging. See the full Opsgenie alternatives comparison.
When teams evaluate replacements, six criteria separate the contenders:
A realistic migration for a team of 10 to 50 engineers takes 4 to 8 weeks. Here is the sequence that avoids gaps in coverage:
The single most common migration failure is skipping the parallel run. Alert routing has silent edge cases, and the only way to find them is to let real alerts flow through both systems for a full cycle.
Pre-calculated for a 25-person engineering team, billed annually:
| Tool | Pricing basis | Annual cost (25 users) |
|---|---|---|
| Opsgenie Standard (legacy) | $9.45/user/month | about $2,835 |
| PagerDuty Professional | about $21/user/month | about $6,300 |
| Jira Service Management | per agent, tier dependent | comparable to or above Opsgenie |
| Pagerly Starter | $39/month/team ($390/year annual) | $390 plus $4/user/month paging for users who need calls |
Moving from Opsgenie to PagerDuty Professional roughly doubles the bill for this team, an increase of about $3,465 per year. Moving to Pagerly Starter cuts the base cost by about 86 percent, saving roughly $2,445 per year even before comparing against PagerDuty. Even with voice paging enabled for ten primary responders ($480 per year), the total stays under $900.
When exactly does Opsgenie shut down?
Opsgenie reaches end of support on April 5, 2027. After that date it stops routing alerts, and Atlassian deletes remaining customer data.
Can I still buy or renew Opsgenie?
New purchases and trials ended on June 4, 2025. Existing customers can use the product until the 2027 end-of-support date.
How long does a migration really take?
Plan 4 to 8 weeks for a mid-sized team: one week of inventory, one to two weeks of evaluation, two weeks of rebuild, and at least one full rotation cycle of parallel running.
Is Jira Service Management a full replacement for Opsgenie?
It covers most alerting and on-call features and has an automated migration, but it is a heavier ITSM product, and some Opsgenie behaviors map imperfectly. Teams that only used Opsgenie for paging often find lighter tools a better fit. See our guide to the best Opsgenie alternatives.
What is the cheapest serious Opsgenie replacement?
For teams under about 50 responders, per-team pricing beats per-user pricing decisively. Pagerly Starter at $390 per year per team is about 86 percent cheaper than what a 25-person team paid for Opsgenie Standard.
What should I export from Opsgenie before it is deleted?
Users and teams, schedules, escalation policies, routing rules, the integration list, notification preferences, and any alert history you need for compliance. Export everything even if your destination has an importer.
How do I avoid missing pages during cutover?
Run both systems in parallel for at least one full rotation, sending every alert to both, and only remove Opsgenie from the alert path after the new tool has matched it page for page.
Pagerly runs on-call rotations, escalations, paging, and incident workflows inside Slack and Microsoft Teams. Install it free, no credit card required, or see pricing.
