> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Switching to Rootly

> Move to Rootly from your current on-call tool. Rootly-led migrations bring your users, schedules, and escalation policies over without a rebuild.

Rootly migrations are led by the Rootly 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.

> [card] [Migrating from PagerDuty](https://docs.rootly.com/switch/pagerduty-migration.md)
>
> Concept-to-concept mapping, what gets imported, timeline, parallel-running patterns, and cutover validation steps.

> [card] [Migrating from Opsgenie](https://docs.rootly.com/switch/opsgenie-migration.md)
>
> 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](https://rootly.com/demo) or [contact support](https://docs.rootly.com/contacting-support.md) and the Rootly
team will walk you through it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.