# ITSM consolidation archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/itsm-consolidation-archive-context-checklist
Last updated: 2026-11-05

Only if incidents name the change that caused them and the backout decision is written down, and only if the migration keeps both. Confirm a short list at three stages: before the consolidation is announced, before cutover to the target instance, and before the old instance is switched off. Each item asks whether a change, the outage it triggered and the decision to reverse or repair will still point to each other afterward, who owns that answer, and what breaks if nobody checks. Stage dates come from the company's plan.

This is part of the [consolidation guide for platform consultants](/guides/moment-itsm-consolidation-servicenow-consultants). The [25-minute meeting agenda](/resources/itsm-consolidation-meeting-agenda) is where the questions are first asked; this checklist keeps the answers current through to retirement.

## Fixing the countdown dates

| Stage | Typical source of the date | If the date is missing |
|---|---|---|
| Announcement | The consolidation business case, an acquisition integration plan or a license renewal | Start early and treat stage one as a calm inventory |
| Cutover | The migration runbook for the target instance | Record who owns go-live |
| Retirement | The old instance's subscription end, a decommission request or an integration milestone | Leave it open; the item becomes "who decides retirement" |

Use three states for every item: **confirmed** by someone with authority, **unknown** with a named person to find out, and **at risk** when the current plan drops it. Write down configuration, counts and owners only. Never copy ticket numbers, work note text or names into your sheet.

Revisit the sheet at each stage rather than once. An item confirmed at announcement can slip to at risk when the runbook is rewritten, and an unknown can resolve itself when the platform team publishes its mapping. Date each status change and keep the earlier value, so the owner can see how the picture moved. Share the sheet only with the people who supplied answers.

## Stage one: before the consolidation is announced

The scope is still open, and nobody has a plan to defend.

| Item to confirm | Owner | Cost of skipping it |
|---|---|---|
| How many instances or tools hold change and incident history, and how many years each | Platform owner | The oldest instance is forgotten when scope is written |
| Whether incidents name the change that triggered them, and how consistently across teams | Incident manager | Nobody knows the chain is thin until it is gone |
| Whether normal changes carry a written restore plan | Change manager | The intended recovery cannot be shown for older changes |
| Who owns ticket history if an MSP or the acquired company ran the desk | CIO or owner | Rights questions appear only after an introduction |

On the standard incident form, a Caused by Change field records which change request led to the incident. Knowing whether teams fill it in is the most useful single fact at this stage.

## Stage two: before cutover to the target instance

Mapping is being finalized, and anything missing from it is lost by default.

| Item to confirm | Owner | Cost of skipping it |
|---|---|---|
| Whether changes are renumbered, and whether a cross-reference to old numbers is kept | Platform owner | Incident references point to change numbers that no longer exist |
| Whether each incident's pointer to its triggering change is updated to the new numbering | Migration lead | Both sets land intact while the pointer between them breaks |
| Whether work notes and journal history migrate or stay behind | Platform owner | The reasoning behind each reversal stays in the old instance |
| Where post-change reviews and change board minutes live, inside or outside the platform | Change manager | Reviews kept in a wiki fall outside every migration scope |

The Backout plan field holds what is needed to restore a system if an implementation fails. It is valuable only alongside the record of whether it was used, which is why journal history matters as much as the plan.

## Stage three: before the old instance is switched off

This is the last point at which keeping something is still a choice.

| Item to confirm | Owner | Cost of skipping it |
|---|---|---|
| What happens to archive tables in the old instance | Platform owner | Archived years disappear with the instance |
| Whether the read-only period has a documented end and a reviewer | CIO | Retirement happens at license renewal without review |
| Who signs off the final retention decision | CIO or COO | No one is accountable for what was dropped |
| Whether the owner wants to hear about licensing before switch-off | Owner | The question is never asked while the history exists |

ServiceNow data archiving moves older records out of live tables into archive tables. A retirement plan that talks only about live tables may say nothing about the archived years, which may hold the longest run of change history. The [ServiceNow archiving and retention guide](/guides/servicenow-data-archiving-retention-policy) covers archive and destroy rules in detail.

## From a completed checklist to an owner decision

A finished checklist describes the archive; it does not establish fit. Check the basics before raising SourceX: 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.

| What the checklist tells you | What only SourceX review can tell you |
|---|---|
| Instances, years and whether the chain is complete, partial or broken | Current demand for change-failure records |
| Who owns the history and who signs retirement | The rights review result, including MSP and customer contracts |
| Documented cutover and retirement dates | Any offer to the company |
| That the reward was disclosed | Whether any referral reward becomes payable |

Ask permission first and disclose your interest in the same sentence. SourceX licenses approved business data directly from companies for AI training and evaluation and pays any eligible reward separately under its [terms](/terms), never from the company's payout. Illustrative only: a $400,000 payout to the company would mean a USD 70,000 default reward on its first qualifying transaction; there is no per-company cap, and the USD 50,000 floor applies once per company. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. When the owner opts in, use the [introduction email](/resources/itsm-consolidation-introduction-email). The [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation), the [HaloPSA data page](/systems/halopsa-data) and the [ITSM agents guide](/guides/ai-agents-itsm) cover adjacent situations.

## 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 stage three is still ahead and the owner wants to talk before the old instance retires, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) first.

## Sources

- https://refer.sourcex.si/terms
- 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
