# Inventory change collision history before ITSM merge

Canonical: https://refer.sourcex.si/guides/workflow-change-collision-recovery
Last updated: 2026-11-04

Before an ITSM consolidation, inventory the records that explain how change collisions were caught and undone: change requests with their approvals and planned windows, conflict detection results, CMDB dependency records and their history, monitoring alerts and change events, rollback approvals and post-incident reviews. Note years of coverage, the owner of each source and the date old instances lose read access. Keep it at metadata level, then introduce the decision-maker through the service delivery director.

A change collision is two or more changes that each passed review and worked alone, but broke something together. Recovering from one leaves an unusually complete record: the calendar that let both changes run, the dependency the review missed, the alert, the rollback decision and the review afterwards. Consolidation projects tend to carry forward open work and current configuration, and leave exactly that history in the old instance. This guide shows what to inventory and why.

## Why does an ITSM consolidation put change collision history at risk?

Because the records that explain a past collision are closed, historical or stored outside the main tables, and migration plans are scoped around what is open and current.

Vendor documentation shows how many pieces a collision touches. In ServiceNow, conflict detection needs a configuration item and planned start and end dates on the change, and detected conflicts list the conflicting change, the affected CI and the issue type, such as CI already scheduled, not in maintenance window or blackout. On the monitoring side, PagerDuty change events do not create alerts or incidents; an incident's Recent Changes section shows up to three change correlations from the past 24 hours with a reason, and related-service correlation depends on configured service dependencies. PagerDuty's ServiceNow integration can create those change events when a change request is opened.

Put together, the history of one collision spans closed change requests, stored conflict results, the dependency record as it was on the night (not as it is now), monitoring correlations and a review. Each is easy to leave out of scope on its own.

## What should be inventoried before ITSM consolidation affects change collision recovery history?

Inventory what the consolidation plan carries forward and what it leaves behind.

| Record class | Ask the project team | What to note |
|---|---|---|
| Closed change requests | Are closed changes, approvals and CAB notes in scope for migration? | Years held; whether approvals move with them |
| Conflict results | Are conflict lists stored, and will they move? | Present or not; not their content |
| CMDB relationships | Will relationship history move, or only current relationships? | Whether "when was this dependency added" survives |
| Incidents and reviews | Will post-incident reviews and attachments move? | Where reviews live if not in the ITSM tool |
| Monitoring and on-call | How long are alerts and change events kept in those tools? | Retention set by the company's plan and settings |
| Real deadline | When does read access to the old instance end? | Date from the decommission plan or vendor contract |

## An Illustrative migration scope

Illustrative, for a fictional managed services company merging two instances into one. The migration scope, shown as the line in the graphic, covers open changes and current CIs. Read access to the old instance ends on March 31.

| Layer in the old instance | In migration scope? | What it explains about a past collision |
|---|---|---|
| Open changes | Yes | Nothing about the past |
| Current CIs | Yes | Today's configuration, not the night's |
| Closed changes and approvals | No | That both changes were approved, and by whom |
| Conflict results | No | Whether the tool flagged anything |
| Relationship history | No | Whether the missing dependency existed then |
| Post-incident reviews | No | What the company concluded and changed |

The top two rows are what the new instance needs to run. The bottom four are the collision history. The decision about them belongs to the company; the partner's job is to make sure the service delivery director has seen this table before March 31, not after.

## Stay inside your role

Do not recommend retaining data the company has no authority or reason to keep, and do not export records, take screenshots or pull samples for a licensing conversation. Project access to the instance does not give you, or the client's IT team, authority to license its records. If the company already plans to archive its old instance, that is its own decision; the inventory just records what exists. For ticket-level history more generally, see [ITSM ticket history](/data-types/itsm-ticket-history) and [ServiceNow incident data](/systems/servicenow-incident-data-for-ai-training).

## Does the company qualify?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. The service delivery director usually knows coverage; the company's counsel decides what client contracts allow for records about client systems; the CEO, CTO or owner typically authorizes a licensing discussion. Whether buyers want collision history and what the rights review concludes about client-related records stay unknown until SourceX reviews it. The [software implementation partners page](/for/software-implementation-partners) and the [industries hub](/industries) describe the wider fit.

## Go deeper on change collision recovery

- [Change collision recovery referral brief template](/resources/change-collision-recovery-referral-brief-template) gives a fill-in introduction note.
- [Change collision recovery exception examples](/guides/change-collision-recovery-exception-examples) works through collisions and the rollbacks that resolved them.
- [Change collision recovery records across systems](/guides/change-collision-recovery-records-across-systems) is a field map of how ITSM, CMDB and monitoring records join.
- [Who can license change collision recovery records](/questions/who-can-license-change-collision-recovery-records) answers which decision-maker to introduce.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the consolidation plan leaves years of closed changes, conflict results and reviews below the scope line, [register as a partner](/register), check the client against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the executive who can authorize the discussion.

## Sources

- https://refer.sourcex.si/terms
- https://docs.servicenow.com/bundle/paris-it-service-management/page/product/change-management/task/t_RunManualConflictDetection.html
- https://support.pagerduty.com/docs/change-events
- https://support.pagerduty.com/main/docs/servicenow-change-requests-integration-guide
