How to migrate from PagerDuty
EvoHub can import your PagerDuty schedules, escalation policies and service integrations with a read-only API key, and accepts PagerDuty Events API v2 events as they are. This guide walks through the move — people, schedules, escalation and alert sources — with a parallel run before you cut over.
What moves and what doesn't
| What | Details |
|---|---|
| Imported | Schedules with their layers, rotations and — where they fit — layer restrictions, plus overrides in the next 90 days; escalation policies with their rules, delays and repeats; and the inbound integrations of every service that is not disabled. |
| Matched, not created | PagerDuty users are matched to EvoHub members by email address. PagerDuty teams are not created: you choose which EvoHub team each one's schedules, policies and integrations go into. |
| Not imported | Services as objects, team members, event orchestrations and service event rules, response plays, business services, status pages, maintenance windows, notification rules and change events. |
| History | Incidents, alerts and their history are not imported — the importer reads configuration only. |
| Your PagerDuty account | Nothing in PagerDuty is changed. The importer only reads, with a REST API key that is used for that request and is not stored. |
PagerDuty concepts, mapped to EvoHub
| PagerDuty | EvoHub | Notes |
|---|---|---|
| Users | Organization members | Matched by email. Invite anyone the preview lists as missing — EvoHub has no per-seat fee. |
| Teams | Teams | Map each PagerDuty team to one of your EvoHub teams in the preview; team membership is not imported. |
| Schedules & layers | Schedules & layers | Same layer order and participants, in the schedule's time zone. Layers that have already ended are skipped. |
| Rotation turn length | Daily, weekly or every N days | EvoHub hands over in whole days; shorter turns are rounded and flagged — give each shift its own layer with a shift window. |
| Layer restrictions | Shift windows | One daily window, or the same window on chosen weekdays, carries over; anything else is flagged in the preview. |
| Schedule overrides | Overrides & takeover | Overrides in the next 90 days are imported with their schedule. Responders can also take over an alert from the mobile app. |
| Escalation policies | Escalation policies | Each rule becomes a step that notifies a person or a schedule; a rule with several targets becomes steps a minute apart. Repeats carry over. |
| Services | No equivalent — integrations | EvoHub On-Call has no services: each integration routes alerts to its own escalation policy. A service's integrations are imported under the service's name, with its escalation policy when you import that too. |
| Events API v2 integration | API integration (Events API v2 compatible) | Same JSON: routing_key, event_action (trigger, acknowledge, resolve), dedup_key. Only the URL and the key change. |
| Tool integrations (Datadog, Prometheus, CloudWatch, email…) | EvoHub's integration for that tool | Re-point the tool at the new integration's URL or inbound email address in its own settings. |
| Notification rules | Per-step notification method | Not imported. Each escalation step pages by voice call, mobile push or email; SMS is coming soon. |
| Mobile app | iOS and Android apps | Acknowledge, resolve and take over incidents. |
| Status pages | Status pages | Not imported. EvoHub status pages are in the same platform, on your own domain. |
Step-by-step migration
Create your EvoHub organization and invite the team
Sign up, create teams that mirror your PagerDuty teams, and invite responders with the same email address they use in PagerDuty — the importer matches people by email. Seats are free, so there is no reason to leave anyone out. Ask responders to install the iOS or Android app and allow notifications.
Create a read-only PagerDuty API key
In PagerDuty, go to Integrations → API Access Keys → Create New API Key and choose a read-only key. Note whether your account is in the US or EU service region. EvoHub uses the key for the import request only and does not store it.
Preview the import
In EvoHub, open On-Call → Import from PagerDuty (it needs permission to change On-Call settings), paste the key and pick the region. The preview lists every schedule, escalation policy and integration it would create, with a note on anything that does not carry over exactly, and the people who are not in EvoHub yet — invite them from there. Map each PagerDuty team to an EvoHub team. Nothing is created until you confirm.
Import, then fill the gaps
Untick anything you do not want and import. Then fix whatever the preview flagged — shifts shorter than a day, restrictions that did not fit, escalation targets other than people and schedules. Running the import again never makes duplicates; it only adds people who have joined since.
Re-point alert sources — and run both tools in parallel
Each imported integration has its own URL and key in EvoHub. Senders that use the Events API v2 only need the new URL (it ends in /ingest/api) and the new key as routing_key. Tools with their own EvoHub integration are re-pointed in their settings. Where a source allows several destinations, keep PagerDuty and add EvoHub, so both receive the same alerts for a week or two.
Test paging end to end
Send a test trigger through each integration and confirm the right person is paged and can acknowledge from the app. For Events API v2 senders, send a resolve with the same dedup_key and check the alert closes. Compare what EvoHub paged against PagerDuty during the parallel run.
Cut over
Once the parallel run is clean, remove the PagerDuty destinations from your alert sources and leave a quiet week with EvoHub as the only pager before you wind PagerDuty down.
Setup steps for each alert source: EvoHub integrations. Product comparison: EvoHub vs PagerDuty. More on EvoHub On-Call and its pricing.
PagerDuty migration FAQ
Can I import my PagerDuty configuration automatically?
Yes. On-Call → Import from PagerDuty reads your users, teams, schedules, escalation policies and services with a read-only REST API key, shows a preview, and creates schedules, escalation policies and integrations only when you confirm. Running it again never makes duplicates.
Does EvoHub accept PagerDuty Events API v2 events?
Yes. The EvoHub API integration takes the Events API v2 body: routing_key (or the key in the URL, or a bearer token), event_action trigger, acknowledge or resolve, dedup_key and payload. It answers like PagerDuty does, with status, message and dedup_key, so a sender only changes the URL and the key. Events API v1 and change events are not accepted.
What happens to my PagerDuty services?
EvoHub On-Call has no services. Alerts arrive through an integration, and each integration has its own escalation policy. The importer creates an integration for each integration of a PagerDuty service that is not disabled, named after the service and set to that service's escalation policy when you import that policy too.
Is my incident history imported?
No. The importer reads configuration — users, teams, schedules, escalation policies and services — not incidents or alerts. Keep your PagerDuty records for as long as you need them.
Is my PagerDuty API key stored?
No. The key is used for that one import request and is not stored, logged or sent back. A read-only key is enough.
How much does EvoHub cost compared to PagerDuty?
EvoHub has no per-user fee. You pay per usage — an ingested alert is 1 EvoHub token (about $0.015), a voice call 10 tokens (about $0.15), an email 0.7 tokens, push and webhook notifications are free — and every account gets 200 free tokens each month.
Does EvoHub support SMS alerts?
Not yet. EvoHub pages by voice call, mobile push and email today; SMS is coming soon.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.