Migrate from Opsgenie

Rotations and escalation steps here can only name people on your team, and the importer matches Opsgenie users to them by email. Invite your responders first. The preview lists anyone it could not match, so nobody is silently dropped from a rotation.

In Opsgenie, add an API integration with read access and copy its key. The importer reads your heartbeats, schedules, escalations and user list with it and writes nothing to Opsgenie. The key is used for the import and not stored, so you are asked for it again on the import step. Choose the EU region if your Opsgenie address is on the EU instance.

In your dashboard, open Import from another service and use Import from Opsgenie. The preview shows each heartbeat with its interval, each schedule rotation with its people, handoff time and time zone, and each escalation with its steps. Heartbeats import on every plan, Free included, and count as monitors (10 on Free). Schedules and escalation policies are on-call, which starts on Pro, so they import on Pro and Business, by an owner or admin. Choosing an escalation brings the schedules it pages along with it.

Each heartbeat gets a new ping URL, listed once on the result screen; the URL is the credential, so it cannot be the Opsgenie one. Change each job to call it. A new heartbeat waits for its first ping and alerts nobody until then, so jobs can move over one at a time. To report failures and run times too, see failed and stuck cron runs. Then attach the imported escalation policy to your checks, or make it the account default, under On-call.