---
title: "Migrate to Grafana IRM | Grafana Cloud documentation"
description: "Learn about migration options to Grafana IRM from PagerDuty, Splunk OnCall, Opsgenie, or Grafana OnCall OSS. Choose from automated tools, Terraform, API-based, or manual approaches."
---

# Migrate to Grafana IRM

Grafana IRM unifies on-call management and incident response with observability-native workflows. This guide helps you choose the right path to migrate from your current on-call management tool to IRM.

## Why migrate to Grafana IRM

- **Observability-native workflows:** Resolve incidents faster with observability signals integrated into alerting, incident response, and collaboration, all built into your Grafana Cloud stack.
- **Tool consolidation:** Reduce the number of tools you manage by integrating incident response into the Grafana ecosystem.
- **Cost savings:** Move away from inflexible licensing. IRM uses active user pricing so you pay for what you use.

## Migration paths

IRM supports migration from PagerDuty, Splunk OnCall (VictorOps), Opsgenie, and Grafana OnCall OSS. Choose the path that best fits your team and source platform:

Expand table

| Source platform           | Recommended path                                                                                 |
|---------------------------|--------------------------------------------------------------------------------------------------|
| PagerDuty                 | [Migration tool](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/migrator-tools)         |
| Splunk OnCall (VictorOps) | [Migration tool](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/migrator-tools)         |
| Opsgenie                  | [Migration tool](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/migrator-tools)         |
| Grafana OnCall OSS        | [OnCall OSS migration guide](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/oncall-oss) |
| Other                     | [Manual migration](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/manual-migration)     |

### Professional services

If you’re migrating at scale or under tight deadlines, Grafana Professional Services can handle the migration end-to-end, including auditing your current setup, writing Terraform scripts, and providing post-migration support.

To explore this option, contact your Grafana account manager or [Grafana Professional Services](/professional-services/).

### Migrate from PagerDuty, Splunk OnCall, OnCall OSS or Opsgenie using the migration tool

Use the open-source [Grafana IRM migration tools](https://github.com/grafana/irm-tooling) to migrate from PagerDuty, Splunk OnCall (VictorOps), OnCall OSS or Opsgenie. The migration tools are Docker-based and support migrating schedules, escalation policies, integrations, notification rules, and more.

For details, refer to [Migrate to Grafana IRM with the migration tool](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/migrator-tools).

### Migrate manually from Grafana OnCall OSS

Grafana OnCall OSS users can migrate to Grafana Cloud IRM using Terraform or the OnCall API.

For details, refer to [Migrate from Grafana OnCall OSS to Grafana Cloud IRM](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/oncall-oss).

### Migrate manually

If you’re migrating from a vendor not supported by the options above, or prefer a different approach, you can migrate manually using Terraform or the IRM UI.

For details, refer to [Migrate to Grafana IRM manually](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/manual-migration).

## Next steps

- [Migrate to Grafana IRM with the migration tool](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/migrator-tools)
- [Migrate from Grafana OnCall OSS](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/oncall-oss)
- [Migrate to Grafana IRM manually](/docs/grafana-cloud/alerting-and-irm/irm/set-up/migrate/manual-migration)
- [Set up Grafana IRM](/docs/grafana-cloud/alerting-and-irm/irm/set-up)