← Back to Dashboard

Before you start

This step only reads. Nothing is created in your account until you review the report and confirm.

What comes across

  • Schedules, with their timezone
  • Rotations, turn lengths and handoff times
  • Coverage hours (time restrictions)
  • Rotation order and participants
  • Overrides, and the people in them

What doesn't, and why

  • Escalation-policy participants. We won't guess who a policy would have paged
  • Nested schedules as participants. Flattening a live schedule into a fixed list of people drifts silently
  • Per-rotation overrides stay whole-schedule. Ours apply to the schedule, so they cover a little more
  • Alerts and alert policies. This imports schedules only

Want the full walkthrough first? Migrating from Opsgenie covers the export, every report finding and what to do after.

Get your configuration out of Opsgenie

Two exports work. The one you'll find first by clicking around does not — see below.

  1. In Opsgenie, go to Settings → API key management and add a key with Read access.
  2. Paste it below. We use it once and never store it.

Check the region against the address you use for Opsgenie. A key from an EU account fails against the US endpoint with exactly the same error as a wrong key.

Not the calendar export. Opsgenie's Export team schedule gives you an .ics file — twelve months of who was on call, but not the rules that produced it. Rotations can't be rebuilt from that, so we'll refuse it rather than guess.
Nothing is written. You'll get a report first.