PagerDuty Migration
The following attributes will be pulled from PagerDuty to Rootly during the migration.
- Match users between PagerDuty and Rootly based on their email address
- if users do not match, new users will be created in Rootly
- Pull-in contact methods
- email address
- phone number
- SMS number
- Match notification rules between PagerDuty and Rootly
- if notification rules do not match, they will not be pulled in
- Contact methods and notification rules will be mapped accordingly
- Pull-on schedules
- Schedules
- Shifts
- Rotations
- Daily
- Weekly
- Custom
- Match escalation policies with schedules from PagerDuty into Rootly
Step 1: As you start your onboarding experience, we will ask if you want to do a PagerDuty migration. If you are interested in doing so, your onboarding representative will ask you the following questions:
- What attributes would you like to migrate from PagerDuty to Rootly?
- When would you like to have this migration performed?
Step 2: To access your PagerDuty API Key required for a migration, we have provided you with instructions on how to do so below:
- In PagerDuty, navigate to Under Integrations > Developer Tools > API Access Keys
- Click 'API Access Keys'
- Name the API and click ‘Create Key,' then check the box for “Read-only API Key”
- Copy the generated API Key
Step 3: Once the Rootly team has your API Key, desired PagerDuty attributes, and the date on which you would like the migration to be performed, we will schedule your migration and provide you confirmation of the migration once it is completed.
If you have any additional questions or concerns, please get in touch with your Rootly onboarding representative or email [email protected].
