Last updated: 2026-05-29
OpsGenie is shutting down.
Atlassian stopped new account creation on June 4, 2025. The product is in maintenance mode — no new features, limited support. Full shutdown is April 5, 2027 — as of May 2026, roughly 10 months away.
If your team relies on OpsGenie for on-call scheduling and alert routing, you need to migrate before the service goes dark. But the story behind why this happened matters just as much as the deadline — because it explains why many teams started looking for alternatives years ago.
The 2022 outage changed everything. From April 4 to April 18, 2022, Atlassian’s entire cloud platform went down for 13 days after a faulty script deactivated roughly 400 enterprise accounts. OpsGenie — the tool whose entire job is to alert you when things go wrong — was unreachable for all 13 days. Atlassian provided no human contact to most affected customers until day seven or later and published no post-mortem explaining why restoring an incident alerting tool wasn’t a priority. Many teams migrated to PagerDuty directly after that outage. The March 2025 shutdown announcement was the confirmation, not the surprise.
This guide covers the full alternatives landscape, what the migration actually involves, and how to pick the right tool for your team.
Related reading: For the full Atlassian stack comparison including Statuspage and monitoring gaps, see Atlassian Statuspage vs StatusPage.me. For on-call operating models, see the On-Call Rotation Guide and On-Call Escalation Policies Explained.
Timeline: What Happens Between Now and April 2027
| Date | Event |
|---|---|
| September 2018 | Atlassian acquires OpsGenie for ~$295M |
| April 4–18, 2022 | 13-day Atlassian cloud outage — OpsGenie unreachable the entire time |
| October 2024 | Atlassian raises cloud prices 5–20%, including OpsGenie |
| March 4, 2025 | End of Sale announced — consolidation into JSM and Compass |
| June 4, 2025 | End of Sale effective — no new accounts, no upgrades/downgrades |
| Now → April 2027 | OpsGenie in maintenance mode — no new features, limited support |
| April 5, 2027 | OpsGenie shuts down completely. All data deleted. |
There is no extension announced. Teams that have not migrated by April 5, 2027 will lose on-call schedules, escalation policies, alert routing rules, and integrations without warning.
Why Atlassian Killed OpsGenie
Atlassian acquired OpsGenie in September 2018 for approximately $295 million with plans to fold it into a new product called “Jira Ops.” Those plans stalled. OpsGenie continued as a standalone product for years but received minimal investment relative to its importance — a pattern that became visible in April 2022.
The 2022 outage is the defining event. A faulty internal script intended to deactivate one obsolete app version instead deactivated approximately 400 enterprise accounts across all Atlassian cloud products. Affected customers included companies with 50,000 to 800,000 end users. OpsGenie was down for the full 13 days. Atlassian’s incident response — for an incident management company — was widely criticized: most customers received no human contact until day seven, and Atlassian published no post-mortem explaining why restoring the alerting tool was not treated as a priority.
The trust damage was permanent for many teams. Discussion threads from 2023 and 2024 on Hacker News and Reddit routinely referenced the 2022 outage as the reason teams were already evaluating alternatives before the shutdown was announced.
In October 2024, Atlassian raised cloud prices 5–20% across all products. In March 2025, they announced End of Sale. The framing was “consolidation to reduce tool sprawl” into JSM and Compass — but for engineering teams that deliberately chose OpsGenie over ITSM-heavy tooling, being pushed into JSM read as a forced downgrade, not an upgrade.
The practical implication for your migration: Teams burned by the 2022 outage now worry about single-vendor concentration risk. If you are choosing a replacement, the acquisition history of alternatives matters — see the risk notes in the alternatives table below.
What Must Be Migrated
Atlassian’s migration tool (Settings > Migrate Opsgenie) handles basic schedules and simple routing rules automatically. Everything else typically requires manual recreation.
Automatic migration (Atlassian tool)
- Basic on-call schedules
- Simple routing rules
Manual recreation required
- Escalation policies with complex conditions
- Third-party integrations (Datadog, PagerDuty webhooks, custom notification templates)
- Multi-team configurations
- Custom alert routing logic
In practice, the migration is more involved than Atlassian’s documentation implies. Most teams with non-trivial configurations hit a manual intervention step that the automated tool cannot handle.
OpsGenie’s Final Pricing (for comparison context)
Before evaluating alternatives, it helps to know what OpsGenie cost at End of Sale:
| Plan | Annual billing | Monthly billing |
|---|---|---|
| Free | $0 (up to 5 users) | $0 (up to 5 users) |
| Essentials | $9.45/user/mo | $11.55/user/mo |
| Standard | $19.95/user/mo | $24.15/user/mo |
| Enterprise | $31.90/user/mo | $38.50/user/mo |
The Essentials tier was frequently described as arbitrarily limited — the realistic entry point for professional on-call was Standard at $19.95/user/month. A 10-person team on Standard paid roughly $200/month on annual billing before the October 2024 price increase. After the increase, effective costs rose by 5–20%.
Full Alternatives Landscape
Before diving into detailed comparisons, here is the full picture of where teams are migrating. Pricing verified May 2026 — verify current rates at each vendor’s pricing page before committing.
| Tool | Model | Starting price | Best for | Risk flag |
|---|---|---|---|---|
| Jira Service Management | ITSM suite | Free (3 agents); ~$17.65/user/mo Standard | Teams already on Atlassian stack | Same vendor as OpsGenie |
| PagerDuty | On-call + AIOps | $25/user/mo Professional | Large SRE teams, complex AIOps | Most expensive option; add-ons push cost much higher |
| Grafana Cloud IRM | Cloud on-call | Free (3 users); $20/user/mo + $19/mo Pro | Grafana stack users | Open-source Grafana OnCall archived March 24, 2026 |
| incident.io | Slack-native IRM + on-call | ~$25/user/mo (IRM) + ~$20/user/mo (on-call) | Slack-heavy 50–500 eng teams | Higher combined cost |
| Squadcast | On-call + SLO + status | Free (5 users); Pro ~$9–19/user/mo | Budget-conscious teams | Acquired by SolarWinds, March 2025 |
| FireHydrant | Structured incident workflows | From $6,000/year | Teams needing rigorous postmortems | Acquired by Freshworks, December 2025 |
| StatusPage.me | Monitoring + status pages + on-call | $49/mo flat (Team) | Teams wanting consolidated stack | — |
Acquisition risk note: 2025 saw two significant acquisitions in this space. Squadcast was acquired by SolarWinds on March 3, 2025 — SolarWinds was the target of the high-profile 2020 supply chain attack. FireHydrant was acquired by Freshworks in December 2025 with product roadmap details still uncertain. Teams wary of vendor concentration risk after the OpsGenie situation should factor this in.
Grafana OnCall note: The open-source, self-hosted Grafana OnCall project was archived on March 24, 2026. The escape valve of “self-host for free” is now closed. Grafana Cloud IRM is the only supported Grafana on-call product.
PagerDuty
PagerDuty is the most direct feature-for-feature replacement for OpsGenie and the most expensive. Professional plan is $25/user/month ($21 annual); Business is $49/user/month ($41 annual). Enterprise add-ons for AIOps, status pages, and advanced analytics push costs significantly higher. PagerDuty has an official OpsGenie migration guide that can import schedules and escalation policies. Best choice for large SRE teams with complex service dependency maps who have the budget for it.
Grafana Cloud IRM
Grafana Cloud IRM is the successor to Grafana OnCall, now hosted exclusively in Grafana Cloud. The free tier covers up to 3 active users; Pro is $20/active user/month plus a $19/month platform fee. For teams already running Grafana dashboards and alerting, the stack integration is tight and the migration path from OpsGenie is documented. For a 50-person on-call team this runs roughly $1,000/month. Not worth the switching cost if you are not already invested in the Grafana stack.
incident.io
incident.io is purpose-built for Slack-native incident coordination. The product bundles incident management and on-call scheduling but prices them separately — approximately $25/user/month for IRM plus $20/user/month for on-call. At $45/user/month combined for a 20-person team, the annual cost approaches $10,800. The post-incident analysis tooling and Slack workflow depth are genuinely superior to most competitors. Best fit for engineering organizations between 50 and 500 people where incident coordination happens entirely in Slack.
Squadcast
Squadcast is the budget option but carries acquisition risk. Pricing runs from free (5 users) through $9–19/user/month depending on tier. The product bundles on-call scheduling, SLO tracking, and status pages at every tier — similar breadth to StatusPage.me. The SolarWinds acquisition (March 2025) is the main concern: teams already rattled by a vendor killing their tool may not want to hand the replacement to a company with its own trust issues.
Path A: Migrate to Jira Service Management
Atlassian’s official replacement for OpsGenie is Jira Service Management. On-call scheduling is included in the Standard tier.
JSM pricing for on-call
| Tier | Cost | Notes |
|---|---|---|
| Free | $0 | Up to 3 agents |
| Standard | ~$17.65/user/mo | Per-user pricing above 3 agents; verify current rates at atlassian.com |
A 3-person engineering team can run on-call on JSM Free. A 10-person team pays per-user pricing for Standard — roughly $176/month, modestly less than what OpsGenie Standard cost at $19.95/user/month, though JSM pricing does change.
What JSM covers
- On-call scheduling
- Escalation policies
- Alert routing
- Native Jira issue linking
What JSM does not cover
JSM is an IT service management platform first. It does not include:
- Uptime monitoring
- Status pages
- Multi-region monitoring checks
Teams using OpsGenie alongside Atlassian Statuspage will still need a separate monitoring tool and a separate status page product. That means adding a Datadog, Pingdom, or similar subscription on top of JSM.
The ITSM mismatch problem: Many engineering teams chose OpsGenie specifically to avoid ITSM tooling. JSM is optimized for ITIL workflows — ticket queues, SLAs, change management. Developer-centric SRE teams frequently find the interface heavier than OpsGenie was, and the on-call features feel like an appendage to the platform rather than its core purpose.
Path B: Migrate to StatusPage.me
StatusPage.me bundles uptime monitoring, status pages, incident management, and on-call scheduling in a single product. On-call scheduling is available on the Team plan ($49/mo) and above.
StatusPage.me on-call features (Team plan and above)
- Daily, weekly, or custom-duration rotations
- Timezone-aware scheduling (IANA timezone support)
- Multi-level escalation policies (L1 → L2 if no acknowledgment within configured window)
- iCal export for calendar visibility
- Shift-start notifications
- Visual schedule timeline
- Override conflict detection
- One-click acknowledgment from the alert email — no app login required
What the migration looks like
There is no automatic import from OpsGenie. You will manually recreate:
- On-call schedules
- Escalation policies
- Team member assignments
- Notification channels
The tradeoff is that you also gain built-in monitoring and a status page without separate subscriptions.
Pricing comparison for a 10-person team
| Stack | Monthly cost | What’s included |
|---|---|---|
| JSM Standard + Atlassian Statuspage Business + monitoring | ~$550–$650 | On-call + status page + monitoring via 3 separate tools |
| PagerDuty Professional (10 users) | ~$210–$250 | On-call + AIOps only — no status page, no monitoring |
| Squadcast Pro (10 users) | ~$90–190 | On-call + SLO + status page bundled |
| StatusPage.me Business | $99 | Monitoring + status page + on-call in one product |
JSM and PagerDuty pricing is per-user. StatusPage.me pricing is flat per plan regardless of team size — a 20-person team pays the same as a 10-person team.
On-Call Feature Comparison: JSM vs StatusPage.me
| Feature | Jira Service Management | StatusPage.me |
|---|---|---|
| On-call scheduling | Standard tier and above | Team ($49/mo) and above |
| Escalation policies | Yes | Yes — multi-level |
| Pricing model | Per-user above 3 agents | Flat per plan |
| iCal export | Yes | Yes |
| Timezone-aware scheduling | Yes | Yes (IANA) |
| Shift-start notifications | Yes | Yes |
| Visual schedule timeline | Yes | Yes |
| Override conflict detection | Yes | Yes |
| One-click email acknowledgment | Yes | Yes |
| Built-in uptime monitoring | No | Yes — 8 monitor types |
| Built-in status page | No | Yes |
| Multi-region monitoring | No | Yes — 4 to 9 locations |
| 30-second check intervals | No | Team and Business plans |
| Jira integration | Native | No |
| Notification channels | Email, SMS, Slack, webhooks | Email, Slack, Discord, Telegram, SMS, Mattermost, Rocket.Chat, PagerDuty, webhooks (plan-dependent) |
Decision Framework: Which Path to Choose
Choose Jira Service Management if:
- Your team is already deep in the Atlassian stack (Jira, Confluence, Statuspage)
- Native Jira issue linking for incidents is non-negotiable
- Your on-call rotation is 3 people or fewer (JSM Free covers this)
- You are comfortable managing monitoring and status pages as separate tools
Choose PagerDuty if:
- You run a large SRE org (20+ people in on-call) with complex service dependency maps
- You need enterprise AIOps or advanced analytics
- Budget is not a primary constraint
Choose Grafana Cloud IRM if:
- You are already running Grafana dashboards and alerting
- You want tight native integration between metrics and on-call routing
- You do not need a built-in status page
Choose incident.io if:
- Your incident coordination happens entirely in Slack
- Post-incident analysis and retrospective tooling are a priority
- Your team is between 50 and 500 engineers
Choose StatusPage.me if:
- You want on-call scheduling, uptime monitoring, and a status page under one subscription
- Your team has more than 3 people in on-call rotations and per-user pricing creates budget unpredictability
- You need monitoring checks from multiple regions with 30-second intervals
- Your team uses Discord, Mattermost, Telegram, or PagerDuty for alerting and needs native support
Avoid StatusPage.me if:
- Jira integration for incident management is non-negotiable
- Your procurement process requires a vendor with a longer compliance history
Avoid JSM if:
- You need built-in uptime monitoring without purchasing a separate tool
- Your team is larger than 3 agents and per-user pricing creates budget unpredictability
- You want a single product for monitoring, status pages, and on-call
Migration Checklist
Use this checklist whether you are moving to JSM, PagerDuty, Grafana Cloud IRM, incident.io, Squadcast, or StatusPage.me.
1. Inventory what you have in OpsGenie
- List all on-call schedules
- Document escalation policies (including complex conditions)
- Catalog third-party integrations (Datadog, PagerDuty webhooks, custom templates)
- Map alert routing rules
- Note multi-team configurations
- Export team member list with roles
2. Decide on notification channels
- Confirm which channels each team member needs (email, SMS, Slack, etc.)
- Verify Slack/Discord workspace permissions for bot integrations
- Test PagerDuty or webhook endpoints if used
3. Recreate schedules in the new tool
- Build primary rotations
- Add secondary/backup coverage
- Set timezone preferences per team member
- Configure escalation windows (e.g., L1 ack within 15 minutes or escalate to L2)
4. Test before going live
- Trigger a test alert
- Verify the correct person is paged
- Verify escalation fires if the first responder does not acknowledge
- Confirm notification channels deliver messages
- Run a full rotation cycle in parallel with OpsGenie before cutting over
5. Communicate the change
- Notify the team of the new tool and schedule
- Update runbooks and documentation
- Add the new on-call schedule link to shared team resources
Risks of Waiting
- The deadline is fixed. April 5, 2027 does not move. Teams that delay risk a forced, rushed migration.
- OpsGenie is in maintenance mode. If a bug or integration breaks between now and shutdown, there will be no fix.
- Migration complexity grows with team size. Larger teams with complex escalation policies need more time to rebuild and test.
- JSM is designed for IT service management. Developer-centric SRE teams may find the tooling heavier than OpsGenie was — worth validating before committing.
- Vendor concentration risk is real. Squadcast (SolarWinds), FireHydrant (Freshworks), and Grafana OnCall (archived) show the alternatives landscape is consolidating. Do your due diligence on whoever you pick.
Related Reading
- Atlassian Statuspage vs StatusPage.me: An Honest Comparison (2026)
- On-Call Rotation Guide for Small Engineering Teams
- On-Call Escalation Policies Explained
- On-Call Handoff Checklist
- Status Page Best Practices (2026)
- How to Reduce False Downtime Alerts (2026 Guide)
People Also Ask
Is OpsGenie really shutting down?
Yes. Atlassian stopped new OpsGenie account creation on June 4, 2025. The product is in maintenance mode with no new features and limited support. Full shutdown is April 5, 2027. Atlassian’s recommended migration path is Jira Service Management.
What do I need to migrate from OpsGenie?
On-call schedules, escalation policies, alert routing rules, and existing integrations. Atlassian’s migration tool handles basic schedules and simple routing rules automatically. Complex escalation policies, third-party integrations (Datadog, PagerDuty webhooks), and custom notification templates typically require manual recreation.
What are the best OpsGenie alternatives in 2026?
The main alternatives are Jira Service Management (Atlassian’s own migration target), PagerDuty (closest feature-for-feature replacement, most expensive), Grafana Cloud IRM (best for Grafana stack users), incident.io (best Slack-native option), Squadcast (budget option, SolarWinds-owned), and StatusPage.me (bundles on-call with monitoring and status pages at a flat rate).
Does Jira Service Management have a free tier for on-call?
Yes. Jira Service Management includes a free tier for up to 3 agents. Teams with more than 3 people in on-call rotations require the Standard tier — verify current per-user pricing at atlassian.com.
Can I migrate from OpsGenie to StatusPage.me?
There is no automatic import. You will manually recreate schedules, escalation policies, and team assignments. The tradeoff is that StatusPage.me bundles on-call scheduling with uptime monitoring and status pages in one product at a flat monthly rate.
How much does on-call scheduling cost after OpsGenie?
JSM Standard is approximately $17.65/user/month above 3 agents. PagerDuty Professional is $25/user/month. Grafana Cloud IRM Pro is $20/active user/month plus a $19/month platform fee. Squadcast Pro runs $9–19/user/month. StatusPage.me includes on-call on the Team plan at a flat $49/month regardless of team size.
Why did Atlassian shut down OpsGenie?
Atlassian acquired OpsGenie in 2018 and invested minimally in it for years. The April 2022 13-day cloud outage — which took OpsGenie offline for the full duration — severely damaged trust in the product. Atlassian cited “reducing tool sprawl” as the rationale for consolidating OpsGenie into Jira Service Management and Compass, but many teams read it as being forced from a specialized on-call tool into ITSM software they deliberately avoided.
FAQ
What is the exact OpsGenie shutdown date?
April 5, 2027. After this date, OpsGenie will no longer function and all data will be deleted.
What happens if I do not migrate by April 2027?
On-call schedules, escalation policies, alert routing rules, and integrations will stop working. There will be no grace period.
Does the Atlassian migration tool handle everything?
No. It handles basic schedules and simple routing rules automatically. Complex escalation policies, third-party integrations, custom notification templates, and multi-team configurations typically require manual recreation.
Is Jira Service Management the same as OpsGenie?
No. JSM is an IT service management platform. It includes on-call scheduling in its Standard tier, but the interface, workflow, and feature set are substantially different from OpsGenie. Teams that chose OpsGenie to avoid ITSM tooling may find JSM a poor fit.
Is Grafana OnCall still available?
The open-source, self-hosted Grafana OnCall project was archived on March 24, 2026 and is no longer maintained. Grafana Cloud IRM is now the only supported Grafana on-call product and requires a Grafana Cloud subscription.
Does StatusPage.me integrate with Jira?
No. StatusPage.me does not integrate with Jira or Confluence. Teams that require native Jira issue linking for incidents should use JSM or plan for manual workflow management.
Which StatusPage.me plan includes on-call scheduling?
The Team plan ($49/mo) and above. It is not available on the Free or Starter plans.
Does StatusPage.me include monitoring?
Yes. All plans include uptime monitoring with check intervals from 3 minutes (Free) to 30 seconds (Team and Business). Monitor types include HTTP/HTTPS, TCP, DNS, keyword, database, heartbeat, SSL certificate, and email authentication.
When should I start migrating?
Now. Complex configurations take time to rebuild and test. Starting early leaves room for parallel running, team training, and fixing integration issues before the deadline.
Tags: opsgenie, opsgenie alternatives, opsgenie shutdown, migration, on-call, jira service management, pagerduty, grafana oncall, statuspage alternative, incident management
