Opsgenie Is Shutting Down April 5, 2027: The Complete Timeline, Real Migration Costs, and Every Option Compared

Updated: November 2026 Reading time: 9 min By the PagerDock team

Atlassian has confirmed it: Opsgenie reaches end of life on April 5, 2027. New signups have been closed since June 2025, migration tooling into Jira Service Management is live, and on the shutdown date, every unmigrated alert rule, on-call schedule, and escalation policy will be permanently deleted. If your team still runs on Opsgenie, this guide walks through the exact timeline, what the "official" path really costs, and every alternative worth considering โ€” including the option most comparison posts skip: flat-priced tools built for small teams.

TL;DR: You have until April 5, 2027. The official path (JSM Operations) costs roughly 2ร— what you pay today for equivalent functionality. PagerDuty is excellent but enterprise-priced. Budget on-call tools exist โ€” check whether your team actually needs phone/SMS paging before paying for it. Jump to the cost comparison or the migration checklist.

The official timeline (all dates confirmed)

DateWhat happened / happensWhat it means for you
Mar 4, 2025Atlassian announces end of OpsgenieThe writing was on the wall.
Jun 4, 2025End of sale โ€” no new signups, upgrades, or downgradesYou can't onboard new teammates onto Opsgenie plans anymore.
Q2 2026Migration tooling ships in JSMAutomated migration of configurations, typically 1โ€“3 hours for mid-size teams.
Apr 5, 2027End of support โ€” full shutdownWeb app, mobile apps, and REST APIs stop responding. All unmigrated data is deleted.

Two details worth knowing: existing customers can run Opsgenie and its JSM/Compass replacement in parallel for up to 120 days before the switch-off, and Atlassian itself recommends starting your migration at least 6 months before the deadline โ€” which, as of this update, is now.

Why Atlassian is doing this

The official reasoning is consolidation: one incident-management surface instead of two. Opsgenie's core capabilities (alert routing, on-call schedules, escalation policies) have been rebuilt inside Jira Service Management Cloud. For Atlassian, maintaining a standalone product duplicates engineering and splits the user base. For you, it means a forced platform decision โ€” and for teams that used Opsgenie without the rest of the Atlassian stack, it means re-evaluating your whole alerting stack under time pressure.

The real cost of the "official" path: JSM Operations

Atlassian steers every Opsgenie customer toward Jira Service Management Operations. It works โ€” the migration tooling is competent, and if you're already deep in Jira, single-vendor consolidation is real value. But the pricing shock is well documented. In published customer interviews, engineering leaders describe the same math:

"Opsgenie being deprecated... JSM ends up being twice the cost for basically the same features." โ€” Engineering leader, health wearables company (2024)

Concretely: Opsgenie Essentials was $9.45/user/month (annual billing) and Standard $19.95. JSM's equivalent functionality lands at roughly $40โ€“46/user/month for the same teams. For a 10-person rotation, that's the difference between ~$95/month and ~$400+/month โ€” for the same job: who gets woken up, and when.

Every option compared (10-person team, monthly cost)

OptionBilling model~Monthly cost (10 users)What you get / give up
Stay on Opsgenieโ€”โ€”Not an option. Hard stop April 5, 2027, data deleted.
JSM Operations (official path)Per agent~$400+Single vendor, decent migration tooling. Same features, ~2ร— the price. Heavier UX.
PagerDutyPer user~$210โ€“410The enterprise gold standard: huge integration catalog, mature AIOps (add-on from $699/mo). Overkill for many small teams; every seat billed whether paged or not.
Rootly / incident.ioPer userCustom (mid-market pricing)Slack-native incident response, loved by mid-size teams. Pricing targets funded startups, not 5-person rotations.
Better StackPer user~$290Beautiful product, bundles monitoring + on-call + status pages. Per-seat pricing climbs fast.
Squadcast (SolarWinds)Per user~$90โ€“150Cheapest of the established names. Free tier caps at 5 users.
Grafana Cloud IRMActive users + platform fee~$219 ($19 + $20 ร— 10)Natural home if you already run Grafana Cloud. Note: the free self-hosted Grafana OnCall was archived March 2026 โ€” the "just self-host it" escape hatch is gone.
PagerDockFlat per team$12โ€“59 totalAlert routing, on-call schedules, escalation, deduplication, heartbeats, Opsgenie config importer, audit CSV. Email, Slack, webhook + push (Pushover/ntfy/Telegram, emergency wake-up). No telecom mark-up โ€” BYO Twilio for real phone/SMS.

The honest question that saves you the most money

Does your team actually need phone calls and SMS paging? Enterprise on-call tools bill a premium for voice/SMS infrastructure that many small teams never use โ€” their alerts flow through Slack and email, which already reach everyone's pocket. If your escalation path is "Slack the on-call, email the backup," you've been paying enterprise prices for channels you don't fire. That's the gap flat-priced tools fill: same routing/escalation/dedup discipline for the channels that matter, minus the telecom overhead.

If you do need phone paging at scale โ€” hospitals, industrial ops, massive rotations โ€” PagerDuty is genuinely the right answer and no honest vendor will tell you otherwise.

What migration actually involves (any target)

If your destination is PagerDock, steps 1โ€“4 collapse into one

Paste your Opsgenie API key into the importer (it works until the shutdown date). We pull your integrations, escalation policies, schedules, and heartbeats, show you a mapping preview, and recreate them here โ€” then you point your monitoring tools' webhook URLs at pagerdock.dev and swap the API key. Change one URL, keep your stack.

# Before (Opsgenie)
webhook_url: https://api.opsgenie.com/v2/alerts
api_key:     GenieKey 8f2e9d61...

# After (PagerDock)
webhook_url: https://api.pagerdock.dev/v1/events
api_key:     GenieKey b7c41a02...   # Opsgenie-compatible fields โ€” same payload

Your migration checklist (print this)

Frequently asked questions

Can I keep using Opsgenie after April 5, 2027?

No. Web, mobile, and REST APIs all stop, and Atlassian deletes unmigrated data. There is no extension path.

Is JSM Operations included free if I already pay for Jira?

No โ€” Operations capacity is a separate line item, and the per-agent pricing is what drives the ~2ร— total cost teams report.

What's the cheapest way to keep on-call for a small team?

For teams whose alerts flow through Slack/email: a flat-priced tool (PagerDock is $12โ€“59/month total, free up to 5 members) typically lands 70โ€“90% below per-seat enterprise pricing. If you need phone/SMS paging at scale, budget for PagerDuty or Grafana Cloud IRM.

When should I start?

Now. Atlassian recommends 6 months of runway; complex multi-team schedules take the longest, and re-authorization of integrations is the step teams most often underestimate.

Moving off Opsgenie? Dock your pager.

Flat pricing from $12/team/month ยท Free up to 5 members ยท Opsgenie config importer ยท 30-day full trial, no card required

Join the waitlist โ€” founding teams get locked-in early pricing

Sources: Atlassian's Opsgenie end-of-sale announcements and support documentation; published customer interviews on JSM migration costs; public pricing pages of each vendor listed, retrieved November 2026. Pricing changes โ€” verify current list prices before purchasing.

ยฉ 2026 PagerDock HomePrivacyTerms