Migrating from PagerDuty to Nova? This guide walks you through importing your services, on-call schedules, escalation policies, and incident history so you can make the switch without losing any configuration.
In Nova, go to Settings > Migrations > PagerDuty. Enter your PagerDuty API key and click Connect. Nova will scan your PagerDuty account and show a preview of what will be imported.
Select which PagerDuty services to import. Nova maps each service to a Nova service, preserving the name, description, and integration keys.
Nova imports your rotation schedules, including all participants, rotation intervals, handoff times, and overrides. Review the imported schedules to verify they match your PagerDuty configuration.
Escalation rules are mapped to Nova's escalation engine. Multi-level escalations, timeouts, and repeat policies are all preserved.
During migration, configure Nova to forward incidents to PagerDuty as a backup. This lets you validate that Nova is routing correctly before cutting over completely.
Nova can import your PagerDuty incident history (up to 12 months) so your MTTR and incident frequency analytics start with historical data, not from zero.
Point your monitoring tools (Datadog, CloudWatch, etc.) to Nova's integration endpoints instead of PagerDuty. Nova provides compatible endpoints, so in most cases you only need to change the URL and API key.
Send invitations to your team members. Nova matches PagerDuty users by email, so their on-call assignments carry over automatically.
Once you have verified everything works in Nova, disable the PagerDuty integration endpoints and cancel your PagerDuty subscription. Nova provides everything PagerDuty does, plus AI-powered triage and automated remediation.
Switch from PagerDuty to Nova and save up to 60% on your incident management costs.
Start Free Trial