Migrate from opsgenie
Migrate from Opsgenie
Moving your on-call setup between products is nerve-racking: get one rotation wrong and the wrong person — or no person — gets paged. WarnFire’s migration is built around one promise:
Nothing changes until you press Apply. The importer only reads Opsgenie and builds a draft you can inspect, compare, and rehearse. And if you apply and change your mind, there’s a real undo.
The whole flow lives under Integrations → Opsgenie.
Step 1 — Connect (read-only)
- In Opsgenie, create a read-only API key that can read configuration. (Not an alert-only team key — the connect panel reminds you.)
- In WarnFire, choose your Opsgenie region (United States or European Union), paste the key, and press Validate and connect.
WarnFire checks the key works, then stores it encrypted. Only the last few characters are ever shown again.
Step 2 — Inventory
Press Run first inventory. WarnFire reads your Opsgenie users, teams, schedules, rotations, overrides, escalation policies, and services, and builds a draft of how each would look in WarnFire.
Every item gets an honest grade:
| Grade | Meaning |
|---|---|
| Exact | Translates perfectly. |
| Needs review | Translates with a small approximation — read the note. |
| Ambiguous | Opsgenie allows more than one interpretation — a human should decide. |
| Unsupported | WarnFire doesn’t model this construct; it’s listed so nothing is silently dropped. |
Click any grade to filter the list. Each item shows the sanitized Opsgenie original side by side with the proposed WarnFire draft.
Step 3 — Read the readiness report
The cutover readiness panel gives a plain go/no-go: either “Ready to cut over” or a list of specific blockers that would break paging (like a schedule referring to a person who wasn’t importable). Warnings are shown too, but only blockers stop you.
Step 4 — Rehearse with shadow runs
Two rehearsals happen automatically, using real data:
- Schedule shadow — for the next week, hour by hour: would WarnFire page the same person Opsgenie would? Any hour that differs is listed with when, who each system would page, and why.
- Alert shadow — replays a sample of your recent real Opsgenie alerts against the draft and checks whether the person who actually handled each one would have been paged by WarnFire. You get an agreement percentage and the specific divergences.
These two panels are the “don’t take our word for it” step. If they’re green, your draft demonstrably behaves like your current setup.
Step 5 — Apply
Press Apply to live configuration. WarnFire creates the responders, schedules, and escalation policies from your reviewed draft — all at once, so there’s no half-migrated state. Anything that couldn’t be translated is returned as a skipped list for manual follow-up (services always need a fresh WarnFire integration key — your Opsgenie credentials are never reused).
Apply works once per inventory, and only when the readiness report says ready.
Step 6 — If you need to undo
Roll back deletes exactly what Apply created — nothing more — and returns the import to its reviewed state so you can adjust and apply again.
One protective rule: if anything the migration created is already in real use (a policy attached to a live service, a responder who has been paged), rollback refuses and deletes nothing, rather than half-unwinding a setup you’ve started relying on.
After the switch
Point your monitoring tools at WarnFire (Alertmanager or the Events API), send a test alert per service, and run both systems side by side for a few days before turning Opsgenie notifications off.