Last updated: November 16, 2026 — aligned with the production migration wizard; integration setup guides linked.
For a head-to-head of feature parity, API compatibility, and cost, see OpsPing vs Opsgenie.
Step-by-Step Migration
Verify Your Email and Export a Backup
Open the OpsGenie migration wizard. Its steps are Start → Connect → Export → Backup → Destination → Review → Import → Complete. Enter your email and the six-digit verification code, then select the US or EU OpsGenie region and provide an API key with permission to read the configuration you need. You can export a backup before choosing an OpsPing destination.
Custom API URLs must use a public HTTPS hostname. IP literals, private, loopback and link-local destinations are rejected; redirects cannot bypass these checks. Never send your key to support or put it in a URL. The wizard does not save your OpsGenie key in browser storage.
Choose no history, the last 30, 90 or 365 days, or all available. The cutoff is relative to export time; OpsGenie permissions and retention may limit what is available. Configuration and optional history arrive as separate AES-256 encrypted ZIPs. Historical alerts and incidents are archive-only: never imported or paged in OpsPing.
Download, Choose a Destination, and Approve the Plan
Keep the backup-ready email: it contains your status link, separate access ID and archive password. The download page never displays the password; each download link expires after five minutes. Keep the password separate when sharing a link, and use an AES-256 ZIP-compatible tool such as 7-Zip. The whole email contains both access and password, so do not forward it casually. Backups are retained for 30 days by default; download them before the displayed expiry.
Sign in as an administrator of the destination OpsPing tenant, then connect that destination. Review the destination-aware create, existing, manual, skipped and blocked items before approving anything. The dependency-ordered import covers users → teams → services → schedules and overrides → escalations → heartbeats → integrations. Existing matching resources are identified rather than blindly recreated.
Routing, policies, notifications and maintenance are separate review-gated groups: select only those you intend to apply. Integration secrets, when needed, are supplied at approval rather than copied into a report. A plan with blocked resources cannot be imported: resolve the destination conflicts, rebuild the plan, and review its new digest. Approval is tied to the exact plan you reviewed; if it changes, review the new plan and approve again. Exporting or downloading a backup never starts an import. Keep the final import report and resolve any manual items before cutover.
Create or Review Integrations and Repoint the Alert API
After reviewing the imported configuration, open Integrations and copy the new OpsPing integration key (or create the integration you need). Change both the destination URL and credential in your monitoring tools. OpsPing accepts OpsPingKey, X-OpsPing-Key and the compatible GenieKey header syntax; all use the new OpsPing key, not the OpsGenie source key.
Authorization: OpsPingKey YOUR_OPSPING_KEY
# Compatible header syntax, with the same new key:
Authorization: GenieKey YOUR_OPSPING_KEY
Only the alert lifecycle subset below is compatible; do not assume every OpsGenie query parameter, response field or configuration resource is identical. Keep the original destination available until your end-to-end checks pass.
Verify with a Test Alert
Send one firing and one resolution through each repointed monitoring integration. Confirm priority, tags, service/team routing, responder delivery, recurrence behavior, and closure by alias. Use the direct request below only as a 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": "Test alert from migration",
"alias": "migration-test-01",
"priority": "P2"
}'
Cut Over to Push-First Paging
Have the team install the OpsPing mobile app and enable push — iOS Critical Alerts and Android DND-bypass are free and unlimited on every plan. Add a verified voice number for urgent fallback, then email for lower-urgency context. OpsPing deliberately does not add SMS to this ladder: responders already need alert data and a connected device to investigate, while regional restrictions, carrier filtering, consent, and A2P registration make SMS less predictable.
What Transfers — and What Doesn't
| Capability | Migrates? | Notes |
|---|---|---|
| Alerts & lifecycle (ack/close/snooze) | ✓ Supported subset | Verify the endpoints and fields listed below |
| Integrations & webhooks | △ Repoint | Change both destination and credential; verify source-specific payloads |
| Schedules, rotations & overrides | ✓ Yes | Planned and imported through the wizard; inspect unsupported cases in the report |
| Escalation policies | ✓ Yes | Review mapped responders and escalation order before approval |
| Teams & users | ✓ Yes | Destination-aware matching and dependency-ordered import |
| Heartbeats | ✓ Yes | Same ping path and GenieKey header; POST, GET, PUT and PATCH all ping |
| Email integrations (@opsgenie.net) | ✓ Yes | Every OpsPing integration gets an @alerts.opsping.com address — see Email-only tools below |
| Alert policies (noise rules) | △ Review | Approve safe exact mappings in the policies group. Lossy rules stay manual. |
| Opsgenie Edge (on-prem agent) | ✗ No | OpsPing is a hosted service; private single-tenant deployments are available (see FAQ) |
| JSM-only features | ✗ No | Jira Service Management incident tooling is Jira-side; OpsPing is paging-first, not a JSM replacement |
| Opsgenie analytics / reports | ✗ No | OpsPing has its own team-scoped reports |
| Historical alerts & incidents | Archive only | Optional encrypted download; never imported, replayed or paged |
API Compatibility Reference
For the full field-by-field view, see the Opsgenie-compatible alert API guide and the OpsPing API reference.
| Endpoint | OpsGenie Compat | Notes |
|---|---|---|
| POST /v2/alerts | ✓ Supported | Core Opsgenie-shaped alert fields; verify optional fields |
| GET /v2/alerts | △ Verify | query accepts alias: and status: tokens; other text is a substring search, not the Opsgenie query language. Filters and pagination are in the API reference |
| POST /v2/alerts/:id/acknowledge | ✓ Supported | By alert ID, tiny ID, or alias (?identifierType=alias); test actor and activity behavior |
| POST /v2/alerts/:id/close | ✓ Supported | By alert ID, tiny ID, or alias (?identifierType=alias); confirm each source's resolution closes the alert |
| POST /v2/alerts/:id/snooze | ✓ Supported | Alias works; verify duration and escalation interaction |
| GET /v2/alerts/:id | ✓ Supported | By alert ID, tiny ID, or alias (?identifierType=alias: the open alert, otherwise the newest closed one) |
| GET /v2/alerts/count | ✓ Supported | Unfiltered count for your scope; to count by alias or status, use GET /v2/alerts/counts |
| GET /v2/alerts/counts | △ OpsPing endpoint | Status counts for the list scope; query accepts the same alias: and status: tokens |
| Other alert actions | △ Partial | Notes, add/remove tags, assign, responders, escalate, priority changes and details accept alert ID, tiny ID or alias where documented; unacknowledge, unassign, reopen, unsnooze, mark-read and delete need the alert ID or tiny ID. Priority changes do not re-run policies or escalation. No /v2/alerts/requests/:id |
| GET /v2/schedules | △ OpsPing API | Configuration schemas are OpsPing-native |
| GET/POST/PUT/PATCH /v2/heartbeats/:name/ping | ✓ Supported | All four methods ping with the same write authorization; PATCH /:name still updates heartbeat configuration |
| POST /v2/incidents | ✗ No | Incidents are OpsPing-native, not part of the OpsGenie compat layer |
Keeping your existing Opsgenie integrations
Most tools that already post to Opsgenie’s Alert API v2 can keep their existing payloads and GenieKey authentication. Point them at https://api.opsping.com (or your private deployment) and use a new OpsPing API key in the same Authorization: GenieKey <key> header. Step 3 above covers the URL and key change; Alertmanager and Grafana can keep auto-resolve on, because OpsPing closes alerts by alias.
It is a documented subset, not a full drop-in. Only GET /v2/alerts/counts (plural) applies alias or status filters; GET /v2/alerts/count is an unfiltered count. Unacknowledge, unassign, reopen, unsnooze, mark-read and delete are not available by alias — they take the alert ID returned on create, or the numeric tiny ID. Configuration APIs (schedules, teams, policies) use OpsPing-native schemas. See the Opsgenie-compatible alert API for the supported endpoints and the gaps to plan around.
Integration-Specific Instructions
Step-by-step setup guides: Datadog, Grafana, Prometheus Alertmanager, Zabbix, Google Cloud Monitoring, Uptime Kuma, Elastic/Kibana, and CloudWatch SNS.
Datadog
In Datadog, create or edit the webhook/integration destination, set the OpsPing URL, and replace the credential with the OpsPing key. Trigger and recover a monitor to verify both lifecycle directions. Full walkthrough: Datadog → OpsPing.
Prometheus Alertmanager
Update the opsgenie_config block's api_url and api_key, or use an OpsPing inbound webhook integration. Preserve routing/grouping/inhibition rules, then test firing and resolved events. See Alertmanager → OpsPing.
Grafana
For an Opsgenie-compatible contact point, update both URL and key. For Grafana webhook payloads, create a Grafana integration and use its generated inbound URL. Details: Grafana → OpsPing.
Zabbix, Google Cloud Monitoring, Uptime Kuma, Elastic/Kibana, CloudWatch
These often need a webhook (or a custom script) rather than a locked Opsgenie URL. Follow the matching guide: Zabbix, Google Cloud Monitoring, Uptime Kuma, Elastic/Kibana, CloudWatch SNS.
Email-only tools (replaces @opsgenie.net addresses)
Backup jobs, hardware monitors, and older cron tooling often can only send email. Opsgenie gave those an @opsgenie.net address per integration — OpsPing does the same: every integration gets a unique inbound address, <integrationId>.<token>@alerts.opsping.com, shown on the integration's page under Inbound endpoints. Repoint the tool's recipient and you're done:
[P1]–[P5]subject tags set the alert priority (default P3)Re:/Fwd:prefixes are stripped, so reply chains map to the same alert- Message-ID dedupe stops mail-server retries from double-paging
Reproducing Alert Policies
The wizard exports OpsGenie alert and notification policies and converts only the subset whose semantics are exact. These groups are disabled by default: inspect the destination-aware plan, then explicitly approve policies or notifications. The advanced CLI offers the equivalent --include policies and --include notifications options. Rewrite-only actions, unsupported filters and other lossy cases remain explicit manual items rather than being silently approximated:
- Same building blocks: conditions on priority, source, tags, entity, and message content (including regex); actions to suppress, delay, re-prioritize, or add tags
- Ordering matters: preserve the generated order and review team-scoped rules against the mapped OpsPing team
- Verify before cutover: the Policies page dry-run panel shows which policy would fire and what it would do without creating an alert

