Insights & updates from our experts

Switching tools can feel like a big task, so we built a migration tool to do the heavy lifting for you. It allows you to copy your existing teams, schedules, and policies from PagerDuty directly into Xurrent IMR.
The best part is that you are in total control. You don't have to move everything at once. If you are just testing Xurrent IMR out, you can choose to import only a specific team or a single schedule to see how it works.
TL;DR
Here's quick demo to see how it works:
Here is how to get it done.
1. Connect your PagerDuty account
First you need to give Xurrent IMR permission to read your current setup. You do this by creating a simple key in PagerDuty.
- Go to your PagerDuty Dashboard>Integrations>API Access Key and generate a Read-Only API Key.
- Paste that key into the migration box in Xurrent IMR.
- Click Start Migration.

2. Start the migration in Xurrent IMR
- Log in to your Xurrent IMR account.
- Go to Profile → Account → Account Migration.
- Paste the Read-Only API key from PagerDuty.
- Click Start Migration.

3. Select your users
- Select the users you want to migrate.
- Click Continue.

4. Select teams to migrate
- Choose the teams you want to migrate.
- Click Continue.

5. Import your schedules
You likely spent a lot of time building your on-call rotations. You can bring those over exactly as they are. Whether you have complex rotations or simple daily shifts, just select the ones you want to keep.
- Choose your schedules.
- Click Continue.

6. Move your escalation policies
Finally, select your escalation policies. These link your users and schedules together so alerts go to the right people.
- Select the policies you want to migrate.

7: Select services to migrate
- Select the services you want to migrate.
- Click Continue.

8. Review the logs
Once you start the process, you will get a Migration ID. When the migration finishes, you will see a detailed log of everything that was moved.
This log is really helpful if you run into any issues. You can simply download these logs and send them to our support team. We can look at exactly what happened and help you fix anything that didn't go as planned.

That’s it. Refresh your page and your data will be ready for you.
We are super excited to have you on board! If you get stuck at any point or just want some help setting things up, please reach out to us. You can raise a support ticket here, and our team will jump in to help you get settled.
Not sure how to raise a ticket? You can check out our guide on how to do that right here.
Welcome to Xurrent IMR!

Your alerts know they're related. They still can't tell you why.
Everyone knows the boy who cried wolf. He sounded the alarm for fun, the village came running, and after a few false alarms they stopped coming. Then the wolf showed up for real, and the story ends the way you remember.Every on-call engineer is living the grown-up version. The alerts cry wolf all day, so you learn to tune them out. Then one night a page you'd have ignored is the outage, and by the time you look, it's already bad.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.









.webp)



.webp)

.webp)
.webp)















