Which Opsgenie alternatives support automated voice calls?

PagerDuty, Rootly, Better Stack, Grafana Cloud IRM, Splunk On-Call, and Jira Service Management Premium support automated voice calls. AlertKick does not support automated voice calls.

Can I import my Opsgenie schedules and escalation policies automatically?

Self-serve importers are available for Atlassian Jira Service Management, incident.io, Grafana Cloud IRM, and AlertKick. PagerDuty and Rootly offer vendor-run migration services for qualifying customers. Better Stack, Spike.sh, Splunk On-Call, and GoAlert have no importers; you must rebuild configurations manually.

What is the cheapest Opsgenie alternative?

GoAlert is free and open source, but requires your own Twilio and SMTP infrastructure. AlertKick offers a Free plan for up to 2 users. Splunk On-Call starts at $5 per user per month for up to 10 seats.

What happens to my data if I do not migrate before the shutdown?

On 5 April 2027 Opsgenie shuts down and unmigrated data is deleted. Atlassian offers a data download for teams that do not migrate, so export before the deadline.

Does AlertKick support SAML SSO or SCIM?

No. AlertKick does not support SAML SSO or SCIM. It is also not SOC 2 certified and does not include postmortem templates or Jira links.

Opsgenie alternatives in 2026: on-call pricing and what imports from Opsgenie

Q: When does Opsgenie shut down?

Atlassian stopped selling Opsgenie on 4 June 2025. It shuts down on 5 April 2027, when access ends and data that has not been migrated is deleted.

Opsgenie shuts down on 5 April 2027. Atlassian’s recommended path is Jira Service Management. The other realistic alternatives for an Opsgenie team are PagerDuty, incident.io, Rootly, Better Stack, Grafana Cloud IRM, Splunk On-Call, Spike.sh, AlertKick, and self-hosted GoAlert.

The two things that separate these tools for a migrating team are whether on-call is included or sold as an add-on, and whether the tool can import Opsgenie schedules and escalation policies. The table below lists the cheapest plan with on-call and escalation for each vendor. Prices are as listed on each vendor’s own pricing page on 21 October 2026, USD unless noted; prices change.

Tool	Cheapest plan with on-call and escalation	Price per user per month	On-call included?	Opsgenie import
Jira Service Management	Standard (no voice calls) / Premium (voice, heartbeats)	$21.50 / $55.28 per agent	Yes	Atlassian’s in-app migration tool
PagerDuty	Professional	$25 monthly, $21 annual	Yes	Done by PagerDuty’s services team under a migration offer
incident.io	Team + On-call add-on	$15 annual ($19 monthly) + $10 on-call	Add-on	Self-serve: schedules, overrides, escalation policies
Rootly	On-Call	$20	Separate product	Done by Rootly’s team from a read-only API key
Better Stack	Responder license	$34 monthly, $29 annual	Yes	None found; rebuild by hand
Grafana Cloud IRM	Pro	$19 a month platform fee (3 active users), then from $20 per active user	Yes	Self-serve migration tool
Splunk On-Call	Starting tier	$5, billed annually, up to 10 seats	Yes	None found
Spike.sh	Standard	$7 billed monthly	Yes	None; 50% off the first six months for Opsgenie switchers
AlertKick	Free	Not per user: Free, £39 a month (5 users, 5 servers), £149 a month (25 users, 25 servers)	Yes, on every plan	Self-serve: users, schedules, escalation policies
GoAlert (self-hosted)	n/a, open source (Apache-2.0)	$0 plus your own Twilio and SMTP	Yes	None

When does Opsgenie shut down?

Atlassian stopped selling Opsgenie on 4 June 2025. Atlassian allows renewals only for terms ending before the final shutdown. On 5 April 2027 Opsgenie shuts down, access ends, and data that has not been migrated is deleted. Teams that do not migrate can download their data first.

The intended path is Jira Service Management. Atlassian includes an in-app migration tool for alerts, on-call schedules, escalation policies, and integrations. Opsgenie stays usable for 120 days after migration, then shuts off. Compass is the developer-focused alternative in the same ecosystem.

Moving to Jira Service Management changes notifications. Voice calls, heartbeats, incoming call routing, and alert policies are Premium or Enterprise only. Users must re-enter contact methods. API keys are replaced by Atlassian auth. REST integrations need updating for the new auth flow.

Jira Service Management

JSM is free for 3 agents, including alerts, on-call schedules, routing rules, and escalation policies. SMS on the Free tier is limited.

The Standard plan costs $21.50 per agent per month. It includes unlimited alerts, email, and SMS. It does not include voice calls.

The Premium plan costs $55.28 per agent per month. It adds voice calls, heartbeats, incoming call routing, and alert policies. Pricing is tiered by agent count, and Premium costs about 2.5 times the Standard price.

