Opsgenie is Atlassian's on-call and alerting service, past end of sale and reaching end of support in April 2027; these pages cover moving to self-hosted GoAlert instead of Atlassian's recommended destination.
For teams forced off Opsgenie by its end of support: what GoAlert covers (schedules, rotations, escalation policies, SMS and voice through Twilio, Slack, email alerts) against Opsgenie's alerting and integrations, and when moving to Jira Service Management is the better fit.
A rebuild path from Opsgenie to GoAlert before the April 2027 shutdown: exporting schedules, timelines and escalation data through the Opsgenie API, re-creating rotations and escalation policies in GoAlert, re-pointing alert sources, and testing notifications before cutover.
Cost of ownership when Opsgenie ends: Jira Service Management licensing as Atlassian's destination against GoAlert's PostgreSQL hosting, Twilio usage for SMS and voice, setup and the effort of keeping a paging system highly available.
What to pull out of Opsgenie before April 5, 2027, when undeleted data is removed: schedules as iCalendar files and timelines through the Schedule API, the US and EU API hosts and GenieKey authentication, and the download option Atlassian describes for Data Center customers.
Opsgenie shuts down on April 5, 2027 and unmigrated data is deleted. This page sets out the choice between Atlassian's Jira Service Management path and self-hosted GoAlert or OneUptime, the export work to finish before the deadline, and a cutover timeline.
Comparing Opsgenie with OneUptime, which combines on-call schedules and escalation with status pages, incidents and monitoring: what carries over from Opsgenie, what the Apache 2.0 Community Edition includes, and what the Enterprise Edition adds.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.