Last updated: November 1, 2026 — migration-help wording; product steps verified October 14, 2026.
Step-by-Step Migration
Create an Integration, Copy the API Key
Create your OpsPing workspace, then open Integrations in the dashboard, create an API integration, and copy the key. The mobile setup flow provides the QR code for connecting each responder's app.
# Primary header:
Authorization: OpsPingKey abc123-def456-ghi789
# Also accepted (GenieKey-compatible authorization):
X-OpsPing-Key: abc123-def456-ghi789
Authorization: GenieKey abc123-def456-ghi789
Repoint Alertmanager or Your Grafana Contact Point
If you already use an OpsGenie-compatible receiver, update both its destination and credential while keeping your routing, grouping, and inhibition rules:
For a Grafana or Alertmanager webhook receiver rather than opsgenie_config, create a Grafana integration in OpsPing and point the contact point at its generated inbound URL. Preserve the source system's routing rules, then test both firing and resolved notifications.
Rebuild Schedules and Escalation Chains
OnCall schedules and escalation chains don't have a one-click export we can consume, so this step is honest work: recreate your rotations and escalation policies in the OpsPing dashboard, or script it against the OpsPing API (API reference) — teams typically finish in under an hour per rotation. If you get stuck, email [email protected] and we'll help async.
Verify through the Real Receiver
Trigger a test firing and resolution through the repointed Grafana contact point or Alertmanager receiver. Confirm priority, tags, service/team routing, delivery to the intended responder, and closure by alias. The direct API request below is useful only as a separate credential and ingestion smoke check:
curl -X POST https://api.opsping.com/v2/alerts \
-H "Authorization: OpsPingKey YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message": "Checkout migration smoke test",
"alias": "checkout-migration-smoke-01",
"priority": "P2"
}'
Install the App and Retire Cloud Connection
Grafana Cloud Connection mobile push for OnCall OSS ended with archival. Self-hosted OnCall can still use separately configured third-party push services or your own Twilio credentials, but it no longer receives the former Cloud Connection service. The OpsPing app provides iOS Critical Alerts and an Android P1 alarm path; add verified voice or email channels where your response policy requires fallback.
What Transfers — and What Doesn't
| Capability | Migrates? | Notes |
|---|---|---|
| Alertmanager routing (groups, inhibition, receivers) | ✓ Yes | Keep the receiver logic; update the OpsGenie-compatible destination and API key, or use the generated Grafana webhook URL |
| Grafana Alerting contact points | ✓ Yes | Use an updated OpsGenie-compatible endpoint/key or an OpsPing Grafana integration webhook |
| Phone-call alerting | ✓ Yes | Via verified voice-call fallback; push critical alerts remain the primary path |
| Mobile push paging | ✓ Yes | The OpsPing app — iOS critical alerts + Android DND-bypassing P1 alarm |
| Schedules & rotations | ~ Manual | Recreate in dashboard or via API; typically <1 hour per rotation |
| Escalation chains | ~ Manual | Recreate as OpsPing escalation policies |
| Slack notifications | ✓ Yes | Outbound webhooks to Slack/Teams/any endpoint, scoped per team |
| OnCall mobile app | ✗ No | Replaced by the OpsPing app (iOS + Android) |
| IRM incident management / Sift AI | ✗ No | OpsPing is paging-first, not a Grafana Cloud IRM replacement |
Why Not Just Move to Grafana Cloud IRM?
For some teams IRM is the right answer. The teams who come to us usually say one of these:
- You ran OSS OnCall specifically to avoid a per-seat cloud bundle. IRM folds on-call into the Grafana Cloud account; OpsPing offers a Free core tier for up to 5 responders with Grafana and Alertmanager among its 3 integrations, plus Team at $15/responder/month ($12/responder/month billed annually).
- You don't want your paging coupled to your observability vendor. On-call is the last thing that should share a failure domain (or a billing relationship) with the monitoring stack it pages about. OpsPing runs independently — and private single-tenant deployments are available if you want it on your own infrastructure.
- You were burned by a vendor abandoning a product you depended on. Us too — that's why OpsPing exists. Read the OpsPing pledge: no investors, no exit to force, full data export, and a published shutdown protocol. In writing.
FAQ
Can I keep running the archived OnCall OSS code?
Technically yes, but the former mobile Cloud Connection is gone and the archived project no longer receives bug fixes or security patches. Third-party push and self-managed telephony remain possible when you operate them yourself; budget for that maintenance and risk.
Do I need to keep Grafana at all?
No. OpsPing accepts alerts from anything that sends webhooks — Datadog, CloudWatch, Uptime Kuma, Healthchecks, your own scripts. Grafana/Alertmanager is just the smoothest path because the OpsGenie receiver compatibility is native.
Can I script the migration?
Yes — use the documented OpsPing API or importer. GenieKey header compatibility does not make Opsgenie's Terraform resource schemas drop-in compatible with OpsPing configuration endpoints; translate each resource and verify the supported fields before applying changes.
Coming from Opsgenie instead?
See the Opsgenie migration guide — there's a full importer for users, teams, schedules, rotations, escalations, heartbeats, and integrations.
Need Help?
Stuck on a step? Contact us or email [email protected] with your setup and we'll reply with step-by-step guidance. If you need a call, ask and we'll schedule one.