JSM is best for teams already on Jira and Confluence who want service desk and on-call in one Atlassian bill. Teams that require voice calls in their escalation chain must budget for Premium.

PagerDuty

PagerDuty is the incumbent with the largest integration catalogue.

The free plan covers up to 5 users, 1 on-call schedule, 1 escalation policy, and 100 SMS and phone notifications a month.

The Professional plan costs $25 per user per month billed monthly, or $21 billed annually. This includes email, push, SMS, and phone notifications. Status pages, AIOps, Runbook Automation, and live call routing are sold separately. Add-ons stack up.

PagerDuty offers a migration service for current Opsgenie customers buying a qualifying plan. PagerDuty’s services team migrates user profiles, contact methods, notification rules, teams, escalation policies, live on-call schedules, and baseline integrations. This covers up to 250 active users. The offer is valid for the first 50 customers until 1 June 2028.

No self-serve Opsgenie importer was found. Outside the offer, schedules and escalation policies are rebuilt by hand. The AlertKick vs PagerDuty page has the side-by-side.

incident.io

incident.io prices on-call as an add-on to its incident response platform. The base Team plan costs $19 per user per month, or $15 with the annual discount. The on-call add-on is $10 per user per month. The Pro plan is $25 plus $20 for on-call. A standalone On-call product is $20 per user per month.

The Basic plan is free. It includes single-team on-call, one schedule, and one on-call policy.

Channels include mobile push, phone, SMS, Slack, and email.

incident.io offers a self-serve import for Opsgenie data. You can import schedules, overrides, and escalation policies. The import is one-time. Users must already exist in incident.io before you run the import.

This tool suits Slack- or Teams-centric engineering orgs that want incident response, status pages, and on-call together.

On-call is priced on top of the response plan, so the real cost is the two numbers added together.

Rootly

Rootly splits incident response and on-call into separate products. Incident Response costs $20 per user per month. On-Call costs $20 per user per month. Running both together costs $40 per user per month. There is no free tier. Rootly offers a trial of about two weeks.

The On-Call plan supports SMS, voice, push notifications with Do Not Disturb bypass, Slack, and Teams paging. The plan caps schedules and escalation policies at 20.

Rootly handles the migration from Opsgenie for you. You provide a read-only Opsgenie API key. Rootly’s team imports users with their notification rules, teams, schedules with overrides, and future shifts. The process supports a dry run so you can verify the mapping before committing.

Rootly suits teams that want a hands-on, vendor-run migration.

Better Stack

Better Stack bundles uptime monitoring, status pages, incident management, and on-call into a single product. You pay for responders. Non-responder team members are free.

The Responder license costs $34 per month billed monthly, or $29 annually. This includes unlimited phone calls and SMS. The free plan covers 10 monitors and heartbeats, one status page, and Slack or email alerts.

Channels include phone calls, SMS, mobile push, email, Slack and Microsoft Teams. The tool does not have an Opsgenie importer. You must rebuild schedules and escalation policies by hand.

If you already use Better Stack for uptime monitoring or status pages, adding on-call keeps your tools in one place. The pricing scales with the number of responders, not the total headcount. This can be cheaper than per-user models if you have many stakeholders who do not need to receive pagers.

Better Stack works best for teams that want uptime monitoring, status pages, and on-call from one vendor.

Grafana Cloud IRM

Grafana Cloud IRM includes on-call. The free plan covers up to 3 active IRM users per month. The Pro plan costs $19 a month for the platform fee, which includes 3 active users. Additional active users cost from $20 each.

Grafana offers a self-serve migration tool for Opsgenie data. It imports notification rules, on-call schedules with overrides, escalation policies, and supported integrations. The tool does not support Opsgenie schedules with time-of-day or weekday restrictions. Some delay intervals round up; a 4-minute delay becomes 5 minutes.

Grafana OnCall OSS, the self-hosted version, entered maintenance mode on 11 March 2025 and was archived on 24 March 2026. It is not a destination for an Opsgenie migration. Teams needing self-hosting must look elsewhere.

This option fits teams already alerting from Grafana or Prometheus.

The Grafana OnCall archive guide covers what the OSS archive means for existing installs.

Splunk On-Call

Splunk On-Call (formerly VictorOps) is still sold. Pricing starts at $5 per user per month, billed annually, for up to 10 seats. Larger teams receive a custom quote.

The plan includes push notifications, SMS, voice calls, and email. There is a free trial, no free plan.

Migration from Opsgenie requires manual work. There is no automated importer for Splunk On-Call. Teams must rebuild schedules, escalation policies, and integration configurations by hand.

The tool suits existing Splunk customers who want to consolidate their monitoring and paging stack.

