OPSGENIE MIGRATION
Leaving Opsgenie? Split the job before you pick the tool.
Based on public information as of 26 October 2026. Spot an error? Tell us through the contact form and we will fix it.
The dates Atlassian has published
Opsgenie end of sale took effect on 4 June 2025. End of support is 5 April 2027: access stops that day, and data not moved to Jira Service Management is deleted. Atlassian points customers to Jira Service Management as the destination.
Sources: atlassian.com/licensing/opsgenie and atlassian.com/software/opsgenie/migration, accessed 26 October 2026.
Short version: keep paging separate
Opsgenie was mostly about schedules, paging and escalation. Incident Lake is not an on-call tool, and we would rather say so up front. Move paging to Jira Service Management or another on-call product, and let Incident Lake run what happens after the page: coordination in Slack or Teams, the record, the postmortem and any regulatory clock.
Four steps
Re-route alerts
Paging goes to your new on-call tool. Alerts that should open an incident go from your monitoring tools to Incident Lake.
Connect Slack or Teams
Enable the agent and choose which channels it watches.
Bring your history
Import past incidents and runbooks via CSV and the knowledge approval queue, with a forward-deployed engineer alongside.
Prove it on one incident
Run one real incident or one drill end to end before you widen the rollout.
Migration checklist
- On-call schedules: move to your on-call tool. Incident Lake does not hold them
- Escalation policies: same. Recreate your severity definitions in Incident Lake so the agent can suggest the right level
- Status page: connect Statuspage, or use the Incident Lake status page
- Postmortems and history: export and import as knowledge so similar-incident search can use them
- Opsgenie data: export anything you need before 5 April 2027
Plan the move with us
A forward-deployed engineer can map your alert routes and import history with you. Or start free and try it on a single incident first.
Talk to an engineer →Opsgenie, Jira Service Management and Statuspage are trademarks of Atlassian. Other names are trademarks of their respective owners.
Whichever route you take, the division of labour in Incident Lake stays the same: the agent proposes a commander, a severity and the affected services, and the people in the thread confirm each one. It never declares an incident resolved or files a report with a regulator on its own.
Anything on this page about regulatory deadlines is general information, not legal advice. Confirm your obligations with your regulator's guidance and qualified counsel.