# ITSM consolidation data introductions | SourceX

Canonical: https://refer.sourcex.si/guides/moment-itsm-consolidation-servicenow-consultants
Last updated: 2026-11-05

Often, but not reliably. In ServiceNow, an incident is tied to the change that caused it through a field on the incident record, and the rollback reasoning sits in the change's backout plan, work notes and review. An ITSM consolidation can keep the tickets and still drop those links. ServiceNow consultants can ask the company owner this metadata-level question before cutover and, if the company appears eligible and wants to proceed, introduce its decision-maker to SourceX.

## Are rollback decisions linked to the changes that caused them?

Ask it in exactly those words, then listen for which records the owner names. A "yes" usually means three things are joined: the change request, the incident that followed it, and a recorded decision to back the change out or fix forward. A "partly" is common and still worth noting.

Two documented fields carry most of the chain. On a standard ServiceNow incident form, the Caused by Change field holds the number of the change request that resulted in the incident. On the change request, the Backout plan field holds the information needed to restore the system to its original state if an implementation fails. Between them sit work notes, CAB discussion and, at the end, a post-implementation review.

A complete chain is valuable because it records a judgment under pressure: something broke after a planned change, someone weighed rollback against a forward fix, and the outcome is known. That is what separates it from a plain ticket export, which the [ITSM ticket history page](/data-types/itsm-ticket-history) and [ServiceNow incident data](/systems/servicenow-incident-data-for-ai-training) cover in general terms.

### The record chain to listen for

Illustrative. A 400-person logistics software company merging two ServiceNow instances into one.

| Link | Where it usually lives | What the owner can tell you without opening it | What breaks it in a consolidation |
|---|---|---|---|
| Change request | Change request record, including its backout plan | How many changes per year, and since when | Renumbering without a cross-reference |
| Incident caused by the change | Caused by Change reference on the incident | Whether teams fill it in consistently | Incident references not remapped to new change numbers |
| Rollback or fix-forward decision | Work notes, the backout plan, CAB minutes | Whether decisions are written or only discussed on calls | Work notes or journal history left in the old instance |
| Post-implementation review | Review fields, problem records, a separate wiki | Which system holds reviews | Reviews stored outside ServiceNow and not in scope |

## Why are change failures and recoveries easy to overlook?

Because of where the link lives. The Caused by Change reference is stored on the incident, not on the change. Migration teams tend to map change requests as a unit and incidents as a unit. If the incident-side reference is not remapped to the new change numbers, both record sets arrive intact and the cause-and-recovery story between them does not. Every ticket count reconciles, and nobody notices the join is gone.

Older years face a second risk. ServiceNow's data archiving moves older records out of live tables into archive tables to free system resources, so a migration scope written around live tables can leave the older years behind entirely. Add a retired instance that stays read-only for a while and is then decommissioned, and the years with the richest history can disappear without a decision ever being made about them.

The third reason is human. Consolidation projects are judged on a single service catalog, unified workflows and license savings. The change manager who knows which incidents were rollbacks is rarely asked, and the reasoning in CAB minutes or a wiki is outside the platform team's scope. The [ServiceNow archiving and retention guide](/guides/servicenow-data-archiving-retention-policy) explains archive and destroy rules in more depth.

## Four metadata questions after the opener

Stay at metadata level: what exists, how much, how long, which system and who owns it.

1. **How far back?** Roughly how many years of change requests exist, in how many instances or tools, and how much is already in archive tables?
2. **Is the link filled in?** Do incidents reference the change that caused them, and has that been consistent across teams and years?
3. **Where is the reasoning?** Is rollback reasoning written in backout plans, work notes, CAB minutes or post-implementation reviews, and are any of those outside ServiceNow?
4. **Who decides?** Who decides what happens to the old instance and its archive tables after cutover, and who owns the ticket history if a managed service provider ran the desk?

Write down the answers as counts, years and system names only. You never need exports, screenshots or logins; the owner or change manager can answer from memory or from a report they already run. If the answer to question 4 depends on a service contract, say so in your notes, because SourceX reviews rights before any agreement.

## How do you disclose the reward and get the owner's permission?

Ask before you introduce SourceX, and disclose at the same moment. Say it plainly: "I can introduce you to SourceX, which licenses approved business data for AI training and evaluation. If a qualifying license completes and is paid, SourceX pays me a referral reward from its own funds, not from your payout. Would that be useful?"

If the answer is no, stop there. A consultant's first duty is to the consolidation project, and a declined introduction should not change anything about it. If the answer is yes, ask who the authorized contact should be. Whether your profession requires a written disclosure is covered in [do you have to disclose a referral fee](/questions/do-i-have-to-disclose-a-referral-fee).

Describe the reward accurately. The default on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. Illustrative only: an $800,000 payout to the company would mean a USD 120,000 reward, because 15% exceeds USD 50,000 plus 5% (USD 90,000) at that size; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months of the first Closing pay 15%. 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. The [rewards page](/rewards) confirms that SourceX funds the reward separately.

## Does the company qualify, and what stays unknown?

A company that has run two ServiceNow instances is often a sizeable one, but that is not evidence it qualifies. It still needs to clear SourceX's baseline.

- 50+ full-time employees at peak, contractors excluded.
- A documented operating history and rights to license the records. Where a managed service provider ran the desk, the contract decides who controls the ticket history.
- An authorized contact who can open a licensing discussion.
- 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.

| Known at introduction | Unknown until SourceX reviews it |
|---|---|
| Record types, years and instances, as the owner describes them | Whether there is current demand for this record type |
| Who owns the platform decision | The rights review result, including provider and customer contracts |
| The cutover and decommission dates in the plan | What, if anything, the company is offered |
| That the reward was disclosed | Whether any referral reward becomes payable |

Partners never ask for or handle raw records. SourceX handles rights review, de-identification and delivery with the company directly. Sign the Channel Partner Agreement before you submit an introduction. Attribution goes to the first valid introduction within the 90-day window and is credited when the company submits a verified application; one partner is credited per company. For other consolidation moments, see the [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation), the [ITSM agents guide](/guides/ai-agents-itsm), the [network opportunity finder](/tools/network-opportunity-finder) and the [partner hub](/for).

## Go deeper on ITSM consolidation records

- [ITSM consolidation introduction email](/resources/itsm-consolidation-introduction-email): a ready-to-adapt email for introducing the owner's chosen contact to SourceX after they opt in.
- [ITSM consolidation meeting agenda](/resources/itsm-consolidation-meeting-agenda): a timed agenda for the owner meeting where the rollback question and the disclosure come up.
- [ITSM consolidation archive context checklist](/resources/itsm-consolidation-archive-context-checklist): a checklist of cutover, migration scope and archive-table decisions to confirm before the old instance retires.

## 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 owner says the change-to-incident chain survives and wants to talk before cutover, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://www.servicenow.com/docs/r/it-service-management/incident-management/create-an-incident.html
- https://www.servicenow.com/docs/r/BgFKZnPHldZ62gGtzQ71Mw/cZZFYNfdM7ypDoSb~J9Mag
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1665539
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
