Skip to main content
Rootly migrations are led by our team and powered by API-based imports, so you keep your schedules, escalation policies, users, and routing rules — no rebuilding from scratch. Most teams run Rootly in parallel with their existing tool during the transition and cut over once everything is validated.

Migrating from PagerDuty

Concept-to-concept mapping, what gets imported, timeline, parallel-running patterns, and cutover validation steps.

Migrating from Opsgenie

Migrate users, schedules, teams, services, routing rules, and notification settings with a Rootly-led, API-based import.
Coming from a different tool, or want help planning your cutover? Book a demo or contact support and our team will walk you through it.