Watch out for the seat limit on the starting tier. The $5 price covers only 10 users. Adding more seats requires moving to a quoted plan.

Spike.sh

Spike.sh charges $7 per user per month billed monthly, or $14 for the Business tier. There is no free plan, but the vendor offers a 14-day trial. The Standard plan includes 100 phone and SMS alerts per month shared across the entire account. When that limit runs out, phone and SMS alerts pause. Slack, Teams, WhatsApp, Telegram, email, and Discord remain unlimited. The Business tier removes the SMS and phone cap.

Spike offers 50% off the first six months for teams switching from Opsgenie.

The tool has no Opsgenie importer. Teams must rebuild schedules and escalation policies by hand or use the Spike API.

The shared alert limit is the constraint to check. A team with high alert volume can use up 100 phone and SMS alerts in a month, and after that only the chat and email channels deliver until the allowance resets.

Spike.sh suits teams that rely heavily on chat-based paging (Slack, Teams, WhatsApp) and have low voice/SMS volume. Among the hosted options only Splunk On-Call starts lower per seat.

AlertKick

AlertKick charges per server, not per user. The Free plan supports 2 users. The Professional plan is £39 a month for 5 users and 5 servers. The Business plan is £149 a month for 25 users and 25 servers. On-call rosters and escalation policies are included on every plan. SMS and WhatsApp paging start on Professional.

Channels include mobile push, SMS, WhatsApp, Telegram, Slack, email and webhooks, chosen per escalation level. Critical alerts bypass Do Not Disturb on Android.

The self-serve importer takes an Opsgenie API key with read and configuration access. AlertKick fetches users, schedules, and escalation policies. It shows a preview of everything it will create and flags anything that does not map one-to-one. The key is not stored.

The gaps are plain: no automated voice calls, no SAML SSO or SCIM, no SOC 2 certification, and no postmortem templates or Jira links.

Uptime, SSL and heartbeat monitoring plus a server agent with SSH and runtime security detection are on the same plan, so the monitoring that fed Opsgenie can move to the same place.

The AlertKick vs Opsgenie page has the full side-by-side, and the migration walkthrough has the steps. What the importer maps lists every field.

GoAlert

GoAlert is an open-source, self-hosted alternative for teams that need on-call scheduling and automated escalations without paying per-seat licensing fees. Maintained by Target, the project uses the Apache-2.0 license. The latest release, v0.35.0, shipped on 21 September 2026.

The tool handles on-call scheduling, automated escalations, and notifications via SMS, voice, email, Slack, and webhooks. It does not include a built-in SMS or voice provider. You must supply your own Twilio account for text and call notifications, and your own SMTP server for email delivery. The application requires a Postgres database to store state.

There is no Opsgenie importer. You must rebuild schedules, escalation policies, and integration configurations manually or through the API.

The software costs nothing. Twilio usage and the SMTP server are the running costs.

GoAlert is best for teams that need self-hosting and have the capacity to run it. It has no vendor support contract and no migration help.

How to choose

The right tool depends on two constraints: whether voice calls are required in the escalation chain, and whether the team wants to run the migration or have the vendor do it.

Teams already using Jira for incidents and change management should start with Jira Service Management. It keeps service desk and on-call on one Atlassian bill. Voice calls, heartbeats, and incoming call routing require the Premium tier, which costs about 2.5 times the Standard price. If voice is not in the escalation chain, Standard covers it.

If voice calls are non-negotiable, the options are PagerDuty, Rootly, Better Stack, Grafana Cloud IRM, Splunk On-Call and Jira Service Management Premium. AlertKick does not place automated voice calls.

For a migration done by the vendor, PagerDuty’s offer and Rootly’s team both work from your Opsgenie account. To run the import yourself, use Atlassian’s in-app tool, incident.io, Grafana Cloud IRM or AlertKick.

When headcount grows faster than the server count, the pricing model matters more than the list price. AlertKick prices per server, not per user. Better Stack offers a Responder license where non-responder team members are free. Other tools charge per user, which can scale costs quickly as more engineers join the on-call rotation.

Before you pick anything

Export schedules, escalation policies and the integration inventory from the Opsgenie API now, whatever the destination. The export guide has the API calls, and the integration inventory lists what to record before anything moves.

Run the new tool in parallel with Opsgenie before the shutdown date. Do not cut over all alert sources at once. Move one service or integration at a time. This approach isolates failures. If the new pager does not trigger correctly for a specific alert type, the issue is contained to that single source. The rest of the on-call rotation continues to function through Opsgenie.

Keep Opsgenie running alongside the new tool until every alert source has moved and each escalation policy has paged the right person at least once. On Jira Service Management users re-enter their own contact methods, so check those first. The Opsgenie end-of-life guide has the full timeline.