Migrate from OpsGenie to Wachd
A step-by-step checklist to move your schedules, escalation chains, integrations, and notification rules — and end up with something better than what you started with.
What you get that OpsGenie never had
OpsGenie routed alerts well. What it never did was tell you anything useful about the alert itself. Every page arrived with a title and a severity — and then you spent 45 minutes figuring out what actually happened.
Wachd collects the last commits, error logs, and metric history around the alert automatically, strips PII, and runs AI correlation before the page reaches you. By the time your phone rings, the probable cause is already written. That part has no equivalent in OpsGenie.
OpsGenie concepts mapped to Wachd
Most of what you built in OpsGenie carries over directly. Two things are different by design.
| OpsGenie | Wachd |
|---|---|
| Teams | Teams |
| Services | Team data sources |
| Schedules | Schedules |
| Escalation policies | Escalation policies |
| On-call overrides | Schedule overrides |
| Integrations (inbound) | Webhooks |
| Notification rules | User notification rules |
| SSO | SSO (Entra, Okta, Google) |
| Maintenance windows | Coming soon |
| Incident reports | Incident history + AI analysis |
Migration checklist
Six weeks for a mid-size team running multiple rotation layers. Smaller teams can move faster.
Deploy and set up your team
- ☐Deploy Wachd on your Kubernetes cluster (helm install wachd wachd/wachd)
- ☐Create your team(s) — one per on-call group or business unit
- ☐Set up SSO (Entra, Okta, or Google) or create local users for each engineer
- ☐Assign roles: viewer, responder, or admin
Recreate schedules and escalation
- ☐Recreate each on-call rotation — name, members, recurrence
- ☐Set time restrictions per rotation (business hours, nights, weekends, always)
- ☐Recreate escalation policies: timeout per layer, repeat interval, max repeats
- ☐Create any known upcoming overrides (booked vacations, on-call swaps)
Move your integrations
- ☐Create a Wachd webhook for each OpsGenie integration — one URL per source
- ☐Update Grafana, Datadog, or Prometheus to send alerts to the new webhook URLs
- ☐Connect data sources per team: GitHub repo, Loki, Prometheus (for AI context collection)
- ☐Choose your AI backend: Ollama for air-gapped, Claude or OpenAI for cloud
- ☐Fire a test alert and confirm the full pipeline — webhook → context → AI → notification
Set up notifications per engineer
- ☐Set per-user notification rules: which channel (email, SMS, voice, Slack) for which event
- ☐Configure Slack bot token and alert channel per team
- ☐Configure Twilio account SID and auth token if using SMS or voice calls
- ☐Verify each engineer receives a test page and can acknowledge it
Run in parallel, then cut over
- ☐Run Wachd and OpsGenie in parallel — both receive the same alerts for one week
- ☐Verify real incidents appear and are handled correctly in Wachd
- ☐Switch primary on-call notifications to Wachd
- ☐Keep OpsGenie configured as a silent fallback
Done — export and close OpsGenie
- ☐Export your OpsGenie incident history as CSV (Settings → Export) before the deadline
- ☐Export on-call schedule history and team member list
- ☐Document any alert routing rules your team relied on
- ☐Cancel OpsGenie subscription
Export from OpsGenie before April 2027
Once OpsGenie shuts down, this data is gone. Export it early — do not wait until the last month.
- →Incident history — Settings → Reports → Export as CSV
- →On-call schedule history — useful for compliance audit trails
- →Team member list with phone numbers and email addresses
- →Integration list — note every webhook URL, API key, and source type
- →Alert policy and routing rules — recreate the logic in Wachd webhooks
- →Notification rule configuration per user
Start the migration now
Wachd deploys in under 30 minutes on any Kubernetes cluster. Run it in parallel with OpsGenie until you are confident. No account required, no per-user fees, Apache 2.0.
Questions? sales@wachd.io or join the Discord.