{"id":5876,"date":"2026-05-22T23:07:55","date_gmt":"2026-05-22T17:37:55","guid":{"rendered":"https:\/\/blog.spike.sh\/?p=5876"},"modified":"2026-05-26T15:55:39","modified_gmt":"2026-05-26T10:25:39","slug":"how-to-migrate-from-opsgenie","status":"publish","type":"post","link":"https:\/\/blog.spike.sh\/how-to-migrate-from-opsgenie\/","title":{"rendered":"How to migrate from OpsGenie before the shutdown"},"content":{"rendered":"\n

TL;DR<\/h2>\n\n\n\n

Atlassian is shutting down OpsGenie on April 5, 2027, and will delete all unmigrated data after that date. You can export schedules, policies, and alert history via the REST API, but integrations and Slack configurations must be rebuilt manually. Spike<\/a> is the best OpsGenie replacement because it mirrors OpsGenie\u2019s on-call and alerting workflows. It starts at $7\/user\/month and offers 50% off for OpsGenie users for the first six months.<\/p>\n\n\n\n

\n\n\n\n

The OpsGenie shutdown: what you need to know<\/h2>\n\n\n\n

Atlassian stopped new OpsGenie sales<\/a> on June 4, 2025. The full shutdown happens on April 5, 2027<\/strong>, at which point Atlassian deletes all data from accounts that have not completed migration.<\/p>\n\n\n\n

Date<\/th>What happens<\/th><\/tr><\/thead>
June 4, 2025<\/td>New sales stopped. No new purchases, trials, or plan changes<\/td><\/tr>
April 5, 2027<\/td>Full shutdown. All access ends and Atlassian deletes unmigrated data<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The platform is now in maintenance-only mode, which means no new features, no new integrations, and limited bug fixes. You can still renew your current subscription until shutdown, but you cannot upgrade, downgrade, or change your plan.<\/p>\n\n\n\n

For the full breakdown of the shutdown timeline and data loss risks, read our detailed OpsGenie shutdown guide<\/a>.<\/p>\n\n\n\n

\n\n\n\n

What you can and cannot export from OpsGenie<\/h2>\n\n\n\n

Not everything in your OpsGenie setup can be moved. Before you start the migration, you need to understand what transfers cleanly and what has to be rebuilt from scratch.<\/p>\n\n\n\n

What you can export<\/h3>\n\n\n\n
Data<\/th>How to export<\/th><\/tr><\/thead>
Escalation policies<\/td>OpsGenie REST API<\/td><\/tr>
On-call schedules<\/td>OpsGenie REST API<\/td><\/tr>
User lists<\/td>OpsGenie REST API<\/td><\/tr>
Alert history<\/td>REST API + built-in export settings<\/td><\/tr>
Team configurations<\/td>OpsGenie REST API<\/td><\/tr>
Routing rules<\/td>OpsGenie REST API<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What you cannot export<\/h3>\n\n\n\n
Data<\/th>Why it doesn’t transfer<\/th><\/tr><\/thead>
Integrations<\/td>Each integration uses API keys and webhook URLs tied to your OpsGenie account. Every integration must be manually reconfigured in your new platform<\/td><\/tr>
Slack configurations<\/td>The Slack app connection is specific to OpsGenie. You need to set up Slack integration from scratch in your new tool<\/td><\/tr>
Notification preferences<\/td>Individual user notification rules do not export. Each team member must reconfigure their personal alert preferences (phone, SMS, Slack, email, quiet hours)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Start this process early. Exporting data under deadline pressure is how teams lose configurations they assumed were backed up.<\/p>\n\n\n\n

Key point:<\/strong> On-call schedules, escalation policies, and alert history can be exported through the OpsGenie REST API. Integrations, Slack configurations, and notification preferences cannot be transferred and must be rebuilt manually.<\/p>\n\n\n\n

\n\n\n\n

How to prepare for the OpsGenie migration<\/h2>\n\n\n\n

Migration planning doesn’t need to be overwhelming, but it does need to start well before April 2027. Here is a practical breakdown of what to do and when.<\/p>\n\n\n\n

Phase 1: Audit your current OpsGenie setup<\/h3>\n\n\n\n

Before you evaluate any replacement, document what you actually have in OpsGenie.<\/p>\n\n\n\n