When does Opsgenie actually stop working?

Atlassian stopped selling Opsgenie on 4 June 2025 and ends support on 5 April 2027. On that date access shuts off and, by Atlassian's own guidance, unmigrated data is deleted. Existing customers can only renew for terms ending before the deadline.

Is AlertKick a drop-in Opsgenie replacement?

For rosters, escalation policies, and paging, close to it: the importer reads Opsgenie schedules and policies and maps daily and weekly rotations, user and schedule targets, delays, and repeats directly. Multi-layer schedules import their primary layer; team targets, time restrictions, and notify-all rules are flagged in the preview. Voice calls and the Jira link do not carry across because AlertKick does not have them.

Why not just move to Jira Service Management?

If your incidents already live in Jira, do. It is the path Atlassian supports and the automated migration is thorough. The reason to look elsewhere is shape: Opsgenie was a standalone pager priced per user, JSM is a service-management suite priced per agent, and the tiers with alerting cost more per person than Opsgenie did. AlertKick keeps the standalone shape and prices per server.

What happens to my heartbeat monitors?

Recreate them as AlertKick heartbeats: an interval, a grace period, and a URL to ping from the job. A missed ping alerts the person on call through the same escalation policy. Separate start and fail pings are not supported yet.

Does AlertKick charge per user?

No. Each plan has a user allowance - 2 on Free, 5 on Professional, 25 on Business - and no per-seat charge. On-call and escalation are on every plan, including Free.

What does AlertKick not do that Opsgenie did?

Automated voice calls, a large integration catalogue, incident management with stakeholder notifications and postmortems, the Jira and Confluence links, SAML SSO and SCIM, and heartbeat start and fail pings. If those are requirements, Jira Service Management is the safer destination.

alternatives · alertkick vs opsgenie

Opsgenie is shutting down. Move the rota, not the whole ITSM suite.

Atlassian ended Opsgenie sales in June 2025 and ends support on 5 April 2027, when access stops and unmigrated data is deleted. The recommended path is Jira Service Management, a full service-management product priced per agent. AlertKick is the other option: a standalone pager, priced per server, with an importer that reads your Opsgenie schedules and escalation policies directly.

Start free Import from Opsgenie

Free plan · no card · commercial use allowed

Dates are from Atlassian's Opsgenie migration page: end of sale 4 June 2025, end of support 5 April 2027. Existing customers can renew only for terms ending before that date.

at a glance

What Opsgenie did, and what replaces it.

Opsgenie was a standalone alerting and on-call product. Jira Service Management absorbs those features into a suite. AlertKick keeps the standalone shape and adds the monitoring underneath.

	Opsgenie	AlertKick
Status	End of sale June 2025. End of support 5 April 2027: access shuts off and unmigrated data is deleted.	Actively developed. Public status page, agent code open on GitHub.
Pricing model	Was per user per month. The successor, Jira Service Management, is priced per agent, and the tiers that include alerting and on-call cost more per person than Opsgenie did.	Per server. Free, £39 a month for 5 hosts, £149 a month for 25 hosts. No per-seat line on any plan.
On-call schedules	Rotations with multiple layers, time restrictions, and participant types (users, teams, escalations, no-one).	Daily and weekly rotations of any length, a roster per team, overrides and paired swaps, timezone-aware handovers, calendar feeds. Hourly rotations, restrictions, and end dates are flagged in the import preview.
Escalation policies	Rules with delay, condition, notifyType, and repeat; targets of user, team, or schedule.	Levels with timeout and repeat, each on its own channel. User and schedule targets import directly; team targets, if-not-closed conditions, and notify-next or notify-all rules are called out in the preview.
Paging channels	Push, SMS, voice calls, email, and chat integrations, with per-user notification rules.	Mobile push (critical bypasses Do Not Disturb on Android), SMS, WhatsApp, Telegram, Slack, email, and webhooks, chosen per escalation level. No automated voice calls.
Alert sources	A large catalogue of integrations plus the Alert API.	28 sources: Prometheus Alertmanager, Grafana, Datadog, New Relic, CloudWatch, Azure Monitor, Google Cloud, Sentry, Zabbix, Nagios, Icinga 2, Checkmk, CI systems, email, and a generic webhook. Deduplicated per source with auto-resolve on recovery.
Heartbeats	Heartbeat monitors with an interval and an alert when a ping is missed.	Heartbeat monitors with an interval and grace period, alerting the person on call when a ping goes missing. No separate start and fail pings yet.
Monitoring	None beyond heartbeats; alerts come from tools you run separately.	Included on the same plan: uptime, SSL, DNS, and TCP checks, an agent for host metrics and containers, and eBPF security detection.
Incident workflow	Incident management, stakeholder notifications, and postmortems, with deep Jira links.	Alerts, incidents, acknowledge and resolve everywhere, maintenance windows, AI triage, and AI after-action summaries. No postmortem templates, incident roles, or Jira link.
Identity	Atlassian account with SAML SSO and SCIM through Atlassian Access.	Email, Google, and GitHub sign-in. No SAML or SCIM yet.
Migration	Atlassian's automated migration to Jira Service Management or Compass.	Import users, schedules, and escalation policies from Opsgenie with an API key that has read and configuration access. Preview everything first; the key is never stored.

AlertKick user allowances per plan are 2 (Free), 5 (Professional), and 25 (Business). They are allowances, not prices - nobody is billed per seat.

read this part first

Where Jira Service Management is the right destination.

