PagerDuty Migration Attributes
The following attributes will be pulled from PagerDuty to Rootly during the migration.User
- 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
Schedules
- Pull in schedules
- Schedules
- Shifts
- Rotations
- Daily
- Weekly
- Custom
Escalation Policies
- Match escalation policies with schedules from PagerDuty into Rootly
Migration Instructions
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?
- 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