Opsgenie is no longer a product you can choose fresh: Atlassian ended new sales on June 4, 2025 and ends support on April 5, 2027, when access is shut off and any data not moved to Jira Service Management is deleted. PagerDuty is actively sold, with a Free plan, Professional at $21 per user per month billed annually ($25 monthly), and PD Reliability Platform plans from $2,800 per year. For existing Opsgenie customers the real question is where to move: Jira Service Management (Atlassian's automated path), PagerDuty (the broadest incident platform, with a vendor-run migration offer), or an on-call tool that keeps the Opsgenie alert API, such as OpsPing, where most alert sources change only the API URL and key.
Side by side
| PagerDuty | Opsgenie | |
|---|---|---|
| Status in 2026 | Sold and supported | End of sale June 4, 2025; end of support April 5, 2027 |
| New customers | Yes, including a Free plan | No. Existing customers can add seats and renew if the term ends before April 5, 2027 |
| Free plan | $0: 5 users, 1 on-call schedule, 1 escalation policy, 100 SMS or phone notifications per month | Not available to new customers |
| Listed per-user price | Professional: $21/user/month billed annually, $25 monthly | Existing customers, 1–25 users, per user per month: Essentials $9.45 annual / $11.55 monthly; Standard $19.95 / $24.15; Enterprise $31.90 / $38.50 (volume tiers lower above 25 users) |
| Platform plans | PD Reliability Platform: Starter $2,800/year (10 seats), Essential $12,000/year (20 seats), Plus $48,000/year (50 seats), Ultimate custom | Not applicable |
| Add-ons on the per-user plan | AIOps, PagerDuty Advance, Runbook Automation, Status Pages, Live Call Routing (purchased separately on Professional) | Upgrades and downgrades closed since June 4, 2025 |
| Integrations | 750+ out-of-the-box integrations on every plan | Remaining Opsgenie-based integrations stop working when Opsgenie is turned off |
| Mobile app | iOS and Android app on every plan | Deactivated at shutdown; Atlassian tells users to switch to the Jira mobile app |
| Your data after April 5, 2027 | Not affected | Only data migrated to Jira Service Management remains; the rest is deleted |
| Vendor migration help | Promotional Professional Services migration for Opsgenie customers buying Operations Cloud Core (first 50 qualifying customers, up to 250 active users) | Atlassian's automated migration to Jira Service Management, with 120 days of parallel Opsgenie access |
Sources, checked November 2, 2026: PagerDuty pricing ↗ and Opsgenie migration offer ↗; Atlassian Opsgenie licensing ↗, what happens when Opsgenie is turned off ↗ and Opsgenie migration ↗. Prices are list prices in USD and can change; confirm with the vendor before you budget.
Opsgenie's end of life, and where Atlassian is steering customers
Atlassian announced in March 2025 that Opsgenie's capabilities are moving into Jira Service Management (Atlassian announcement ↗). The licensing page sets two dates: end of sale on June 4, 2025, and end of support on April 5, 2027, when “access to Opsgenie will be shut off, the product will no longer be accessible, and any customer data in Opsgenie that has not been moved to Jira Service Management will be deleted” (Atlassian ↗).
- Jira Service Management is the sanctioned path. Atlassian's automated tool moves alerts, schedules and policies on a date you pick, with 120 days of parallel Opsgenie access; some setups need manual steps (Atlassian ↗). Atlassian recommends a plan by current edition: Opsgenie Free to JSM Free, Essentials to Standard, Standard to Premium, and Enterprise to Premium or Enterprise (Atlassian Support ↗). JSM's Free plan covers up to 3 agents (JSM pricing ↗).
- Some features do not come along. Atlassian lists deprecated notification policies, incident rules, Opsgenie actions and older integrations such as Crashlytics as permanently unavailable after shutdown (Atlassian Support ↗).
- Compass is being phased out too. Atlassian is moving Compass's catalog and scorecards to DX. Compass closed to new customers on May 13, 2026 and access ends on December 31, 2027 (Atlassian Community ↗); Atlassian's support docs say alerts and operations functionality must move to Jira Service Management because DX does not support it (Atlassian Support ↗).
- The API keeps working until the end. Atlassian says the Opsgenie REST APIs work until April 5, 2027, but recommends updating endpoints before Opsgenie is turned off. Sites that migrate to JSM are shut down automatically 120 days after the migration date unless turned off sooner (Atlassian Support ↗).
Our Opsgenie shutdown timeline has every date with its source, and Opsgenie end of life covers what happens to your data.
What PagerDuty offers
PagerDuty sells two lines, per its pricing page ↗ (checked November 2, 2026):
- Incident Management (per user). Free covers 5 users, 1 on-call schedule and 1 escalation policy. Professional ($21/user/month annually, $25 monthly) adds post-incident reviews, single sign-on, external status pages for up to 250 subscribers, analytics reports and one year of historic data. Noise-reduction features such as alert grouping, suppression and Event Orchestration are marked “Must purchase AIOps” on Professional.
- PD Reliability Platform (annual platform fee). Starter ($2,800/year, 10 seats), Essential ($12,000/year, 20 seats), Plus ($48,000/year, 50 seats) and Ultimate (custom). These bundle Signal Intelligence events, AI actions, private status pages, audit trail reporting and PagerDuty's agents, with credit packs for extra capacity.
- Ecosystem. 750+ out-of-the-box integrations, Slack and Microsoft Teams chat experience, an open API, and a full-featured iOS and Android app on every plan.
The trade-off is cost and packaging: the per-user plan is priced above Opsgenie's listed Essentials and Standard rates for 1–25 users, and several capabilities Opsgenie teams may expect sit in add-ons or the platform plans.
Migration effort
| Path | What moves | What you still do |
|---|---|---|
| Opsgenie → Jira Service Management | Atlassian's automated migration moves most data and configuration on the date you choose; migrated alerts, schedules, escalation policies, incident history and audit logs stay available | Manual steps for some setups; replace features Atlassian lists as left behind; move users to the Jira mobile app |
| Opsgenie → PagerDuty | With the promotional offer: user profiles, contact methods, notification rules, teams, escalation policies, on-call schedules and foundational monitoring integrations, configured by PagerDuty Professional Services for qualifying Operations Cloud Core buyers | Repoint any remaining alert sources and scripts to PagerDuty's own integrations, since it does not accept the Opsgenie alert API; anything beyond 250 users, ITSM integrations such as ServiceNow, or custom builds needs separate scoping; start dates depend on PagerDuty's capacity |
| Any path | — | Export the alert, incident and audit history you need before April 5, 2027, run both systems in parallel, and test a firing and a resolution through every source before moving the rotation |
Migration scope from Atlassian ↗, Atlassian Support ↗ and PagerDuty's offer page ↗ (updated July 10, 2026), checked November 2, 2026.
Who each fits
Stay on Opsgenie (for now) if…
- You are an existing customer and need time to plan. It keeps working until April 5, 2027, which gives you a window to run a new tool in parallel. It is not a long-term option.
Choose Jira Service Management if…
- Your organization already runs on Atlassian and wants alerting, on-call and ITSM in one place, and you are comfortable with per-agent pricing and with the features Atlassian lists as left behind.
Choose PagerDuty if…
- You want the broadest incident platform: 750+ integrations, AIOps and event orchestration, runbook automation and AI agents, and you have the budget for per-user or platform pricing plus add-ons.
- You have up to 250 active users, qualify for the promotional migration, and want PagerDuty's team to do an as-is move.
A third option for teams leaving Opsgenie: OpsPing
If what you need is paging, schedules and escalations, and your alert sources are built on the Opsgenie v2 alert API, an API-compatible pager avoids reconfiguring every integration. OpsPing (this site) is one such tool. The facts below come from our own documentation:
- Opsgenie-compatible alert API. Change the API URL to
https://api.opsping.comand use a new OpsPing API key with the familiarGenieKeyheader. Create with alias deduplication works, and so do get by alias,alias:andstatus:list-query tokens, and most actions by alias (identifierType=alias): acknowledge, close, notes, tags, assign, responders, escalate, snooze and details. That means Alertmanager and Grafana can keep auto-resolve on. - Known gaps. Unacknowledge, unassign, reopen, unsnooze, mark-read and delete still need the alert ID (returned as
alertIdon create) or tiny ID. There is no update-priority route, and configuration APIs use OpsPing's own schemas. The full list is on the Opsgenie-compatible API page. - Importer. Users, teams, services, schedules and overrides, escalation policies, heartbeats and integrations import from Opsgenie; routing, policies, notification rules and maintenance are review-gated. Historical alerts are archive-only. The dry run is free; applying an import needs Team or Business. See the migration guide.
- Native mobile app. OpsPing apps for iPhone, Android and Apple Watch, with iOS Critical Alerts and Android Do-Not-Disturb bypass, and unlimited push on every plan. Voice calls are the urgent fallback on paid plans; OpsPing does not use SMS.
- Pricing. Free for up to 5 responders (1 team, 1 schedule, a single-level escalation policy, 3 integrations); Team at $8 and Business at $15 per responder per month (pricing).
- Migration help. Async by email at [email protected], with calls by appointment.
OpsPing is a smaller product than PagerDuty, with no AIOps event correlation, no runbook automation engine and a much smaller integration catalog. The step-by-step plan is in How to switch from Opsgenie.
FAQ
Is PagerDuty or Opsgenie better in 2026?
For a new purchase, the choice is made for you: Atlassian stopped selling Opsgenie on June 4, 2025, and ends support on April 5, 2027, when access is shut off and data not moved to Jira Service Management is deleted. PagerDuty is still sold, with a Free plan, Professional at $21 per user per month billed annually ($25 monthly), and PD Reliability Platform plans from $2,800 per year (PagerDuty pricing page, checked November 2, 2026). Existing Opsgenie customers are really choosing a destination: Jira Service Management, PagerDuty, or another on-call tool.
Can I still buy Opsgenie?
Not as a new customer. Since June 4, 2025, new purchases, sign-ups and plan upgrades or downgrades are closed. Existing customers can still add seats, and renewals are allowed if the term ends before April 5, 2027 (Atlassian Opsgenie licensing page, checked November 2, 2026).
How much does PagerDuty cost in 2026?
PagerDuty's pricing page, checked November 2, 2026, lists Free ($0, 5 users, 1 on-call schedule, 1 escalation policy), Professional at $21 per user per month billed annually or $25 monthly, and PD Reliability Platform plans: Starter $2,800 per year (10 seats), Essential $12,000 per year (20 seats), Plus $48,000 per year (50 seats) and Ultimate at custom pricing. AIOps, PagerDuty Advance, Runbook Automation, Status Pages and Live Call Routing are listed as add-ons for Professional.
Does PagerDuty help Opsgenie customers migrate?
PagerDuty publishes a promotional offer, updated July 10, 2026: Opsgenie customers that buy the Operations Cloud Core plan can get complimentary Professional Services onboarding and migration, limited to the first 50 qualifying customers, up to 80 Expert Service Hours over the first 3 weeks, "as-is" migrations of up to 250 active users, valid until June 1, 2028. PagerDuty says it may revoke or modify the offer at any time.
Is there an option that keeps the Opsgenie alert API?
Yes. OpsPing accepts a documented subset of the Opsgenie v2 alert API with the GenieKey header, so most alert sources change only the API URL and key. Get by alias, alias: and status: list queries and most actions work by alias; unacknowledge, unassign, reopen, unsnooze, mark-read and delete still need the alert ID or tiny ID, and there is no update-priority route. Plans are Free, Team at $8 and Business at $15 per responder per month.
Sources
- PagerDuty — Plans & Pricing ↗ (plans, prices, add-ons, feature table)
- PagerDuty — Promotional Migration Offer for Opsgenie Customers ↗ (updated July 10, 2026)
- Atlassian — Opsgenie Licensing ↗ (end-of-sale and end-of-support dates, Opsgenie list prices)
- Atlassian Support — What happens when Opsgenie is turned off? ↗
- Atlassian — Migrate Opsgenie ↗ (automated migration, 120-day parallel access)
- Atlassian Support — What are my options for migrating from Opsgenie? ↗ (recommended JSM plans)
- Atlassian — The Evolution of IT Operations and Opsgenie ↗ (published March 2025)
- Atlassian — Jira Service Management pricing ↗ (Free plan for 3 agents)
- Atlassian Community — The Next Chapter for Compass ↗ and Atlassian Support — Migrate from Compass to DX ↗
All sources accessed November 2, 2026. Vendors can change prices and offers at any time; check the source before you plan around a figure. PagerDuty® is a trademark of PagerDuty, Inc. Opsgenie® is a trademark of Atlassian. OpsPing is not affiliated with, sponsored, or endorsed by PagerDuty or Atlassian.