OPSGENIE MIGRATION
Moving off Opsgenie?
Run on-call to ITSM on Incident Lake.
Atlassian has announced that Opsgenie will reach end of support on April 5, 2027. After that date, Opsgenie can no longer be accessed, and any data not migrated to Jira Service Management will be deleted. With Incident Lake, you can build your service operations on one shared record, from on-call phone paging and first response to problem and change management and service requests. You can also start alongside Jira Service Management and migrate step by step.
- Ends April 5, 2027
- On-call and phone paging
- First response in Slack and Teams
- Problem, change and service requests
- Works alongside Jira Service Management
Opsgenie migrations tend to focus on moving schedules and escalation policies. But most of the time in an incident is spent after someone gets paged: who leads, what the severity is, who has been told what. A migration is a good moment to fix that part too.
Three things migrations tend to miss
Your incident history
Data left in Opsgenie will be deleted when support ends. Export the incident records and postmortems you need to keep before the deadline.
What happens after the page
Opsgenie mainly notifies and pages on-call responders. Coordination, task assignment and stakeholder updates often still depend on individual experience and scattered chat threads.
Incidents during the cutover
Incidents don't wait for your migration. Decide how responses will run, and where records will live, while old and new tools overlap.
What Incident Lake does after the page (60 seconds)
Opsgenie end-of-life timeline
Dates are based on Atlassian's official announcement, as of November 2026, and may change.
March 4, 2025 | Atlassian announces end of life
Atlassian names Jira Service Management as the migration path.
June 4, 2025 | End of sale
New purchases and sign-ups, as well as plan upgrades and downgrades, have ended. Existing customers can still add seats, and renewals are allowed only for terms that end before April 5, 2027.
Before April 5, 2027 | Export records and finish the cutover
Beyond schedules, escalations and integrations, decide which alert and incident records to keep, and export them. Allow time for running old and new tools in parallel.
April 5, 2027 | End of support
Opsgenie can no longer be accessed. Data not moved to Jira Service Management will be deleted.
On-call to ITSM, on Incident Lake alone
Schedules and phone paging, first response, problem and change management and service requests all run on one shared record. If you can't switch everything at once, migrate to Jira Service Management as Atlassian recommends and start by using it alongside Incident Lake. People make the decisions; the AI suggests and drafts.
Run everything on Incident Lake
Build on-call, incident response, problem and change management and service requests with Incident Lake alone. No switching between tools, no copying records across.
Start alongside Jira Service Management
Migrate on-call and paging to Jira Service Management, and run first response, records and postmortems in Incident Lake. Response tasks can sync with Jira issues. Once your process is settled, you can migrate on-call to Incident Lake as well and run everything in one place.
On-call schedules and escalation
Set daily or weekly rotations, handoff times and overrides. Unanswered calls are retried, then passed to the next person in the rotation. Automatic escalation when a response deadline is missed is supported too.
Phone paging
Incident Lake phones the person on call when an incident starts or an escalation fires. On the call, the AI briefs them, answers questions from the record, and logs the decisions they make as notes.
Alert intake and first response
Receive alerts and alert emails from Datadog, Grafana, Zabbix, Sentry and more, and open incidents in Slack or Teams. Confirm the commander, severity and affected services one by one.
ITIL service management
Problem management with known errors, change and release management synced with GitHub, a service catalog, service requests with approvals, a self-service portal, IT assets and a CMDB.
Try it on a real incident before you migrate
The Free plan connects one Slack or Teams workspace and one monitoring tool at no cost. See how your everyday incident response changes while the migration is underway.
Start free trialFor details on on-call and service management features, see the help center.
How the migration works
Keep your existing monitoring and ticketing. On Annual plans, our forward deployed engineers (FDE) work with you from sorting out alert routes to importing past records.
1. Decide where paging goes
Decide whether to migrate on-call paging to Incident Lake now or keep it in Jira Service Management for the time being, then point your monitoring alerts to it.
2. Connect Slack or Teams
Enable the agent and choose the channels where incidents are detected automatically. Start it with an “@Incident Lake go” mention.
3. Import past records and runbooks
Import incident records exported from Opsgenie with CSV. Add postmortems and runbooks as knowledge, so they can be matched against similar incidents.
4. Try one, then expand
Check how it works with a single incident or one drill scenario, then extend to more teams and services.
Incident records are your most sensitive information
Root causes, vulnerabilities, customer impact. We publish how the service is run and how data is handled, so you can check before you trust us with it. Permission groups come with Team and above, audit log and SAML SSO with Annual plans, and Self-Hosted with the Annual plan's Custom tier.
Independent assurance
Incident Lake has received a SOC 2 Type 1 report and is undergoing a Type 2 audit. SIGQ, the operator, is ISO/IEC 27001 certified.
Run it in a closed network
Self-Hosted runs inside your environment, including our in-house model Otter, and uses no external LLM API for inference.
Control who gets in
SAML SSO and IP restrictions. Sign in through your own identity provider.
Control what they see
Per-feature permission groups and RBAC tags separate viewing, editing and admin rights.
Keep a trail
The audit log shows who did what, and when. Integration secrets are encrypted per tenant.
AI proposes, people decide
People confirm severity, contain incidents and submit external reports. Connections to monitoring, code and docs are read-only.
FAQ
Can we run on-call with Incident Lake alone?
Yes. With the on-call add-on, you can set up schedules, overrides, escalation and phone paging. On-call responders are reached by voice call and in-app notifications.
Can we build ITSM without Jira Service Management?
Yes. Beyond incident management, Incident Lake includes problem management, change and release management, a service catalog and service requests, a self-service portal, IT assets and a CMDB. You can also migrate to Jira Service Management, start by using it alongside Incident Lake, and consolidate step by step.
Can we bring over our Opsgenie records?
Yes. Import exported incident records with CSV, and add postmortems and runbooks as knowledge. We can work with you on how to migrate.
How do we receive monitoring alerts?
Incidents can be opened from Datadog, Grafana, Zabbix, Sentry, Instana and Rollbar alerts. Alert mailboxes in Outlook are supported as well.
When should we start?
Support ends on April 5, 2027. Allow time for setting up your new tools, running them in parallel and exporting records, and start early. On the Free plan, you can test it on your own incidents before signing a contract.
Does the AI make decisions on its own?
No. The AI suggests the commander, severity and affected services, and people in the thread confirm them. Nothing is executed from an on-call call, and it never declares resolution or contacts outside parties automatically.
Source: Atlassian, “Opsgenie licensing” https://www.atlassian.com/licensing/opsgenie (checked November 17, 2026). Dates and terms follow Atlassian's announcement and may change. Incident Lake features are based on the help center https://support.incidentlake.com/ as of November 17, 2026. On-call is an add-on. Opsgenie, Jira Service Management and Statuspage are trademarks of Atlassian. This page does not imply any partnership with or endorsement by Atlassian.
FREE TRIAL
Try it for free
and see for yourself
Two fields, about two minutes. We set up your workspace and email the login, usually within one to three business days. No sales call unless you ask for one.