> ## 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 and incident management tool. Rootly-led migrations bring your users, schedules, escalation policies, and routing rules over without a rebuild.

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.

<CardGroup cols={2}>
  <Card title="Migrating from PagerDuty" icon="https://mintcdn.com/rootly/Elm2B9K1HrybvGWA/images/integrations/logos/pagerduty-icon.svg?fit=max&auto=format&n=Elm2B9K1HrybvGWA&q=85&s=bf0acf5e28675a27c857f189c563bdd4" href="/switch/pagerduty-migration" width="512" height="512" data-path="images/integrations/logos/pagerduty-icon.svg">
    Concept-to-concept mapping, what gets imported, timeline, parallel-running patterns, and cutover validation steps.
  </Card>

  <Card title="Migrating from Opsgenie" icon="https://mintcdn.com/rootly/Elm2B9K1HrybvGWA/images/integrations/logos/opsgenie.svg?fit=max&auto=format&n=Elm2B9K1HrybvGWA&q=85&s=8a4b68993fb57a8c2135a83cbe2d8bb1" href="/switch/opsgenie-migration" width="40" height="48" data-path="images/integrations/logos/opsgenie.svg">
    Migrate users, schedules, teams, services, routing rules, and notification settings with a Rootly-led, API-based import.
  </Card>
</CardGroup>

Coming from a different tool, or want help planning your cutover?
[Book a demo](https://rootly.com/demo) or [contact support](/contacting-support) and our
team will walk you through it.