ITSM consolidation archive context checklist: what to confirm before the old service desk instance retires

Short answer

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.

Visual briefFull-size diagram
A vertical countdown with three stages, announcement, cutover and instance retirement, where checklist items about the caused-by-change link, backout plans, work notes and archive tables tick off before the old instance is switched off.
The checklist as a countdown. Stage dates come from the company's own consolidation plan.

This is part of the consolidation guide for platform consultants. The 25-minute meeting agenda is where the questions are first asked; this checklist keeps the answers current through to retirement.

Fixing the countdown dates

StageTypical source of the dateIf the date is missing
AnnouncementThe consolidation business case, an acquisition integration plan or a license renewalStart early and treat stage one as a calm inventory
CutoverThe migration runbook for the target instanceRecord who owns go-live
RetirementThe old instance's subscription end, a decommission request or an integration milestoneLeave 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 confirmOwnerCost of skipping it
How many instances or tools hold change and incident history, and how many years eachPlatform ownerThe oldest instance is forgotten when scope is written
Whether incidents name the change that triggered them, and how consistently across teamsIncident managerNobody knows the chain is thin until it is gone
Whether normal changes carry a written restore planChange managerThe intended recovery cannot be shown for older changes
Who owns ticket history if an MSP or the acquired company ran the deskCIO or ownerRights 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 confirmOwnerCost of skipping it
Whether changes are renumbered, and whether a cross-reference to old numbers is keptPlatform ownerIncident references point to change numbers that no longer exist
Whether each incident's pointer to its triggering change is updated to the new numberingMigration leadBoth sets land intact while the pointer between them breaks
Whether work notes and journal history migrate or stay behindPlatform ownerThe reasoning behind each reversal stays in the old instance
Where post-change reviews and change board minutes live, inside or outside the platformChange managerReviews 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 confirmOwnerCost of skipping it
What happens to archive tables in the old instancePlatform ownerArchived years disappear with the instance
Whether the read-only period has a documented end and a reviewerCIORetirement happens at license renewal without review
Who signs off the final retention decisionCIO or COONo one is accountable for what was dropped
Whether the owner wants to hear about licensing before switch-offOwnerThe 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 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 youWhat only SourceX review can tell you
Instances, years and whether the chain is complete, partial or brokenCurrent demand for change-failure records
Who owns the history and who signs retirementThe rights review result, including MSP and customer contracts
Documented cutover and retirement datesAny offer to the company
That the reward was disclosedWhether 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, 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. The software consolidation handoff checklist, the HaloPSA data page and the ITSM agents guide 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, confirm the company against who qualifies, and read the program terms first.

  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 cross-reference table between old and new change numbers really necessary?

It is the single item that keeps the incident-to-change link readable after renumbering. Whether to build one is the platform team's decision; the checklist only makes sure someone decides it on purpose.

What if the old instance stays read-only indefinitely?

Record the documented plan and who reviews it. Read-only instances can be retired later when the license is reviewed, so the third stage is postponed, not removed.

Does the consultant need admin rights to complete the checklist?

No. Every item is answered by the people who own the process or the platform. The consultant records answers as counts, years, system names and owners.

Sources

  1. refer.sourcex.si/terms
  2. servicenow.com/docs/r/it-service-management/incident-manage…
  3. servicenow.com/docs/r/BgFKZnPHldZ62gGtzQ71Mw/cZZFYNfdM7ypDo…
  4. support.servicenow.com/kb

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