Opsgenie Rescue Hub
Opsgenie end of life: your rescue plan before April 5, 2027
Atlassian shuts Opsgenie down on April 5, 2027. That day, login, the REST APIs, integrations, and the mobile app stop, and any data you haven't moved to Jira Service Management is deleted. This hub covers the dates, what to export, and where your on-call can go next.
Facts checked October 28, 2026 against Atlassian's own pages.
Free for 14 days. No credit card required.
Opsgenie shuts down
139days left
21% of the notice period left
What happens next
- Today, Nov 17, 2026Opsgenie still pages
- Migration date + 120 daysAutomatic switch-off, unless you turn it off sooner
- Apr 5, 2027Shutdown and data deletion
Not ready to switch yet?We'll send one email 30 days before shutdown. Nothing else.
Opsgenie shutdown dates for your situation
Pick the one that sounds like your team.
You have until April 5, 2027
Opsgenie keeps paging until then. Use the time to test a replacement against real alerts before you touch Atlassian's migration tool, because starting it sets a much shorter clock.
Your Opsgenie shuts off 120 days after your scheduled migration date
Atlassian turns Opsgenie off automatically 120 days after your scheduled migration date, unless you turn it off sooner. Enter that date to see your switch-off day.
Any renewal has to end before April 5, 2027
Atlassian still allows renewals and added seats, but only on terms that end before the shutdown. Every renewal signed now is a short, final term, so it's worth pricing the replacement before you sign.
Opsgenie end of life timeline
Two dates are fixed. The third depends on your scheduled migration date.
- Jun 4, 2025End of saleNo new purchases or edition changes. Added seats and short renewals still allowed.
- Nov 17, 2026You are here139 days left. Renewals signed now are short, final terms.
- Migration date + 120 daysAutomatic switch-offOpsgenie shuts off 120 days after your scheduled migration date, unless you turn it off sooner.
- Apr 5, 2027Shutdown and data deletionLogin, APIs, integrations, and the mobile app stop. Unmigrated data is deleted.
View the timeline as a table
| Date | Milestone | What it means for you |
|---|---|---|
| Jun 4, 2025 | End of sale | No new purchases or edition changes. Added seats and short renewals still allowed. |
| Nov 17, 2026 | You are here | 139 days left. Renewals signed now are short, final terms. |
| Migration date + 120 days | Automatic switch-off | Opsgenie shuts off 120 days after your scheduled migration date, unless you turn it off sooner. |
| Apr 5, 2027 | Shutdown and data deletion | Login, APIs, integrations, and the mobile app stop. Unmigrated data is deleted. |
Opsgenie alternatives and Atlassian's migration paths
Atlassian's Opsgenie migration guide lists only Jira Service Management plans as destinations. Compass closed to new customers on May 13, 2026, and Atlassian says Compass alerting has to move to Jira Service Management. That leaves two paths for an on-call team: Jira Service Management, or alerting and on-call outside Atlassian. Two lifeboats, compared on what changes for an on-call team.
| Compared on | Jira Service ManagementAtlassian's ITSM path | |
|---|---|---|
| Who it suits | Teams that want alerting inside an ITSM service desk | Any team that needs alerting, escalation, and on-call on its own |
| How it bills | Per agent. Atlassian shows Opsgenie customers their migration price inside Opsgenie. Does everyone who gets paged need an agent seat? Check before you count. | Per user at published rates. Free up to 5 users. |
| Migration clock | Opsgenie switches off 120 days after your scheduled migration date | No clock. Run both side by side. |
| Moving your setup | Atlassian's automated migration tool | Opsgenie importer for schedules, rotations, overrides, and people. Escalation policies, alert rules, and integrations are rebuilt by hand. |
| Voice and SMS | SMS in all countries. Voice calls on Premium and Enterprise only. | Voice and SMS from Starter, in the US, UK, and Australia. Email, push, Teams, and Slack anywhere. |
Already moved Opsgenie into Compass? See Opsgenie vs. Jira Service Management vs. Compass.
What to export from Opsgenie before it shuts down
Pack your grab bag before you move anything. Your ticks stay in this browser, so you can come back to it.
0 of 6 packed
Start with schedules. They take longest to rebuild.
Move Opsgenie to JAMS Incident Management in five steps
JAMS Incident Management is a standalone alerting, escalation, and on-call product from JAMS Software. Its Opsgenie importer builds nothing until you've reviewed a full report.
Get your schedules out of Opsgenie
Use a read-only API key, or run the provided script if policy blocks pasting a live key. A few minutes.
Run the free check
Nothing is written to your account. You get a full report: every schedule and rotation, exactly what can't be represented, and a coverage preview showing any hours nobody would be on call.
Fix what the report flags
Blocking items, like a rotation with nobody in it, stop the import until resolved in Opsgenie. Re-running the check costs nothing and there's no limit on how many times.
We build it with you
Confirm the report, and everything (people, schedules, and rotations) is created in one operation, or none of it is. Today, send the finished report to JAMS and the team builds it with you.
Finish the switch
Add the phone numbers Opsgenie didn't export, point a flow at each imported schedule since it won't page anyone until you do, then send a real test alert before you turn Opsgenie off.
Read the Opsgenie migration guide
Hear what a real page sounds like
Watch an alert route, escalate, and land as a phone call.
- Seven channels, including voice
- Policy-driven escalation
- Two-way Azure Monitor, ServiceNow, Zendesk
- OIDC single sign-on
- Hosted on Microsoft Azure
- Failed JAMS Scheduler jobs open incidents
Run a free trial before you start Atlassian's clock
Point a copy of your alerts at JAMS Incident Management, rebuild one escalation policy, and let both tools page for a week. When the new one is right, start the migration.
Free carries one alert flow, one on-call schedule, and no escalation policies, so it can't mirror a real Opsgenie setup. A parallel run with real escalation needs Starter.
Start the trial. Every feature is unlocked for 14 days, with 50 SMS or WhatsApp messages and 10 voice calls. Invite the whole rotation.
Rebuild your highest-severity escalation policy and on-call schedule. Send a real alert through it.
Connect the source that matters most: Azure Monitor, ServiceNow, Zendesk, a webhook, or email.
On day 14 nothing is deleted. Pick a plan, or stay on Free if your team is five people or fewer.
Count everyone in the rotation, not just your service desk. Starter is $6 per user a month billed annually, and teams of five or fewer stay free.
- 5 SMS or WhatsApp messages per user/month ยท no voice calls
- 1 flow ยท 1 on-call schedule
- Unlimited email, push, Teams & Slack alerts
- No SSO
- No premium integrations, AI Helper, or audit trail
No card required. Upgrade when you outgrow it.
- 50 SMS or WhatsApp messages + 10 voice calls per user/month
- Unlimited flows & on-call schedules
- Unlimited email, push, Teams & Slack alerts
- SSO available as an add-on
- No premium integrations, AI Helper, or audit trail
Add SSO, extra SMS or extra voice calls as add-ons.
- 100 SMS or WhatsApp messages + 20 voice calls per user/month
- Unlimited flows & on-call schedules
- Unlimited email, push, Teams & Slack alerts
- Includes SSO
- Includes premium integrations, AI Helper & audit trail
Everything in Starter, plus SSO, premium integrations, AI Helper, and audit trail.
- Customized packaging and pricing for large, enterprise teams
Tailored to your team's needs.
Monthly billing adds $2 per user. Messaging and voice figures are per-user rates pooled across your team, so ten Starter users share 500 SMS or WhatsApp messages and 100 calls rather than rationing them per person. Extra blocks of 50 cost $100 a month each. Exhausting the messaging allowance pauses SMS and WhatsApp only. Voice keeps working, and email, push, Teams, and Slack are never affected. Admins get an email at 75% and 100% of each allowance.
Opsgenie end of life FAQ
When does Opsgenie shut down?
April 5, 2027. Atlassian shuts off access that day: login, the REST APIs, integrations, and the mobile app stop, and unmigrated data is deleted.
What happens to my Opsgenie data after April 5, 2027?
Atlassian deletes any data that hasn't been moved to Jira Service Management. Export schedules, escalation policies, and any alert history you need before then.
Can I still renew Opsgenie?
Yes, as long as the term ends before April 5, 2027. Any renewal signed now is a short, final term.
Can I still add Opsgenie seats?
Yes. Atlassian sells added seats until April 5, 2027. Edition upgrades and downgrades ended June 4, 2025.
What happens if I use Atlassian's migration tool?
Opsgenie shuts off automatically 120 days after your scheduled migration date, unless you turn it off sooner. Plan a four-month cutover, not one that runs to April 2027.
Is there a free Opsgenie alternative?
JAMS Incident Management is free for up to 5 users, with one alert flow and one on-call schedule. Escalation policies need Starter, at $6 per user a month billed annually.
Do I need JAMS Scheduler to use JAMS Incident Management?
No. JAMS Incident Management is a standalone product. If you run JAMS Scheduler, a failed job can open an incident automatically.
Which regions get voice and SMS alerts?
The United States, the United Kingdom, and Australia today. Email, push, Microsoft Teams, and Slack work anywhere.
Facts we checked
Last checked October 28, 2026
Leave Opsgenie on your schedule
Test JAMS Incident Management against your real alerts while Opsgenie is still running.
Free for 14 days. No credit card required.


