Leaving Opsgenie before April 2027 - a migration checklist and step by step guide

Atlassian discontinued new customer sales of Opsgenie on June 4, 2025, with support ending on April 5, 2027. To migrate schedules, escalations, users, and integrations, a migration checklist and step-by-step guide is provided. Six components do not carry over: rotation layers, time restrictions, overrides, escalation delays, heartbeats, and email senders. These must be manually exported, mapped, and repointed in the new system.

The migration process starts with exporting users, schedules, escalations, and integrations via the Opsgenie REST API. The exports take approximately ten minutes and produce JSON files containing user, schedule, escalation, and integration data. Users include fields like ID, username, full name, role, time zone, blocked status, verification status, and creation timestamp.

Schedules include ID, name, timezone, enabled status, owner team, and rotation data. Escalations and integrations include ID, name, timezone, enabled status, and integration type.

Key actions include configuring API key access with Read and Configuration Access rights, selecting the appropriate API host based on account location (US or EU), and running sanity checks on exported data to ensure accuracy. Rotation layers, time restrictions, and escalation delays must be manually interpreted and mapped to the new system, as these elements do not migrate automatically.

Once base rotations are established, overrides can be recreated manually in the new tool. It is crucial to keep the exported JSON files as they provide the only record of the current configuration.