Move your on-call.Keep your bearings.
Your schedules and escalation rules carry years of operational knowledge. Start with a migration assessment that makes that knowledge explicit.
Migration enquiries are open. Automated imports and feature parity are not yet available or promised.
The date to plan around
April 5, 2027
Atlassian’s announced end of support for Opsgenie. Confirm the dates and options that apply to your account with Atlassian.
01 The migration plan
Prove the path before you move the traffic.
This is the assessment framework we want to work through with early-access teams. Scope, supported integrations and timing need to be agreed for each migration.
- 01
Inventory before importing
List teams, users, schedules, overrides, escalation policies, integrations and alert rules. Record time zones and ownership. Identify the history you need to retain.
- 02
Map behaviour, not just fields
Agree how each routing rule, priority, alias and escalation should behave in the destination. Document gaps and unsupported features before committing to a move.
- 03
Rehearse the hard cases
Test out-of-hours alerts, unacknowledged pages, overrides, duplicate alerts and recovery events. Verify who is notified and who takes over. Avoid duplicate production paging during the rehearsal.
- 04
Cut over with a way back
Assign an owner, choose a change window and define rollback criteria. Validate each alert source after switching. Keep access to the old configuration until the new path is verified.
02 Before you commit
The questions worth asking now.
Can I import my Opsgenie configuration today?
No self-service importer is available yet. Send a description of your setup so we can discuss the scope and assess fit. Do not send API keys, secrets or incident exports by email.
Will every Opsgenie feature be supported?
We cannot promise full parity. Schedules, escalation, routing, integrations and historical records each need an explicit mapping and a documented decision about any gaps.
What does migration cost?
Platform pricing and migration terms have not been published. We will agree scope and commercial terms before you commit.
What should I include in an enquiry?
Your team size, number of schedules and integrations, critical alert sources, requirements and target cutover date. A configuration summary is enough to start.
Start with your current setup.
Tell us what needs to move, and what cannot be missed.