Switching pagers to save money and then hitting a gap at 3 AM is a bad trade. If two or more of these apply, stay where you are.

Your team already lives in Jira

If incidents become Jira issues, postmortems are Confluence pages, and the service desk is JSM, the automated Atlassian migration keeps all of that connected. That is the lowest-friction path, and it is the one Atlassian will support.

Voice calls are in the escalation chain

Opsgenie placed automated voice calls, and JSM keeps that. AlertKick has no voice channel; its loudest step is SMS or WhatsApp alongside a critical push.

You depend on Opsgenie-specific integrations

Opsgenie had a large catalogue, much of it carried into JSM. AlertKick covers the common monitoring sources and a generic webhook; check your inventory against the list before deciding.

Procurement needs SAML, SCIM, and Atlassian-grade compliance

Atlassian Access provides SSO and provisioning, and the compliance paperwork is done. AlertKick is not SOC 2 certified yet and signs in with email, Google, or GitHub.

what changes when you switch

Where AlertKick is the better exit.

Teams that bought Opsgenie because it was a pager, not a service desk, and do not want the per-agent suite pricing that comes with the recommended path.

Keep the standalone shape

Rosters, escalation policies, and paging with nothing else bolted on. No agents to license, no service desk to configure, no Jira project required to receive a page.

The bill stops tracking headcount

Adding people to the rota costs nothing. On-call, escalation, and the alert sources are on every plan including Free; the paid plans buy monitoring for more servers and SMS and WhatsApp paging.

The importer reads Opsgenie directly

Paste a key with read and configuration access and AlertKick fetches users, schedules, and escalation policies, shows exactly what it will create, and explains every item that cannot map one-to-one before a single object exists.

The monitoring comes with it

Uptime checks, heartbeats, host metrics, and eBPF security detection are on the same plan, so the tools that used to feed Opsgenie can be consolidated later without another migration.

the maths for one team

A twelve-person rota with a deadline.

Take an Opsgenie team of twelve with two rosters, three escalation policies, and alerts arriving from Grafana and CloudWatch. Support ends on 5 April 2027; nobody wants to switch pagers in March.

Line	Jira Service Management path	AlertKick Business
On-call and escalation	12 agents on a tier that includes alerting and on-call, per agent per month	Included, up to 25 users
Schedules and policies	Atlassian's automated migration	Imported from the Opsgenie API with a preview of every mapping
Alert sources	Reconnect Grafana and CloudWatch to JSM	Reconnect Grafana and CloudWatch to AlertKick; both in the 28-source list
Monitoring the servers	Separate	Included: 25 hosts with the agent, 50 monitors and 50 heartbeats
Monthly total	Per-agent suite pricing, published by Atlassian	£149

The deadline is the point. Export schedules, escalation chains, and the integration inventory now - it takes about an hour and de-risks everything after it - then run the destination in parallel for a quarter and cut over source by source.

Jira Service Management pricing is per agent and published by Atlassian; it is not reproduced here because it changes by tier and region. AlertKick Business includes 25 users; Professional at £39 includes 5 users and 5 hosts.

how the move goes

The exit, in the right order.

step 1

Export while you still can

Pull schedules, escalation policies, and the integration inventory out of the Opsgenie API today. After 5 April 2027 the data is gone.
step 2

Preview the import

Create an Opsgenie API key with Read and Configuration Access, paste it on the AlertKick Migrate page, and read the preview: every roster and policy it will create, every mapping that needs a decision.
step 3

Import and reconnect one source

One click creates the rosters and policies. Point one alert source at AlertKick and press Send Test Alert on each policy to watch it page the right person.
step 4

Run in parallel, then decommission

Keep Opsgenie alongside for a few weeks, move sources one at a time, and decommission well before the deadline so the export never becomes a fire drill.

Questions teams ask before switching

When does Opsgenie actually stop working?: Atlassian stopped selling Opsgenie on 4 June 2025 and ends support on 5 April 2027. On that date access shuts off and, by Atlassian's own guidance, unmigrated data is deleted. Existing customers can only renew for terms ending before the deadline.
Is AlertKick a drop-in Opsgenie replacement?: For rosters, escalation policies, and paging, close to it: the importer reads Opsgenie schedules and policies and maps daily and weekly rotations, user and schedule targets, delays, and repeats directly. Multi-layer schedules import their primary layer; team targets, time restrictions, and notify-all rules are flagged in the preview. Voice calls and the Jira link do not carry across because AlertKick does not have them.
Why not just move to Jira Service Management?: If your incidents already live in Jira, do. It is the path Atlassian supports and the automated migration is thorough. The reason to look elsewhere is shape: Opsgenie was a standalone pager priced per user, JSM is a service-management suite priced per agent, and the tiers with alerting cost more per person than Opsgenie did. AlertKick keeps the standalone shape and prices per server.
What happens to my heartbeat monitors?: Recreate them as AlertKick heartbeats: an interval, a grace period, and a URL to ping from the job. A missed ping alerts the person on call through the same escalation policy. Separate start and fail pings are not supported yet.
Does AlertKick charge per user?: No. Each plan has a user allowance - 2 on Free, 5 on Professional, 25 on Business - and no per-seat charge. On-call and escalation are on every plan, including Free.
What does AlertKick not do that Opsgenie did?: Automated voice calls, a large integration catalogue, incident management with stakeholder notifications and postmortems, the Jira and Confluence links, SAML SSO and SCIM, and heartbeat start and fail pings. If those are requirements, Jira Service Management is the safer destination.