Skip to main content

​
You do not have to migrate on day one

WHAWIT can ingest alerts from PagerDuty and Opsgenie. Point your existing tool at WHAWIT and it picks those alerts up, correlates them, and runs its investigation — while your current rotations keep paging exactly as they do today. That means you can evaluate WHAWIT against real incidents, on your own systems, without changing anything for the people carrying the phone.
1

Keep paging where you are

Send your alerts to WHAWIT in parallel. Nothing changes for responders. Your existing escalation stays authoritative.
2

Compare the investigations

For each incident, compare what WHAWIT concluded against what your team found. This is the part that decides whether the migration is worth doing, and it costs you nothing but time.
3

Bring the rotations across

Import them from Opsgenie in one step, or rebuild them by hand. Both systems can exist simultaneously — nothing goes dark during the transition.
4

Cut over

Turn off the old escalation. One system, and the page now arrives with the analysis attached.

​
Coming from Opsgenie? Do not retype anything

Opsgenie reaches end of support on 5 April 2027, and Atlassian deletes unmigrated data on that date. WHAWIT imports your teams, schedules and escalation policies straight from the Opsgenie API — you paste a key, review what will be created, and apply.

Importing from Opsgenie

The full guide: the API key you need, what maps to what, what does not come across, and what to verify before you turn Opsgenie off.
Coming from PagerDuty, the rest of this page is the manual path — and it is worth reading either way, because the checks at the end apply to both.

​
Mapping the concepts

The vocabulary differs slightly. The concepts line up:

​
What to check once the rotations are in

This is the most common thing to get wrong in a migration. Handoffs are evaluated in the schedule’s own timezone — set it explicitly rather than assuming the default is right.
WhatsApp and SMS are delivered to the number on the user’s profile. A user without one is silently skipped for those channels. Fill these in before you depend on an SMS escalation level.
Mark one policy as the organization default. It catches any incident raised by something you have not explicitly configured.
Preview resolves a policy as if an incident had just fired and shows who would actually be paged at each level, with current rotations and overrides applied. Run it on every policy you imported or rebuilt — it is the cheapest way to find a coverage gap.
Look at the shifts each schedule produces across a whole week. Restrictions that do not quite meet leave a window where the schedule resolves to nobody.
Planning a migration? Email [email protected] and we will walk your existing schedules and escalation policies with you. If you are already on WHAWIT and something is not resolving the way you expect, [email protected].

​
Leaving Opsgenie specifically

Teams migrating off Opsgenie are usually doing it on someone else’s timetable rather than their own. If your rotations have to move somewhere regardless, it is worth moving them somewhere that also does the triage — the import does the mechanical work, and the investigation is what you get on top.

​
Next

Schedules and rotations

Building the rotations you are moving across.

Escalation policies

Rebuilding the escalation chains, and previewing them.