From OpsGenie

The Oppex team migrates your Opsgenie account for you. Within 24 hours of receiving access, Oppex moves all of your teams, services, escalations, on-call schedules, users and historical incidents. You do not rebuild anything by hand.

Atlassian is retiring Opsgenie, with support ending on April 5, 2027. Migrating early gives your team time to run both tools side by side before that date.

You provide a read-only Opsgenie API key and a few decisions. Opsgenie keeps working throughout, because the migration only reads from it. You choose when to switch over.

Who does what

The Oppex team runs the migration. To create the API key, you need an Opsgenie user with the Owner or Admin role. To review the result in Oppex, you need an Account Owner, Account Admin or Workspace Admin in the target workspace.

What is migrated

In Opsgenie	In Oppex	Details
Teams	Teams	Each team keeps its members and the services it owns.
Services	Services	Each service is linked to the escalation policy its team uses. Each one gets a new Oppex integration key.
Escalations	Escalation policies	Rules keep their order, targets (users, schedules or teams) and delays.
Schedules	Schedules	Rotations, participants, rotation length (daily, weekly or monthly) and time restrictions.
Users	Users	Every user in the account gets an Oppex account with the same email address.
Alerts and incidents	Incidents	Your incident history moves too, so past incidents stay in one place.

Opsgenie roles are mapped to the closest Oppex role. The Oppex team confirms the mapping with you before the migration starts.

Timeline

When	What happens
Kickoff	You send the items in What you need to provide.
Within 24 hours	Oppex migrates everything and sends you a summary, including anything that needs a manual decision.
Review	Your admins check teams, services, schedules and escalation policies in Oppex.
Parallel run	Your monitoring tools send alerts to both Opsgenie and Oppex. Optional: Oppex compares the alerts raised in Opsgenie with the incidents raised in Oppex every day and reports any raised in one but not the other.
Switch over	You point your monitoring tools at Oppex only, and delete the Opsgenie API key.

What you need to provide

1. Create a read-only Opsgenie API key

1. In Opsgenie, go to Settings > API key management.
2. Click Add new API key.
3. Enter a name, such as Oppex migration.
4. Under access rights, select Read and Configuration access. Leave Create and update and Delete cleared.
5. Click Add API key, and copy the key.

Send the key to the Oppex team through a password manager share or a one-time secret link. Do not send it by email or chat.

Opsgenie in the EU, or inside Jira Service Management

Tell the Oppex team if your account is hosted in the EU (your Opsgenie address contains eu), or if your Opsgenie data has already moved into Jira Service Management. Both use a different API address.

2. Tell Oppex where and what to migrate

Decision	What to send
Target workspace	The Oppex workspace the migrated teams and services belong in.
Scope	Either the whole account, or a spreadsheet with a Team or Service column listing the exact Opsgenie names to move.
Replacement for former employees	One Oppex user who takes the place of anyone who has left your Opsgenie account but is still named in a schedule or escalation.
Email domain	Whether your Oppex email domain differs from the one in Opsgenie. If it does, accounts are created on your Oppex domain with the same name before the @.

A scoped migration moves only the escalations and schedules that those teams and services use. Every Opsgenie user is still migrated, so people are ready for later batches.

After the migration

1. Ask each person to sign in with their work email and click Forgot your password? to set a password, or to use single sign-on if your account has it. See Logging into Oppex.
2. Ask each person to add their phone number and choose how they are paged. Migrated escalation levels notify by email until you turn on calls or SMS. See Set up how you are paged.
3. Assign service admins to each service. See Service admins.
4. Point each monitoring tool at the new Oppex integration key of its service. See Integrating Oppex with your stack.
5. After the parallel run, delete the Opsgenie API key.

What is not migrated

Item	Why, and what to do
Integrations	Each Oppex service has its own integration key. Point each tool at Oppex during the parallel run.
Personal notification rules	Each person sets their own contact methods in Oppex after signing in.
Rotations that have already ended	Only current and future rotations matter for paging.
Rotations shorter than a day	Oppex rotations are daily, weekly or monthly. These are listed in your migration summary so that you can decide how to recreate them.
Alert policies, notification policies and heartbeats	Set up noise reduction in Oppex instead. See Grouping strategy.

FAQ

Does Opsgenie stop working while the migration runs?

No. The API key can only read, so the migration cannot change anything in Opsgenie. Your team keeps being paged by Opsgenie until you switch your monitoring tools over.

Can we migrate some teams first and the rest later?

Yes. Send a spreadsheet of the first teams or services, then another for the next batch. Anything already migrated, such as a shared schedule or a user, is reused, not duplicated.

What happens to items that fail to migrate?

Oppex records each one with the reason, retries the ones that can be retried, and lists the rest in your migration summary so that you can decide what to do with them.