Opsgenie replacement
Why teams evaluate CallHeim as an Opsgenie replacement.
Atlassian stopped selling Opsgenie to new customers and has set a shutdown date, so every Opsgenie customer is moving somewhere. Here is why CallHeim ends up on that shortlist, what Atlassian's own route offers instead, and how a move to CallHeim actually works.
The dates that matter
- New sales ended
- 2025-06-04
- End of support
- 2027-04-05
Opsgenie ended new sales on 4 June 2025 (announced 4 March 2025): no new purchases, sign-ups or plan changes. (Atlassian Opsgenie licensing page, checked 2026-09-24)
Opsgenie end of support is 5 April 2027: access is shut off then, and data not migrated by that date is deleted. (Atlassian Opsgenie licensing page, checked 2026-09-24)
Existing customers can still renew (term ending before 5 April 2027) and add seats until that date; new customers cannot buy Opsgenie at all. (Atlassian Opsgenie licensing page, checked 2026-09-24)
Atlassian ended new sales — it has not said existing customers can no longer buy anything. Take an export well before the shutdown date rather than on it.
Competitor information last verified September 2026. Sources are linked beside each fact.
Your options
Where Opsgenie customers are moving.
We are not going to characterise Jira Service Management's feature set beyond what Atlassian itself publishes about the move. Evaluate it on its own merits; here is the shape of the decision.
Move within Atlassian
Atlassian’s licensing and migration pages name Jira Service Management as the successor; the Opsgenie pricing page still (as checked) says "Jira Service Management or Compass". (Atlassian Opsgenie licensing page, checked 2026-09-24)
Atlassian’s migration route is an automated tool (Settings > Plan your move) with no downtime, 120 days of parallel access and a 14-day migration trial; alerting and on-call ship in every JSM plan, and AI grouping and automation are Premium and Enterprise only. (Atlassian Opsgenie migration page, checked 2026-09-24)
Items that do not carry over unchanged to JSM: Incident Command Center, Edge Encryption, MSP sub-accounts, Heartbeats V1 and Policies V1; Opsgenie groups become JSM teams. (Atlassian Opsgenie deprecations documentation, checked 2026-09-24)
Move to another on-call tool
PagerDuty is the other well-known incumbent, and there are several smaller on-call and incident-response products in the market. Check each one’s own migration tooling before you decide.
Move to CallHeim
Import tooling (early access) reads your PagerDuty or Opsgenie configuration (US-region accounts); an optional dry run lets you review the result before anything is written to your workspace.
Run in parallel during a move: CallHeim receives PagerDuty Events API v1 and v2 bodies, Opsgenie outgoing webhooks, and alerts forwarded from Splunk On-Call, Squadcast, Zenduty and Grafana OnCall. Every sender needs a CallHeim integration URL and key; existing PagerDuty routing keys are not reused.
Migration
How the move to CallHeim works.
A parallel run first, then an import you can review before it changes anything.
1. Parallel run by forwarding
CallHeim accepts Opsgenie outgoing webhooks, so you can forward alerts to both platforms and compare before changing anything for your team.
2. A qualified importer
Import tooling (early access) reads your PagerDuty or Opsgenie configuration (US-region accounts); an optional dry run lets you review the result before anything is written to your workspace.
Read the full Opsgenie migration checklist →
More on the Opsgenie end-of-support timeline →
See how CallHeim compares with PagerDuty and Jira Service Management too →
Why it's worth a look
What CallHeim brings to the move.
Explainable alert handling
CallHeim’s alert handling is rule-based and deterministic: given the same alert, settings and state it makes the same decision, and no AI model reads your alert data today.
The thresholds behind the noise handling are published: a 300-second dedup window, a flap threshold of 4 state changes in 600 seconds, and title-similarity grouping at a default of 0.6.
Transparent, per-seat pricing
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Paid plans are activated directly by the CallHeim team.
14-day trial with up to 5 seats and no card required. Adding a user beyond a plan’s seat limit is refused (Trial 5, Starter 10, Pro 50, Business 200); existing users and paging are not affected.
Questions
About leaving Opsgenie.
Can I migrate from Opsgenie?
Atlassian ends Opsgenie support on 5 April 2027; data not moved by then is deleted. Import tooling (early access) reads your PagerDuty or Opsgenie configuration (US-region accounts); an optional dry run lets you review the result before anything is written to your workspace. CallHeim also accepts Opsgenie outgoing webhooks, so alerts can be forwarded to both platforms during a parallel run.
How does pricing work?
Starter $9, Pro $15 and Business $29 per user per month. Enterprise is negotiated. Paid plans are activated directly by the CallHeim team. Some features are tied to plan: the REST incident API and related-incident insights on Pro and above; email-to-alert (per-workspace inbound alert e-mail addresses) on Trial, Business and Enterprise, not Starter or Pro.
Is there a trial?
CallHeim is in early access. 14-day trial with up to 5 seats and no card required. Adding a user beyond a plan’s seat limit is refused (Trial 5, Starter 10, Pro 50, Business 200); existing users and paging are not affected.
Forward your alerts before you touch the configuration.
CallHeim helps teams stay in control when critical systems are not. Explore the platform, connect one source, and send yourself a page.
Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required