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:
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.
Migrate with the migration tool
Use the open-source Grafana IRM migration tools to migrate from PagerDuty, Splunk OnCall (VictorOps), Opsgenie, or Grafana OnCall OSS. 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.
Migrate manually
If you’re migrating from a vendor not supported by the migration tool, or prefer a different approach, you can migrate manually using Terraform or the IRM UI.
For details, refer to Migrate to Grafana IRM manually.
