# Your genie is vanishing: introducing the Opsgenie rescue program *July 9, 2026* If you run on Opsgenie, you already know the bad news. Atlassian stopped selling it in June 2025, and on April 5, 2027, it shuts down for good. The alerts stop. The schedules stop. Your historical data gets deleted. The genie lamp goes dark. So this isn't the usual on-call story where a team finally gets fed up and decides to switch. Opsgenie customers don't get to decide. The only choice left is where you land, and how much pain you take getting there. Today, we're launching the Opsgenie Rescue Program to make that landing soft: simplified migration and free overlap so you never pay two vendors at once. ## Don't get stuffed back in the bottle The path Atlassian points you toward is Jira Service Management or Compass. Both pull you deeper into a suite that was never built around on-call. JSM is a service desk first and an incident tool second. The migration tooling moves some of your setup automatically, then hands you a list of things to rebuild by hand: action policies, chat integrations, and a service desk UI nobody asked to learn. And it costs more for the privilege. This is the part that surprises people most. As one engineering leader at a health wearables company told us, "JSM ends up being twice the cost for basically the same features." That's the (Ops)genie going back in the bottle and calling it an upgrade. You don't have to take that deal. A forced migration is a bad hand. But it's also the rare moment when you get to leave a tool that stopped improving years ago. As an SRE lead at an open source pioneer put it, the appeal was "continued improvements with incident.io well beyond what we saw with Opsgenie just kind of being the same thing for the last eight years that I've used it." If you have to move anyway, move somewhere that's still being built. ## What's in the program Four parts, each there to remove a reason to settle for the default path. ### Migrate on your timeline, not Atlassian's You're already paying for Opsgenie until your contract ends. You shouldn't pay for incident.io on top of it while you migrate. Opsgenie customers get free overlap when they sign up, so you run both systems in parallel, validate the new setup with zero risk, and cut over when you're ready. No double billing, and no racing a deadline you didn't set. ### Simplified migration We’ve migrated hundreds of companies from Opsgenie to incident.io, and we’ve got your back to make sure your migration is smooth. incident.io connects straight to your existing Opsgenie setup, so you can try it out before you change a thing. When you're ready, your schedules, escalation paths, and notification preferences come across in a few clicks, and your teams and services show up automatically. Run both side by side for as long as you like, check everyone's set up to get paged, then flip the switch when it suits you. Most teams are live in days, not the months a JSM rollout usually takes. ### 99.99% uptime for Enterprise teams that need it Your on-call tool should be the last thing that goes down. For Enterprise teams whose reliability bar demands it, we commit to 99.99% uptime in our SLA, in writing. That's under an hour of downtime a year on the tool that's meant to wake you up. Not every team needs that guarantee. The ones that do shouldn't have to wonder whether their pager will be there at 3am. ### No more cold starts This is where the gap is widest. Opsgenie pages you and stops. incident.io keeps working. The moment an incident is declared, Investigations scours your logs, deployment and commit history, past incidents, and service dependencies to build a structured root cause hypothesis before you've touched a thing. You arrive with a working theory and a direction on where to start, not a blank page. And it keeps going alongside you, running parallel analysis and surfacing things you haven't thought to look for yet. The reason you can't just point Claude at your Datadog and do this yourself? Investigations learns from your organisation. It's built from your incidents, your services, and your deployments, and it knows which investigation strategies failed last time, so it skips them and goes straight to what works. ## Why not just wait until 2026 is almost over? Because migrations done under deadline pressure are how teams miss pages and route alerts to the wrong people. A clean parallel run takes a few weeks of calendar time and almost no risk when you do it early on your own terms. Do it in the last six months before April 2027, with every other Opsgenie customer scrambling for the same migration help, and it's a very different experience. The demands on on-call are only going up, too. Coding agents have changed how software gets built, with pull request volume doubling at some teams. A pager built for human-speed development doesn't keep pace with agent-speed deployment. The bottleneck isn't writing code anymore. It's keeping production running once that code ships. Landing on a frozen tool, or a service desk wearing an on-call hat, doesn't fix that. ## A platform, not just a pager The Rescue Program gets you off Opsgenie. What keeps you on incident.io is a different approach to reliability. incident.io is an end-to-end incident management platform built on two foundations: a living model of your entire system, and AI that knows how to use it. Catalog maps every service, team, and dependency in your organisation and keeps that model current as things change. When an alert fires, incident.io uses that context to investigate immediately. It knows what broke, what depends on it, and who owns it. Scribe transcribes your incident calls in real time so no context is lost. AI drafts post-mortems in seconds, pulling from your timeline, Slack threads, and pull requests. And automated workflows handle the operational noise throughout: naming incidents, suggesting follow-ups, surfacing similar past incidents, and drafting customer updates. Teams start by replacing their Opsgenie on-call and expand into a platform that covers the full lifecycle, from first alert to follow-up action. Opsgenie gave you alerting. We grant the rest. ## Don't wait for the smoke to clear The Opsgenie Rescue Program is available now to any team running on Opsgenie. April 2027 will arrive faster than you think, and the teams that move early are the ones who get to do it calmly. You're going to have to make a wish either way. Make a good one. Learn more at [incident.io/rescue/opsgenie](https://incident.io/rescue/opsgenie)