{
  "id": 5880535,
  "title": "Leaving Opsgenie before April 2027 - a migration checklist and step by step guide",
  "url": "https://urgent.news/2026/09/06/leaving-opsgenie-before-april-2027-a-migration-checklist-and-step-by",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-06T01:14:27.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/sandeep_sidhu/leaving-opsgenie-before-april-2027-a-migration-checklist-and-step-by-step-guide-2djb"
  },
  "original_language": "en",
  "account": "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.\n\nThe 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.\n\nKey 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.",
  "summary": "Atlassian stopped selling Opsgenie to new customers on 4 June 2025. Support ends on 5 April 2027. On that date access shuts off and unmigrated data is deleted. You have a hard deadline to move schedules, escalations, users, and integrations to a new system. The migration is not automatic, whatever the destination. Six things do not survive the move intact: rotation layers, time restrictions,…",
  "key_points": [
    "Opsgenie sales end April 2027, migration deadline April 5, 2027",
    "Manual export via Opsgenie REST API required for data transfer"
  ],
  "editors_take": "The end of Opsgenie support in April 2027 prompts users to migrate to a new system, requiring manual recreation of certain components and careful data export and mapping.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}