From PagerDuty

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

You provide a read-only PagerDuty API key and a few decisions. PagerDuty 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 a PagerDuty user with the Admin or Account Owner 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 PagerDuty	In Oppex	Details
Services	Services	Each service is linked to its escalation policy. Each one gets a new Oppex integration key.
Escalation policies	Escalation policies	Levels keep their order, targets and escalation timeouts.
On-call schedules	Schedules	Active layers, members, rotation length (daily, weekly or monthly) and time-of-day restrictions.
Teams	Teams	Each team keeps the services linked through its escalation policies, and its own member list.
Users	Users	Every user in the account gets an Oppex account with the same email address. See Roles.
Incidents	Incidents	Your incident history moves too, so past incidents stay in one place.

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 services, schedules and escalation policies in Oppex.
Parallel run	Your monitoring tools send alerts to both PagerDuty and Oppex. Optional: Oppex compares the incidents raised in each tool every day and reports any raised in one but not the other.
Switch over	You point your monitoring tools at Oppex only, and revoke the PagerDuty API key.

What you need to provide

1. Create a read-only PagerDuty API key

1. In PagerDuty, go to Integrations > Developer Tools > API Access Keys.
2. Click Create New API Key.
3. Enter a description, such as Oppex migration.
4. Select Read-only API Key.
5. Click Create Key, and copy the key. PagerDuty shows it only once.

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.

2. Tell Oppex where and what to migrate

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

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

Roles

PagerDuty role	Oppex role
Account Owner, Admin	Workspace Admin
Manager	Service Admin
Every other role	Responder

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. Service admin assignments are not migrated. 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, revoke the PagerDuty API key.

What is not migrated

Item	Why, and what to do
Monitoring 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.
Schedule layers that have already ended	Only current and future layers matter for paging.
PagerDuty's newer shift-based schedules	These are listed in your migration summary so that you can recreate them. Classic layered schedules are migrated in full.
Features with no Oppex equivalent	For example event orchestration rules and response plays.

FAQ

Does PagerDuty stop working while the migration runs?

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

Can we migrate some services first and the rest later?

Yes. Send a spreadsheet of the first services, then another for the next batch. Anything already migrated, such as a shared escalation policy 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.