Full reference: Alert Policies and the policies guide.
Advanced / Support Path: Local CLI
Most migrations should use the wizard. For a support-assisted or private-environment migration, the repository still includes scripts/opsgenie-import.ts. It exports a checksummed local bundle and defaults to dry-run. Supply credentials through a protected local environment, not pasted shell commands, tickets or source control. Applying requires a short-lived destination admin JWT; an integration API key is not sufficient.
# OG_API_KEY is already loaded securely into your environment:
PAGER_API_URL=https://api.opsping.com \
npm run opsgenie-import -- --dry-run --out ./opsgenie-export
# Inspect opsgenie-export/plan.md, then load PAGER_JWT securely:
PAGER_API_URL=https://api.opsping.com \
npm run opsgenie-import -- --bundle ./opsgenie-export --apply
Keep the bundle and resume state private. Unlike the wizard's encrypted ZIP delivery, the CLI writes local files; protect and encrypt those files yourself. Optional mappings require explicit --include choices. --include-alerts and --include-incidents archive history locally, never import it. The CLI does not send wizard status emails or manage hosted artifact retention.
FAQ
Which emails should I expect?
A verification code, export-started notice, backup-ready email and import-complete email. The backup-ready email includes your archive password; the download portal does not. No email contains your OpsGenie API key or OpsPing admin token. If a message is missing, check spam and contact support with the migration ID, not credentials.
Can I leave the wizard and come back?
The wizard remembers the migration ID and session capability in your browser so polling can resume after reload. Treat that browser session as sensitive. The backup-ready email provides a separate access link. Import still requires destination admin authentication and explicit plan approval; a backup download does not grant destination access.
Do my existing OpsGenie Terraform / API scripts work?
Alert API calls that use the v2 alert shape and the GenieKey header work after you change the host and key. Terraform resources for teams, schedules, and other configuration are not all supported — check the compatibility reference before relying on them.
What about SMS?
OpsPing uses push notifications first, voice calls second, and email third. We do not offer SMS for new channel setups. On-call engineers need the alert data and a connected device to investigate; SMS adds regional content restrictions, carrier filtering, consent workflows, and A2P registration without improving that response path.
Can I run OpsPing in my own environment?
Yes — as a private, single-tenant deployment. The backend is a single static Go binary backed by PostgreSQL, so it runs comfortably on your own infrastructure or in a managed private setup we operate for you. Point your integrations at your deployment's URL and the same GenieKey-compatible API applies. Contact us to discuss a private deployment.
Need Help?
Stuck on a step? Contact us or email [email protected] with your setup and we'll reply async with step-by-step guidance. Calls are by appointment.
Coming from Grafana OnCall instead? See the Grafana OnCall migration guide. Wondering why OpsPing won't pull the same rug? Read the OpsPing pledge.