Opsgenie Is Shutting Down. What Small Teams Should Do Before April 2027

Atlassian is retiring Opsgenie. New sales have already stopped, and the service shuts down for good on April 5, 2027. If your team's on-call alerting runs through Opsgenie, you have a deadline — and, more usefully, you have a rare excuse to ask whether the tool you migrate to should look anything like the tool you're leaving.

Here's what's happening, what the default migration path costs, and what the decision actually looks like for a small team.

---

What's happening

Opsgenie was the approachable one: solid alerting, sane pricing, none of the enterprise ceremony. Atlassian bought it in 2018, and is now folding incident management into Jira Service Management and Compass. Existing customers keep working until the shutdown date; after April 5, 2027, Opsgenie is gone.

Atlassian's pitch is that JSM inherits the job. For teams already living in Jira, that may genuinely be the right answer — the migration tooling exists and the alerting features have been landing steadily.

The catch for small teams

Jira Service Management is an ITSM suite. It thinks in tickets, queues, SLAs, approvals, and agents — and it's priced per agent, per month. The alerting you used in Opsgenie becomes a feature inside a much larger product with a much larger surface to configure and pay for.

The rest of the incident-management market has the same shape. PagerDuty's Professional tier lists at about $21 per user per month. Put ten people on the rotation — the owner, two managers, the on-call devs, the weekend crew — and you're at ~$2,520 a year for the ability to make phones ring. These are excellent products built for teams with an SRE function. The pricing model itself assumes one.

What a small team actually needs

Strip away the enterprise layer and the on-call job for a 3–15 person team is short:

• Events in from the systems that matter (site, store, forms, cron jobs, API)
• Routing so the right person gets the right alert — not everyone, everything
• A phone that actually rings, distinctly, past the notification blur
• Acknowledgement, so the team can see someone owns it
• Escalation, so an unacknowledged alert climbs to a backup instead of dying
• A dead-man's switch for the things that fail silently

What it doesn't need: incident timelines with stakeholder comms templates, service catalogs, postmortem workflows, or a seat-based bill that punishes you for adding the Saturday person.

The migration checklist (whichever way you go)

1. Inventory your Opsgenie routing — teams, escalation policies, integrations, schedules. Most teams find a decade of cruft; migrate the 20% that fires.
2. Map your event sources. Webhooks, email integrations, monitoring tools. Each needs a new home.
3. Rebuild escalation deliberately. Who gets paged first, how long until it climbs, who's the final catch?
4. Test it like you mean it — send a real alert through the new pipe to a real phone, let it go unacknowledged on purpose, and watch the escalation climb. An alerting tool you haven't tested is a hope, not a system.
5. Don't ride the deadline. Run old and new in parallel for a month. April 2027 sounds far away; on-call migrations always take one quarter longer than planned.

Where FlowAlert fits

We built FlowAlert for exactly the teams Opsgenie's exit strands: businesses that need routing, acknowledgement, and escalation on real phones, without adopting an ITSM suite to get them. One flat price per workspace — $29/month with up to 25 teammates included — with one-click WordPress and WooCommerce integrations, a REST API for everything else, uptime checks and dead-man's-switch monitors built in, and a weekly test drill so you're never trusting an untested pager. The full comparison is here: FlowAlert as an Opsgenie alternative.

If your team runs Kubernetes and carries a five-nines error budget, migrate to PagerDuty or JSM — sincerely. If your on-call reality is "the store, the site, the forms, and whoever's awake," you now have until April 2027 to stop paying enterprise prices for it — and a good reason to switch calmly this quarter instead of frantically next spring.