Hi, I’m Ivan — I lead Atlassian consulting here at iTmethods. I work with all kinds of teams who rely on Opsgenie for incident response, on-call management, and alerting.
When Atlassian announced they were retiring Opsgenie (new sales ended June 4, 2025, and full support gone by April 5, 2027), I started getting the same question over and over:
“Do we really need to do something about this now?”
Short answer: yes, and I’ll explain why, along with a simple checklist to help you get ahead of it.
If your artifact management or CI/CD workflows are still relying on manual oversight or scattered tooling, you’re not just slowing down your team. You’re exposing your business.
Here’s how leading engineering and security teams are rethinking open-source governance with the Sonatype Platform, alongside the operational simplicity of a managed solution from iTmethods.
Why start now?
I get it. 2027 feels like forever away. But trust me, you don’t want to be scrambling two years from now trying to figure out where your alerts went or why your billing suddenly broke.
Here’s what I’ve seen happen when teams wait too long:
- Someone forgets about it until renewal season. Then there’s a mad dash to migrate before the contract ends.
- Billing platforms get in the way. (Fun fact: one customer couldn’t even schedule a migration because they were on an older billing system and didn’t realize it.)
- Custom setups don’t map cleanly. That clever alert escalation rule you built in 2021? You’ll want time to replicate it properly in the new system.
So… what are my options?
There are two Atlassian-native destinations for Opsgenie users:
| Platform | Best used for | Highlights |
|---|---|---|
| Jira Service Management (JSM) | Centralized incident response and IT/DevOps teams | Built-in alerting, on-call schedules, AI virtual agent, ITSM workflows |
| Compass | Engineering teams managing microservices and distributed teams | Service catalog, scorecards, component ownership |
Honestly? Most teams I work with are happy with Jira Service Management. It picks up where Opsgenie leaves off and will add a whole lot more.
That said, I get the hesitation. If you’ve seen Reddit threads or talked to teams who struggled with early versions of JSM, you’re not alone. I’ve had customers ask things like:
“Isn’t JSM overly complex?”
“Do I have to rebuild everything from scratch?”
“Will it actually handle our on-call needs like Opsgenie does?”
The truth? Those concerns were valid two or three years ago. But JSM has come a long way. Here’s what we’ve seen in the field:
- Built-in alerting and on-call scheduling is powered by the same Opsgenie engine, so you’re not losing core functionality.
- Incident management, escalation rules, and integrations are smoother and more customizable than they used to be.
- The new AI virtual agent, real-time collaboration, and workflow automation bring added value you won’t get with Opsgenie alone.
- With the right setup (which we help with), JSM can reduce complexity, not increase it.
And for teams that don’t have the internal bandwidth to learn it all, that’s where we come in.
If JSM feels like more than you want to manage, you don’t have to go it alone. We manage it for several customers today. We handle updates, workflows, tuning, and more.
In short: it’s not perfect out of the box, but with the right configuration, JSM is a solid, future-proof replacement for Opsgenie and a powerful upgrade for teams that want more visibility, structure, and automation.
Your Opsgenie Migration Checklist
This is the actual process I walk through with clients. Whether you’re going DIY or working with a partner, it’ll help you stay ahead.
1. Take inventory
- What alerts, schedules, and integrations are live?
- Who owns them? Who’s on-call?
- Any automation in place?
2. Pick your destination
- If you need alerting, incident workflows, SLAs, etc., JSM is usually your best bet.
- Compass is great for engineering orgs with lots of microservices and component tracking.
(Still not sure? We help teams figure this out all the time.)
3. Set your migration date
- This kicks off automated data migration.
- Double check you’re on an Atlassian-supported billing platform (this trips people up more often than you’d think).
4. Get billing approval
- You’ll need your Atlassian Billing Admin to approve it.
- Without that, you can’t move forward. It’s that simple.
5. Prep your configuration
- Map Opsgenie features to JSM/Compass equivalents.
- Build out alerting logic, escalation paths, and workflows.
6. Test in a demo environment
- Atlassian offers a 30-day trial to test the migration.
- Pro tip: invite your team in early so they can poke around and flag any gaps.
7. Handle post-migration setup
- Finish configuring integrations, permissions, automations.
- Use the personalized migration checklist Atlassian provides in the destination tool.
8. Decommission Opsgenie
- Make sure you’ve exported anything you might need.
- Shutting it off is permanent (no take-backs!).
If your team is already stretched thin, or if you’re juggling five other IT projects at once, trying to manage an Opsgenie migration probably isn’t the best use of your time.
Why Work with iTmethods?
We’re not just here for the migration. We help teams:
- Configure JSM the right way (not just ‘get it running’)
- Align to ITIL and other ITSM frameworks without the jargon
- Streamline processes so on-call doesn’t feel like chaos
- Manage JSM long after the migration so you can focus on real work
Whether you need a one-time boost or long-term managed services, we’ve got you covered.
Get a free migration consultation
Let’s chat. No pressure, just a conversation to understand where you are now and how we can help you move forward.
If you’re still on Opsgenie, the clock is ticking, but you’ve got time if you start now.
And if your team wants help navigating the path to JSM (and actually running it well), that’s what we’re here for.
— Ivan
Atlassian Consultant @ iTmethods
