Importing historical incidents from Rootly

Bring your incident history from Rootly into incident.io, so your reporting and insights cover more than just the incidents you declare from now on.

You can automatically import your incident history from Rootly. Migrating your on-call setup is normally simpler than you’d think, and we’re here to support you throughout.

Contact support or talk to your account manager to get access to the automatic importer.

What comes across

We import your resolved and closed incidents, leaving behind sub-incidents, tests, examples, and maintenance windows. Each incident arrives with:

• Name, summary, and severity, matched to your incident.io severities by name
• Its Rootly incident number, so existing links and references still make sense
• Timestamps for when the incident was reported, accepted, resolved, and closed. Started, detected, and mitigated come across too, if you have timestamps named Started at, Detected at, and Mitigated at
• The reporter, plus role assignments, with Rootly’s Commander mapped to your lead role
• Services, mapped to a Catalog custom field named Service or Services
• A link to the Rootly retrospective, where the incident has one

Slack channels and custom field values stay in Rootly.

See importing historical incidents for the general approach and the API.

Moving your on-call setup

You’ll build your schedules and escalation paths fresh in incident.io. A few things make that quick:

• Duplicate a schedule once you have the first rotation shaped the way you want, or define rotations and paths as code with the Terraform provider.
• Point your monitoring tools straight at incident.io alert sources. A custom HTTP source takes any webhook you can shape with a transform expression, and the Datadog migration tool repoints Datadog monitors in bulk.
• Load your services and teams into Catalog.
• Use the on-call readiness report to see who’s reachable before you hand them the pager.