Change collision recovery history: what to inventory before an ITSM consolidation

Short answer

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.

Visual briefFull-size diagram
Two stacked columns: the old ITSM instance holds open changes, current CIs, closed changes, conflict results, relationship history and post-incident reviews; the new instance receives only open changes and current CIs, and the other four layers stay behind until read access ends on March 31.
Illustrative migration scope for a fictional ITSM consolidation. The layers that explain past collisions sit below the scope line.

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 classAsk the project teamWhat to note
Closed change requestsAre closed changes, approvals and CAB notes in scope for migration?Years held; whether approvals move with them
Conflict resultsAre conflict lists stored, and will they move?Present or not; not their content
CMDB relationshipsWill relationship history move, or only current relationships?Whether "when was this dependency added" survives
Incidents and reviewsWill post-incident reviews and attachments move?Where reviews live if not in the ITSM tool
Monitoring and on-callHow long are alerts and change events kept in those tools?Retention set by the company's plan and settings
Real deadlineWhen 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 instanceIn migration scope?What it explains about a past collision
Open changesYesNothing about the past
Current CIsYesToday's configuration, not the night's
Closed changes and approvalsNoThat both changes were approved, and by whom
Conflict resultsNoWhether the tool flagged anything
Relationship historyNoWhether the missing dependency existed then
Post-incident reviewsNoWhat 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 and ServiceNow incident data.

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 and the industries hub describe the wider fit.

Go deeper on change collision recovery

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, check the client against who qualifies, and read the program terms before you introduce the executive who can authorize the discussion.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a change collision the same as a failed change?

No. A failed change is one change that did not work. A collision is two or more changes that each passed review and worked alone, but broke something together. The records are more valuable because they show why the review process missed it.

Does the consolidation project need to keep every old change record for this?

No. What the company keeps is its own decision, made with the required authority. The inventory only describes which records exist and whether the migration plan carries them, so a decision-maker can weigh the history before it is changed.

Can an ITSM implementation partner introduce its own client?

Yes, as the introducer, provided you sign the Channel Partner Agreement first and stay at metadata level. Your project access to the instance does not give you, or the client's IT team, authority to license its records.

Sources

  1. refer.sourcex.si/terms
  2. docs.servicenow.com/bundle/paris-it-service-management/page/prod…
  3. support.pagerduty.com/docs/change-events
  4. support.pagerduty.com/main/docs/servicenow-change-requests-integra…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment