Skip to main content

Import from PagerDuty or Opsgenie

If you already run on-call in PagerDuty or Opsgenie, you can copy your schedules and escalation policies into Regen instead of rebuilding them by hand. The import reads from your existing account and creates the matching records in your workspace. A read-only API key is enough, so it cannot change anything in the other tool.

Importing is done by workspace admins under Migrations in the left-hand menu.

What is imported​

ImportedNot imported
Schedules, with their rotation layersAlert and incident history
Escalation policies, with their tiersAlert sources and integrations: you point your monitoring tools at Regen yourself
Chat connections, such as Slack: you connect these in Regen

Check the Notes in the preview and the Warnings after the import. They list anything that could not be copied exactly.

Before you start​

  • Create a read-only API key in the other tool. The import only reads data.
    • PagerDuty: Integrations → API Access Keys.
    • Opsgenie: Settings → API key management.
  • Know which region your account is in: US or EU. PagerDuty EU accounts use api.eu.pagerduty.com. Choosing the wrong region makes the key fail with an authorization error.

Run the import​

  1. Open Migrations and choose Import from PagerDuty or Import from Opsgenie.
  2. Choose your region.
  3. Paste the API key. You can show or hide it as you type.
  4. Choose Preview Import. Regen fetches your data and shows what it would create, such as Primary On-Call – 2 layers, 4 users and Default Escalation – 3 tiers. Nothing is created yet.
  5. Review the preview and any notes.
  6. Choose Confirm Import.

When it finishes, Regen shows how many schedules and escalation policies were imported, followed by any warnings and errors.

Names that already exist​

If a schedule or policy with the same name already exists in Regen, it is skipped and a warning tells you. This makes it safe to run the import more than once.

To replace existing records with the same name, tick Overwrite records with conflicting names before you confirm.

Things that need your attention​

  • Custom rotations in PagerDuty, which do not repeat on a fixed interval, cannot be copied. They are skipped with a warning. Recreate them under On-Call → Schedules.
  • Team targets in an escalation tier are skipped with a warning. Add the people or schedule to that tier yourself.
  • A layer with no people is imported with an empty participant list.

After the import​

  1. Open On-Call and check each schedule: the rotation times, time zone and who is in it.
  2. Check each escalation path and its tier timings.
  3. Make sure everyone who will be paged has an account, and has set up notifications so Regen can reach them.
  4. Point your monitoring tools at Regen. See alert sources.
  5. Run both systems side by side for a short time, then switch your alert sources over.