Dates and rules checked on Atlassian’s pages on November 1, 2026
Quick answer: OpsGenie is being discontinued, and its end-of-life date is April 5, 2027. On that date, Atlassian shuts OpsGenie down, so logins, the REST API, integrations, and the mobile app stop. Any data you haven’t moved is deleted. New sales already ended on June 4, 2025. Atlassian recommends moving to Jira Service Management (JSM). Teams that would rather keep a standalone on-call tool can move to one (like Spike) instead.
TL;DR
- OpsGenie keeps working as it does today until April 5, 2027.
- Existing customers can still add seats and renew, as long as the new term ends before April 5, 2027.
- Moving to JSM with Atlassian’s tool switches OpsGenie off 120 days after your migration date.
- Export the data you need first, then set your own cutover date well before the deadline.
This guide is for the person planning the move off OpsGenie before its end of life. April 2027 can feel far away, but a lot has to happen before you can switch OpsGenie off. The new tool needs a security review and a contract. Schedules and escalation policies have to be rebuilt, every integration needs a new destination, and both tools should run side by side for a while. HitPath ran OpsGenie and Spike together for about a month before switching OpsGenie off.
If you move to JSM with Atlassian’s migration tool, OpsGenie keeps running for 120 days after your migration date and then switches off. A migration on December 1, 2026, for instance, would switch OpsGenie off on March 31, 2027.
One note before the details: Spike is our product, and it’s one of the tools you could move to. Since we’re not a neutral source, we don’t ask you to take our word for the dates and rules. Each one links to Atlassian’s own pages, so you can check it yourself. The guide starts with what’s changing and the key dates. It then covers what keeps working until the shutdown, what happens to your data, your options and what to do this month.
What’s actually changing, and why
OpsGenie isn’t disappearing as a set of features. Atlassian bought OpsGenie in 2018, and over the years it built OpsGenie’s alerting and on-call features into JSM. In March 2025, it announced that the standalone product would close. In its email to customers, Atlassian said the goal is “to simplify collaboration between the development and IT operations teams that rely on Atlassian to keep their businesses running”.
So OpsGenie’s ideas live on inside Atlassian’s bigger products. Your OpsGenie account, URL, mobile app and setup do not. Teams that used OpsGenie alongside Jira every day may find the move natural. Teams that chose OpsGenie as a focused alerting and on-call tool are the ones weighing a different home.
When is OpsGenie’s end of life?
OpsGenie reaches end of life on April 5, 2027. Atlassian announced two dates on March 4, 2025. The end of sale on June 4, 2025, stopped new purchases and plan changes. The end of support on April 5, 2027, shuts OpsGenie down for good.
| Date | What happened / happens | Source |
|---|---|---|
| March 4, 2025 | Atlassian announces the end of sale and end of support | Atlassian licensing FAQ |
| April 5, 2025 | Chat support is replaced by support requests | Atlassian support coverage |
| June 4, 2025 | End of sale. No new customers and no plan upgrades or downgrades. Existing customers can still add seats and renew for terms that end before April 5, 2027 | Atlassian licensing FAQ |
| Your migration date + 120 days | If you migrate with Atlassian’s tool, OpsGenie keeps running for 120 days after your migration date, then turns off automatically | What to expect from OpsGenie migration |
| April 5, 2027 | End of support. Access ends, the REST API stops and unmigrated data is deleted | Atlassian licensing FAQ |
Atlassian hasn’t announced any extension or extended support beyond April 5, 2027.
What still works until April 5, 2027, and what doesn’t
For a team that hasn’t started a migration, OpsGenie works as it does today until the shutdown. Alerts fire, schedules rotate, escalations run and the API answers.
A few things have already changed:
- The roadmap is frozen. Atlassian is investing in JSM, so OpsGenie gets no new features.
- Support works through requests. Chat support ended in April 2025. You can still open OpsGenie support requests until April 5, 2027.
- Your plan is fixed. You can’t upgrade or downgrade, but you can add seats.
Your contract and billing until the shutdown
Your current subscription keeps running, so nothing changes on your bill today. Renewals are allowed only if the new term ends before April 5, 2027, so a shorter renewal avoids paying for months you can’t use. Cancelling turns your subscription into a Free plan, and “Delete Account” removes your data for good.
If you move to JSM before your OpsGenie term ends, Atlassian adds the unused time to your new subscription. This applies when more than 30 days are left and you don’t already have JSM on that site.
What stops when OpsGenie is turned off
Atlassian’s support page lists what ends on April 5, 2027, or earlier if you migrate and turn OpsGenie off:
- Logins and data: your users can’t log in or retrieve any data.
- Integrations: any integration still pointing at OpsGenie stops delivering alerts, from monitoring tools to custom webhooks.
- The REST API: it works until April 5, 2027, then stops. Scripts, Terraform setups and internal tools that call it stop working too.
- The mobile app: it’s deactivated. Atlassian asks JSM users to switch to the Jira mobile app.
- Heartbeats: cron jobs and services that ping OpsGenie’s heartbeat endpoint need a new destination, or a missed run will go unnoticed.
What happens to your OpsGenie data
Atlassian deletes any data you haven’t moved on April 5, 2027. That covers alert history, schedules, escalation policies, users and integration settings.
What you can take with you depends on the path. Atlassian’s migration tool moves alerts, schedules, escalation policies, incident history and audit logs into JSM. For any other tool, you export through OpsGenie’s REST API and the alert list. Our OpsGenie export guide lists what you can and can’t export.
There’s one change that’s easy to miss if you move to JSM. OpsGenie Enterprise kept your alert history with no time limit. JSM deletes alert history after a set period, and the period depends on which JSM plan you buy:
| Jira Service Management plan | How long alert history is kept |
|---|---|
| Free | 1 month |
| Standard | 1 year |
| Premium | 3 years |
| Enterprise | 5 years |
Source: Atlassian support coverage after migration.
If you work in a regulated industry, run compliance reports or look back at old incidents, this matters. It’s worth checking how far back your team looks in OpsGenie before you pick a JSM plan, and exporting the history you need to keep.
Your options before April 5, 2027
There are two lasting places to move, plus the option of waiting. A few questions point to the right path for your team:
| If this sounds like your team | The path to look at first |
|---|---|
| You already run IT service management in Jira and want one Atlassian product | Jira Service Management |
| Your engineering team wants on-call without a full service desk | A standalone on-call tool |
| You used OpsGenie as a standalone alerting and on-call tool | A standalone on-call tool |
| You manage OpsGenie as code, with Terraform or scripts | Any path, but plan time to move your code to the new tool’s provider or API |
| You need SSO from day one | JSM Enterprise includes it, lower JSM plans need Atlassian Guard, and other tools vary by plan |
| You need a status page for customers | JSM Enterprise, or a tool that includes one |
Move to Jira Service Management
JSM is Atlassian’s main destination and suits teams that already run IT service management in Jira. Start in OpsGenie under Settings > Plan your move. Atlassian’s tool moves users, schedules, escalation policies, alerts and most integrations. Our OpsGenie to JSM guide covers each step.
The tool doesn’t move everything. Atlassian’s list of feature changes names the gaps:
- Phone numbers that Atlassian provided for OpsGenie have to be ported by hand before migration.
- OpsGenie SSO doesn’t carry over. Access moves to Atlassian Guard, which is a separate subscription below JSM Enterprise.
- Some features need JSM Premium or Enterprise. These include heartbeats, stakeholder notifications, a phone number that rings whoever is on call, and integrations with tools on your own servers.
- API keys are replaced by Atlassian authentication, so scripts need new endpoints. Terraform users move to Atlassian’s Operations provider.
- Global notification policies become team-level, and the Incident Command Center (OpsGenie’s built-in space for running incidents) is retired.
JSM Standard costs about $21.50 per agent per month at 75 agents, and smaller teams pay more per agent. Our JSM pricing breakdown shows the cost at 10, 25 and 50 agents. It includes unlimited alerts, SMS and voice. Status pages come only with Enterprise. Our JSM vs. Spike comparison shows where a standalone tool differs. The move also starts the 120-day clock. A few people who made the switch report friction, and one user on r/sysadmin wrote that “It’s not been fun”.
What about Compass?
Atlassian’s older migration pages also list Compass, its product for software engineering teams. In April 2026, Atlassian announced that Compass will be phased out. Its Compass support docs plan the end of support for December 31, 2027 and say alerts and on-call “must be migrated to Jira Service Management”. So a move to Compass now would probably mean a second move within about a year. If your team already moved to Compass, it can be useful to plan the next step early.
Move to a standalone on-call tool
Teams that chose OpsGenie for alerting and on-call rather than tickets often look outside Atlassian. A standalone tool keeps alerting and on-call as the whole product, the way OpsGenie did. The trade-off is a manual move: you rebuild schedules and escalation policies, point each integration at the new tool and run both side by side before switching.
We compare these tools in two guides, one for startups and one for enterprise teams. Spike is one of the tools we compare, and it feels familiar to OpsGenie users. Its Business plan costs $14 per user per month, and OpsGenie users get 20% off their first year on an annual plan. Spike’s team can import your schedules and escalation policies, and you can run both tools for as long as you need. If your team keeps Jira, our list of JSM alternatives for teams that keep Jira compares how each tool syncs with it.
Wait until 2027
Nobody plans to wait, but it’s easy to drift into it. OpsGenie keeps working until April 5, 2027, so waiting costs nothing on the bill. The cost shows up later as a squeezed parallel run, rushed integration work and a renewal that can’t stretch past the deadline. Waiting turns a planned move into a hurried one.
What to do this month
Five steps keep the move on your terms, whichever path you choose:
- Export your OpsGenie data now, starting with alert history and anything your compliance team needs. The export guide lists what you can and can’t export.
- List everything connected to OpsGenie: integrations, scripts and Terraform that call its API, heartbeats, phone numbers, and SSO.
- Pick your path with the table above and check your renewal date against April 5, 2027.
- Set your own cutover date well before the deadline, with time for a parallel run.
- Run both tools side by side until every alert shows up in both, then switch OpsGenie off.
The move is also a change for the people who get alerted, so it helps to bring them in early. Share the dates and your cutover plan. Treat the move as a reliability decision, not a tooling chore. Tell responders how long the parallel run will last, give them a place to ask questions and update runbooks before the switch. Our migration resources include a checklist and a parallel run plan.
FAQ
Is OpsGenie’s end of life the same as its end of support?
Yes. Atlassian calls April 5, 2027 the end of support. “End of life” is the term most people outside Atlassian use for the same date.
Is OpsGenie going read-only before April 2027?
Atlassian’s support pages list no read-only date for OpsGenie. It keeps working until April 5, 2027, or until it turns off 120 days after a migration to JSM. If a banner in your account shows a different date, Atlassian support can confirm what it means for your account.
How much does OpsGenie cost until it shuts down?
Your current price stays in place, because plans can no longer change. On monthly billing for up to 25 users, OpsGenie costs $11.55 per user per month on Essentials, $24.15 on Standard and $38.50 on Enterprise. The price per user falls as you add more users, and annual billing costs less.
Can I still buy OpsGenie seats or renew?
Yes, with limits. Existing customers can add seats until April 5, 2027, and can renew if the new term ends before that date. New customers can’t sign up, and plans can’t be upgraded or downgraded.
What’s replacing OpsGenie?
Atlassian is moving OpsGenie’s alerting and on-call features into Jira Service Management. It also listed Compass as an option, but Compass is being phased out. Standalone on-call tools are the other common choice for teams leaving Atlassian.
Do I have to move to Jira Service Management?
No. JSM is Atlassian’s recommended path. You can also export your setup and move to any other on-call tool, as long as you’re done before April 5, 2027.
What is OpsGenie used for?
OpsGenie alerts the right person when monitoring tools detect a problem. It also keeps on-call schedules and escalates an alert when nobody responds. A replacement needs to cover all three.
OpsGenie’s shutdown has a fixed date, and that makes it easier to plan around than most changes. If you’d like help with the move, we’ll map it out with you on a short call.
