OpsGenie is sunsetting.
Your on-call setup needs a new home.
The complete migration guide. Data export, honest alternative comparison, and a realistic plan to move your alerting and incident management before Atlassian pulls the plug.
Last updated: March 14, 2026
1. What's happening and why
On March 4, 2025, Atlassian announced that OpsGenie, the alerting and on-call management platform it acquired in 2018, will be discontinued. New sales ended on June 4, 2025. Existing customers have until April 5, 2027.
After April 5, 2027:
- All OpsGenie accounts will be permanently shut down
- API endpoints and webhooks will stop accepting alerts
- On-call schedules and escalation policies will stop working
- Integrations with monitoring tools (Datadog, Prometheus, CloudWatch, etc.) will break
- Mobile app notifications will stop
Atlassian is directing users toward Jira Service Management (JSM), which includes incident management features. For some teams, particularly those already deep in the Atlassian ecosystem, this makes sense. For many others, JSM is a full ITSM platform that adds complexity they don't need.
This guide covers both the JSM path and purpose-built alternatives. (For a general overview of what SaaS sunsets mean, see our glossary and survival guide.)
2. Key dates and timeline
13 months feels comfortable, but on-call migrations are uniquely risky. You cannot afford a gap in alerting coverage. Plan for at least 4 weeks of parallel running, and start evaluating alternatives now.
3. How to export your configuration
OpsGenie does not have a one-click "export everything" button. You need to use a combination of the UI, the API, and manual documentation.
Via the OpsGenie API
The OpsGenie REST API lets you programmatically export most configuration. Key endpoints:
- Teams:
GET /v2/teamsto list all teams and their members - Schedules:
GET /v2/schedulesfor on-call rotations - Escalation policies:
GET /v2/escalations - Routing rules:
GET /v2/teams/{id}/routing-rules - Integrations:
GET /v2/integrationsto list all connected tools - Users:
GET /v2/usersfor user list and notification preferences - Alerts:
GET /v2/alertsfor historical alert data
Write a script that calls each endpoint and saves the JSON responses. This is your migration blueprint.
Via the UI (manual documentation)
- Go to Teams and screenshot each team's configuration
- Go to On-call schedules and document every rotation (who, when, timezone, override rules)
- Go to Escalation policies and document each step (delay, target, repeat rules)
- Go to Integrations and list every connected monitoring tool with its configuration
- Go to Policies (alert policies, notification policies) and document the rules
- Check Heartbeat monitors if you use them for cron job / batch monitoring
4. What to save before it's gone
- On-call schedules (rotations, overrides, timezone settings, handoff times)
- Escalation policies (every step, delay, condition, and target)
- Routing rules (which alerts go to which team, based on what conditions)
- Integration configurations (every monitoring tool, webhook URL, API key, filtering rules)
- Alert policies (auto-close rules, priority mapping, deduplication settings)
- Notification preferences (per-user: SMS, email, push, call preferences and quiet hours)
- Heartbeat monitors (for cron job and batch process monitoring)
- Team structures (who is on which team, roles, permissions)
- Historical alert data (for post-incident analysis and SLA reporting)
- Maintenance windows (scheduled suppression rules)
- Custom actions (any custom alert actions or automation rules)
Integration configurations are the hardest part to recreate. For each monitoring tool connected to OpsGenie, document: what alerts it sends, what filters are applied, what priority mapping is used, and what team it routes to. This is the blueprint for your new setup.
5. Should you just use Jira Service Management?
Atlassian wants you to migrate to JSM. For some teams, that's the right call. For others, it's not. Here's an honest assessment.
JSM makes sense if:
- You already use Jira and Confluence heavily
- You need a combined ITSM + incident management platform
- You want to consolidate Atlassian billing
- You have a dedicated ITSM/platform team to manage JSM configuration
- Atlassian is offering you migration assistance or credits
JSM may not be right if:
- You used OpsGenie as a standalone alerting tool (JSM adds significant complexity)
- Your team values simplicity: JSM is a full ITSM platform, not a focused alerting tool
- You don't use Jira otherwise (adding Jira just for alerting is overkill)
- Cost is a concern: JSM pricing is per-agent, and you may end up paying for ITSM features you never use
- Your on-call team is small (5-15 engineers) and just needs reliable paging
JSM's incident management module has improved significantly, but it was built as an addition to an ITSM platform, not as a purpose-built on-call tool. Many Reddit threads from OpsGenie users report that the migration to JSM felt like trading a scalpel for a Swiss Army knife: more features, but worse at the specific job they needed done.
6. Alternative comparison
We compared five purpose-built alternatives to OpsGenie. Each focuses on alerting, on-call management, and incident response. All pricing is as of March 2026.
| Feature | PagerDuty | incident.io | Better Stack | Grafana OnCall | Squadcast |
|---|---|---|---|---|---|
| Starting price | Free (5 users), $21/user/mo | $19/user/mo | Free plan, $29/user/mo | Free (OSS), Cloud included | Free (5 users), $21/user/mo |
| On-call schedules | Advanced rotations | Schedule builder | Schedule builder | Calendar-based | Rotations + overrides |
| Escalation policies | Multi-level, conditional | Configurable | Multi-level | Escalation chains | Multi-level + round-robin |
| Alert routing | Event orchestration | Catalog-based routing | Rules-based | Routes + labels | Rules + tags |
| Integrations | 700+ | 50+ | 100+ | Native Grafana ecosystem | 100+ |
| Incident management | Built-in (full lifecycle) | Core strength (Slack-native) | Basic | Grafana Incident (separate) | Built-in |
| Status pages | Add-on | Built-in | Built-in | No | Built-in |
| Notification channels | SMS, call, push, email | Slack, email, push | SMS, call, push, email | SMS, call, push, Slack, Telegram | SMS, call, push, email |
| Self-hosted option | No | No | No | Yes (open source) | No |
| Best for | Enterprise, complex routing | Modern teams, Slack-heavy | Uptime + alerting combo | Grafana/Prometheus users | SMBs, cost-conscious |
7. Head-to-head: OpsGenie vs. each alternative
Select a tool to see how it compares directly to OpsGenie.
OpsGenie vs. PagerDuty
PagerDuty is the most mature incident management platform on the market. With 700+ integrations, it connects to virtually every monitoring tool your team uses. Event orchestration lets you build complex routing logic that goes beyond OpsGenie's capabilities. The analytics and reporting are deeper, with SLA tracking and operational reviews built in. If you had enterprise-grade OpsGenie, PagerDuty is the most direct lateral move.
PagerDuty is more expensive than OpsGenie was. The Professional plan at $21/user/month is comparable, but enterprise features (AIOps, event orchestration) push the price up significantly. The free tier is limited to 5 users. If you were on OpsGenie's $9/user/month Essentials plan, PagerDuty will be a cost increase. The platform has also become feature-heavy over the years, and some teams find it more complex than necessary for basic on-call.
OpsGenie vs. incident.io
incident.io is the modern alternative. It is Slack-native, meaning incidents are declared and managed entirely within Slack channels. On-call schedules, escalation policies, and alert routing are all built in. The product catalog lets you map alerts to services and teams in a way OpsGenie never quite nailed. Status pages are included. The UX is noticeably cleaner than OpsGenie's. If your team lives in Slack, incident.io feels like a natural extension of your workflow.
incident.io has fewer integrations than OpsGenie or PagerDuty (50+ vs 200+). If you rely on niche monitoring tools, check compatibility first. Phone call notifications are available but less central to the product than in PagerDuty or OpsGenie. It is a newer platform (founded 2021), so it may lack specific edge-case features you relied on. Teams not using Slack will miss the core value proposition.
OpsGenie vs. Better Stack
Better Stack combines uptime monitoring, on-call alerting, and status pages in one platform. If you were using OpsGenie for alerting plus a separate uptime tool (Pingdom, UptimeRobot), Better Stack consolidates both. The alerting is reliable with SMS, phone call, push, and email notification channels. Status pages are included and look professional out of the box. The on-call scheduling interface is clean and intuitive.
Better Stack's incident management is more basic than PagerDuty or incident.io. If you need complex multi-team escalation policies or detailed post-incident workflows, it may feel limited. The integration library is smaller. It is strongest as a combined monitoring + alerting platform for smaller teams. If you have 50+ engineers with complex routing needs, it may not scale as well.
OpsGenie vs. Grafana OnCall
Grafana OnCall is fully open-source and can be self-hosted at zero cost. If you already use Grafana and Prometheus (or Alertmanager), OnCall integrates natively with your existing observability stack. On-call schedules sync with Google Calendar or Outlook. Escalation chains are flexible. The Grafana Cloud version is included in the free tier with generous limits. For teams that value data sovereignty or operate in regulated environments, the self-hosted option is a major differentiator.
Grafana OnCall is tightly coupled with the Grafana ecosystem. If you don't use Grafana for dashboards and alerting, the integration advantage disappears. Self-hosting requires operational effort. The product is younger than PagerDuty and has fewer third-party integrations. Phone call and SMS notifications require a Twilio account for the OSS version. Enterprise features like RBAC require Grafana Cloud.
OpsGenie vs. Squadcast
Squadcast is the closest OpsGenie equivalent in terms of feature set and pricing. It covers on-call scheduling, escalation policies, alert routing, and incident management at a comparable price point. The free tier supports 5 users with full features. SLO tracking, runbooks, and status pages are built in. For teams that liked OpsGenie's balance of features and cost, Squadcast offers the smoothest transition.
Squadcast is a smaller company than PagerDuty or Grafana Labs. The integration library is growing but not as extensive. Enterprise references are fewer. If vendor stability and large-company backing matter to your procurement team, this could be a concern. The product is solid, but the ecosystem around it is smaller.
8. Our recommendation by use case
PagerDuty
You have 50+ engineers, complex escalation policies, and dozens of monitoring integrations. You need the deepest integration library and most mature platform.
incident.io
Your team lives in Slack. You want incidents declared and managed where the conversation already happens. Modern UX, growing fast.
Grafana OnCall
You already use Grafana for dashboards. You want native integration with your observability stack. Free to self-host, or use Grafana Cloud.
Squadcast
You want a full-featured OpsGenie replacement at a similar price. Free for 5 users, includes status pages and SLOs.
9. Migration walkthrough
On-call migrations are higher-risk than most SaaS migrations. A gap in alerting means missed incidents. Plan carefully.
Phase 1: Audit and document (Weeks 1-2)
- Export all OpsGenie configuration via API (see section 3)
- Document every integration: what monitoring tools send alerts, with what filters and priority mapping
- Map your team structure: who is on which on-call rotation, what are the escalation paths
- List all heartbeat monitors, maintenance windows, and custom actions
- Export historical alert data for trend analysis and SLA reporting
Phase 2: Evaluate and choose (Weeks 3-4)
- Sign up for free trials or free tiers of your top 2-3 choices
- Recreate one team's on-call schedule and escalation policy in each tool
- Connect one monitoring integration (e.g., Datadog or Prometheus) and verify alerts flow correctly
- Test notification delivery: does an alert actually reach the on-call person via SMS/call/push?
- Have the on-call team use it for one rotation and give feedback
Phase 3: Build the new setup (Weeks 5-8)
- Recreate all on-call schedules, escalation policies, and routing rules
- Reconnect all monitoring integrations to the new platform
- Configure notification preferences for every team member
- Set up heartbeat monitors, maintenance windows, and any custom actions
- Create or migrate status pages
Phase 4: Run in parallel (Weeks 9-12)
- Send alerts to BOTH OpsGenie and the new tool simultaneously
- Verify every alert arrives in both places with correct priority and routing
- On-call team responds via the new tool, but OpsGenie remains as a safety net
- Fix discrepancies: missed alerts, wrong routing, notification failures
- Run for at least 2-4 weeks of parallel operation before cutting over
Phase 5: Cut over and decommission
- Redirect all monitoring integrations to the new tool only
- Disable OpsGenie integrations (but keep the account active as read-only until shutdown)
- Update runbooks, documentation, and onboarding materials
- Notify the team that OpsGenie is no longer the primary tool
- Do a final export of any remaining data from OpsGenie
The parallel phase is not optional. On-call migrations have zero margin for error. A missed page during a production outage can mean real revenue loss. Run both tools for at least 2 weeks, ideally 4, before cutting over.
10. Frequently asked questions
When is OpsGenie shutting down?
Atlassian stopped selling OpsGenie to new customers on June 4, 2025. Existing customers have until April 5, 2027, when the product will be fully discontinued. Support continues until that date.
Should I just migrate to Jira Service Management?
It depends. JSM makes sense if you already use Jira and want a consolidated Atlassian stack. But JSM is a full ITSM platform, not a focused alerting tool. Many OpsGenie users report that JSM adds complexity they don't need. If your primary use case is on-call alerting and incident management, evaluate purpose-built alternatives alongside JSM. See our detailed JSM assessment above.
Will my OpsGenie integrations break on April 5, 2027?
Yes. All API endpoints, webhooks, and integrations will stop working on that date. Any monitoring tool (Datadog, CloudWatch, Prometheus, etc.) sending alerts to OpsGenie will need to be reconfigured to point to your new platform. Plan this carefully: each integration needs to be individually redirected.
How long does an OpsGenie migration take?
For small teams (5-10 users, simple routing): 1-2 weeks of setup plus 2 weeks parallel running. For mid-size teams (20-50 users, complex escalation policies, many integrations): 4-8 weeks. For enterprise (100+ users, custom API integrations, compliance requirements): 2-3 months. The parallel running phase is the biggest time investment.
Can I export my on-call schedules from OpsGenie?
Yes, via the API. Use GET /v2/schedules to export schedule definitions including rotations, participants, and timezone settings. There is no one-click UI export for schedules, so you'll need to script it or manually document each schedule.
What are the best free OpsGenie alternatives?
Grafana OnCall is fully open-source and free to self-host. PagerDuty and Squadcast both offer free tiers for up to 5 users. Better Stack has a free plan for small teams. Grafana Cloud includes OnCall in its free tier with generous limits.
What about Atlassian Compass?
Compass is Atlassian's developer experience platform, not a direct OpsGenie replacement. It includes a service catalog and can integrate with JSM for incident management, but it does not replace OpsGenie's core alerting and on-call features. Think of Compass as a complement to JSM, not an OpsGenie alternative.
I have OpsGenie Heartbeat monitors. What replaces those?
Heartbeat monitors (where OpsGenie expects a periodic ping from your cron jobs/batch processes) are available in PagerDuty, Better Stack, and Squadcast. Grafana OnCall does not have a direct equivalent, but you can achieve similar functionality with Grafana Alerting rules. If heartbeat monitoring is critical, verify the replacement supports it before committing.
More from SunsetProof
We publish independent guides for SaaS products being sunsetted. Each one includes data export walkthroughs, honest comparisons, and realistic timelines.
Delighted Migration Guide →
Sunsetting June 30, 2026. NPS/CSAT survey tool alternatives.
Microsoft Project Online Migration Guide →
Retiring September 30, 2026. Compare monday.com, Smartsheet, Asana, ClickUp, and Wrike.
Drift Migration Guide →
Salesloft is shutting down Drift. Compare Intercom, HubSpot Chat, and more.
Workplace from Meta Migration Guide →
Shutting down June 1, 2026. Enterprise communication alternatives.
SaaS Sunsetting Survival Guide →
The universal playbook. Works for any tool, any category, any deadline.
SaaS Sunset Tracker →
Regularly updated list of all SaaS products being retired in 2025-2027.
Sophos UTM 9 Migration Guide →
End of life June 30, 2026. Firewall and network security alternatives.
SharePoint & Exchange Server Migration Guide →
EOL July 2026. Microsoft enterprise collaboration alternatives.
SAP Marketing Cloud Migration Guide →
Sunsetting December 2026. Marketing automation alternatives.
QuickBooks Desktop 2023 Migration Guide →
End of support May 2026. Small business accounting alternatives.
The SaaSpocalypse Is Real (Blog) →
Data analysis: 47+ enterprise SaaS tools sunsetting in 2025-2027.
Atlassian Consolidation Playbook (Blog) →
Navigating the Atlassian ecosystem after OpsGenie sunset.
All Blog Posts →
Analysis and insights on the SaaS sunsetting trend.
⚠️ Get SaaS Sunset Alerts
We monitor the market so you don't get caught off guard. Early warning when tools you might use are shutting down.
No spam. Unsubscribe anytime. Free forever.