Opsgenie alternative · dates checked September 2026
Opsgenie alternative: migrate before support ends on April 5, 2027
Atlassian has stopped selling Opsgenie and will switch it off on April 5, 2027. Here are the official dates, your options, and a step-by-step guide to moving schedules, escalations and alert sources to Oncallz — $4 per user a month.
When does Opsgenie shut down?
Opsgenie reaches end of support on April 5, 2027. Atlassian announced the retirement in March 2025:
-
End of sale
New purchases, sign-ups and edition changes are no longer available.
-
End of support
Access to Opsgenie is shut off. In Atlassian's words, "any unmigrated data in Opsgenie will also be deleted at this point."
Source: Atlassian's announcement "The evolution of IT operations" and the Opsgenie pricing page on atlassian.com, as of September 2026.
What are your options?
You can follow Atlassian's path or move to a separate on-call tool. Both are reasonable; they suit different teams.
Jira Service Management
Atlassian's recommended path. It now includes Opsgenie's alerting and on-call features, and Atlassian says alerts, schedules and policies are migrated automatically. Its docs map Opsgenie Essentials to JSM Standard and Opsgenie Standard to JSM Premium.
Best if you already run Jira Service Management or want one Atlassian bill.
Compass
Atlassian also lists Compass, its developer portal, as a destination on the Opsgenie pricing page, alongside Jira Service Management.
Worth a look if your team is already adopting Compass.
A standalone on-call tool
Tools like Oncallz do on-call scheduling, escalation and paging without a service desk attached. You recreate your setup yourself instead of using Atlassian's migration tool.
Best if you only used Opsgenie for on-call and alerting, and want a simpler, cheaper tool.
How do Opsgenie concepts map to Oncallz?
Most of what an Opsgenie on-call setup uses has a direct counterpart. Two things do not: heartbeats and per-user notification rules.
| Opsgenie | Oncallz | Notes |
|---|---|---|
| Teams | Teams | Each team has its own integrations, schedules and Slack or Microsoft Teams channel. |
| Schedules and rotations | Schedules with rotations | Daily, weekly, every N days, or several shifts a day. |
| Schedule overrides | Overrides | Cover a shift for someone without editing the rotation. |
| Escalation policies | Escalation policies | Steps with a delay, a target (on-call of a schedule, a team role or a user) and channels. |
| API / webhook integrations | Integrations | Each has its own ingest URL that accepts any JSON body. |
| Alert alias (deduplication) | dedup_key, or grouping by title or source ID | Repeated alerts fold into the open incident. |
| Acknowledge and close | Acknowledge and resolve | From the web app, the iOS app, or the phone call keypad; sources can also send resolve events. |
| Notification rules | Severity → channel settings | Set by an admin per severity and per escalation step, not per person. |
| Maintenance | Maintenance windows | Mute or lower matching alerts during planned work. |
| Alert policies | Partial: call-suppression rules | A regex rule can skip the phone call for matching alerts; there is no general alert-policy engine. |
| Heartbeats | Not available | Keep a separate heartbeat or cron monitor and have it send an alert to Oncallz when a check-in is missed. |
| Post-incident review | Post-mortems | With action items and an optional public incident report. |
Opsgenie to Oncallz: step by step
There is no Opsgenie importer, so plan to rebuild your setup by hand. For most teams that is a few hours of work.
-
Take an inventory
List every team, schedule, escalation policy and integration in Opsgenie. Screenshots or an export through the Opsgenie API are enough. Do it early: after April 5, 2027 the data is gone.
-
Invite users
Invite your responders from the Oncallz web app. Each person verifies a phone number for SMS and calls.
-
Recreate teams and schedules
Rebuild each rotation with the same order and hand-off time, then add upcoming overrides. Schedules can also be created through the REST API.
-
Rebuild escalation policies
Copy each policy's steps and delays. Point steps at a schedule's on-call, a team role or a named user.
-
Connect SMS and voice
Opsgenie sent SMS and calls for you. In Oncallz you connect your own Twilio account (SMS and calls) or Vonage account (SMS), then send a test SMS and call.
-
Re-point integrations
Create an Oncallz integration for each source and paste its URL into the monitoring tool's webhook settings, replacing the Opsgenie endpoint.
-
Run in parallel, then cut over
Send alerts to both for a week or two. Once every team has been paged in Oncallz, remove the Opsgenie integrations — well before April 2027.
How does the price compare?
Oncallz costs $4 per user a month. Opsgenie's list prices, still shown on Atlassian's site, start at $9.45 per user a month billed annually — though it can no longer be bought.
| Plan | Billed monthly | Billed annually |
|---|---|---|
| Oncallz (all features) | $4 / user (billed quarterly) | — |
| Opsgenie Essentials | from $11.55 / user | from $9.45 / user |
| Opsgenie Standard | from $24.15 / user | from $19.95 / user |
| Opsgenie Enterprise | from $38.50 / user | from $31.90 / user |
Opsgenie prices from atlassian.com/software/opsgenie/pricing as of September 2026 ("starting at", with volume discounts for larger teams). Jira Service Management is priced per agent on Atlassian's site; check its current pricing there. With Oncallz, add your own Twilio or Vonage usage for SMS and calls.
Frequently asked questions
When does Opsgenie stop working?
On April 5, 2027. Atlassian ended new sales on June 4, 2025 and ends support, and access, on April 5, 2027.
What happens to my Opsgenie data after April 5, 2027?
Atlassian says any data that has not been migrated will be deleted when Opsgenie is shut off. Export or record your schedules, policies and integrations before then.
Can Oncallz import my Opsgenie configuration?
No. There is no Opsgenie importer. You recreate teams, schedules and escalation policies in Oncallz, and schedules can be scripted through the REST API.
Does Oncallz have heartbeat monitoring like Opsgenie?
No. Keep a separate heartbeat or cron monitor and have it send a webhook to Oncallz when a check-in is missed; Oncallz then pages the on-call person.
Should I move to Jira Service Management instead?
If you already use Jira Service Management or want a service desk as well, Atlassian's automatic migration is the easier path. If you only used Opsgenie for on-call and alerting, a standalone tool like Oncallz is simpler and cheaper.
How much does Oncallz cost compared with Opsgenie?
Oncallz is $4 per user a month, billed quarterly. Opsgenie Essentials was listed from $9.45 per user a month billed annually ($11.55 monthly) as of September 2026. SMS and calls in Oncallz go through your own Twilio or Vonage account.
Keep reading
- PagerDuty alternative Compare Oncallz and PagerDuty: on-call schedules, phone/SMS paging and escalation with every feature included, for $4 per user a month.
- Escalation policies Multi-step escalation that climbs from the on-call engineer to the team and then leads, paging until someone acknowledges or the policy runs out.
- Phone & SMS alerting Page on-call engineers by phone call, SMS, push and email by severity — and let them acknowledge or escalate from the phone keypad.
Move off Opsgenie before the deadline
Start free, rebuild one team, and run it next to Opsgenie until you trust it.
Sources
Dates and prices on this page were checked on the pages below in September 2026.
- Atlassian: The evolution of IT operations (end of sale and end of support dates) https://www.atlassian.com/blog/announcements/evolution-of-it-operations
- Atlassian: Opsgenie pricing (dates, migration destinations, list prices) https://www.atlassian.com/software/opsgenie/pricing
- Atlassian Support: Options for migrating from Opsgenie (plan mapping, automatic migration) https://support.atlassian.com/opsgenie/docs/what-are-my-options-for-migrating-from-opsgenie/