Developing
Service reliability also matters for CX: the article lists recent Atlassian disruptions as migration risks.
In 60 seconds
- Opsgenie becomes inaccessible on April 5, 2027, and unmigrated data is deleted; new sales ended on June 4, 2025.
- Atlassian's tool moves alerts, schedules and policies to Jira Service Management, with a 14-day demo and 120 days of parallel running.
- JSM alert data expires by plan: 1 month (Free), 1 year (Standard), 3 years (Premium), 5 years (Enterprise); Opsgenie Enterprise allowed indefinite retention.
- A September 14, 2026 disruption delayed alerts by an average of 22 minutes; nothing was dropped.
Impact Layer
- What changed
- The countdown to Opsgenie's shutdown is now six months, with migration details published.
- Why it matters
- On-call alerting affects how fast customers hear about and recover from incidents.
- Who is affected
- IT service, on-call and customer-support operations teams using Opsgenie.
- Martech stack area
- Customer Experience
- Stack impact
- Start with a gap review: integrations to rebuild, retention periods, SSO and mobile alert behaviour, before choosing JSM or an alternative.
- Business impact
- Moderate A CX Today analysis. Alternatives' claims (PagerDuty, incident.io, Freshworks) are vendor statements.
- Related technologies
- What to watch
- Atlassian's fix for the Slack notification delay (OPSGENIE-2626) and migration tooling for Data Center.
CX Today’s October 7, 2026 report says Opsgenie, Atlassian’s on-call and alerting product, becomes inaccessible on April 5, 2027, and unmigrated data is deleted. New Opsgenie sales ended on June 4, 2025.
The migration path
- Atlassian’s tool moves alerts, schedules and policies to Jira Service Management (JSM); customers get a 14-day demo and can keep Opsgenie for 120 days in parallel, after which it shuts down automatically unless an admin turns it off sooner.
- Tooling does not move data into JSM Data Center; Atlassian’s answer for those customers is Cloud.
- JSM alert data expires by plan: 1 month (Free), 1 year (Standard), 3 years (Premium) and 5 years (Enterprise). Opsgenie Enterprise allowed indefinite retention.
Gaps
Slack incident integrations must be rebuilt, Terraform users move to Atlassian’s Operations provider, about 24 older integration versions cannot be newly configured, the Jira mobile app lacks insistent notifications and Opsgenie SSO does not carry over. Incident templates, responder roles and rules need manual rebuilding.
Reliability
A September 14, 2026 disruption delayed alerts by an average of 22 minutes (nothing dropped), and an October 1 JSM incident delayed email-to-ticket processing. Alternatives include PagerDuty, incident.io and Freshworks (FireHydrant), each with vendor claims.
Our read
For customer-facing teams the issue is time to notice an outage. Run a gap list now and test alert delivery in the new tool before the shutdown.
Sources
- CX Today: Opsgenie end of life, the six-month countdown has started (opens in a new tab)
Source of the dates, migration path, gaps and alternatives.