Catalog rollout archive context checklist: what to confirm before legacy inventories and sources are retired

Short answer

Work through three milestones in order: before the catalog rollout is announced, before the catalog goes live as the place people look things up, and before the legacy inventory, data dictionary or any retiring source system is switched off. At each one, confirm whether the owner can still name the source, decision and permitted scope for each record group, who owns each answer, and what is lost if the item is skipped. Every date comes from the company's own plan or contracts.

Visual briefFull-size diagram
A countdown timeline with three milestones (announcement, catalog go-live and legacy switch-off) where checklist items tick off in turn before the legacy inventory and retiring source systems are switched off.
The checklist as a countdown. Milestone dates come from the company's own rollout plan and contracts.

This checklist belongs to the catalog rollout guide. The three-part question is first asked in the 15-minute meeting agenda; this page carries the open answers forward to the day the old inventory goes dark.

What actually gets switched off in a catalog rollout

A catalog is additive, so the risk is easy to miss. What disappears is the material around it.

Thing retiredWhy it mattersWhere the date comes from
The spreadsheet or wiki inventory stewards kept before the catalogIt often holds the only written note of what a dataset means and which decision it recordsThe rollout plan's decommission step
A legacy data dictionary or older catalog toolBusiness descriptions and owners may not import cleanlyThe old tool's license or support end
A source system replaced during the programRecords may move while their process context stays behindThe replacement project's cutover plan
Lineage events older than a platform's retention windowHistory of how data moved may age outThe platform's documentation

The last row is documented for some platforms. Databricks states that its Unity Catalog lineage system tables keep a rolling one-year window, with older events removed, while Catalog Explorer and the lineage API keep lineage captured after September 1, 2024. That sets no deadline for any company; it tells you to ask what the company's own platform keeps.

Mark every item confirmed (a responsible person said so), unknown (with a name for who will find out) or at risk (the current plan loses it). Ask for descriptions; never ask anyone to open the catalog or send an export.

Milestone one: before the rollout is announced

The program scope is still being drawn. Questions cost nothing now.

ConfirmOwnerIf skipped
Which record groups the rollout will cover first, with start years and rough volumesData governance leadThe checklist has nothing concrete to track
Where business definitions live today (spreadsheet, wiki, old dictionary)Data stewardThe only written context is treated as disposable
Whether "decision documented" will be a catalog field, or only technical metadataData governance leadThe catalog launches with source filled and decision blank
The CEO, who can authorize a licensing discussion about the company's records, by nameOwner or CEOAn interested company has nobody able to say yes

Milestone two: before the catalog goes live

Go-live is when people stop updating the old inventory. Capture what it knows first.

ConfirmOwnerIf skipped
Each priority group's source is scanned, or manually entered where scanning does not reachPlatform ownerLineage gaps look like missing data rather than manual work
Each priority group names the decision it records and the role that made itProcess owner"Rows in a table" is all anyone can say later
Permitted scope has an owner for each priority group, even if the answer is "under review"Counsel or contract ownerScope stays nobody's question indefinitely
Descriptions from the old inventory are carried into the catalog's business layerData stewardYears of notes vanish when the spreadsheet is archived

The second row is the one catalogs miss. In Microsoft Purview, scans fill the Data Map and stewards curate the Unified Catalog; Microsoft's lineage guide covers manual and custom lineage where automation does not reach. None of that captures the business judgment a record documents. The W3C PROV model calls this the activity and the agent, alongside the entity, and it is the part a person has to write down.

Milestone three: before legacy sources are switched off

Once the old inventory is archived or a source system is retired, missing context is hard to recover.

ConfirmOwnerIf skipped
The actual switch-off date for each retiring tool or system, from its contract or planIT or finance leadThe team learns the date after it has passed
Records from any retiring source system have a readable home and a named custodianPlatform ownerRecords survive but nobody can explain them
Lineage history the company wants kept is copied before any retention window removes itPlatform ownerHow data moved between systems is lost
Scope answers marked "under review" have a dated follow-up with counselOwnerOpen questions quietly become permanent gaps

The guide to assessing governance procedures without exposing restricted documents shows how to ask about policies without reading them, and the data catalog vs data inventory comparison explains why retiring the inventory is the risky step.

The summary you hand the owner

Illustrative. A fictional 310-person regional utility contractor completed all three milestones. The advisor's one-page summary read:

AreaStateNote
Priority record groupsConfirmedWork orders from 2012, safety inspections from 2015, change requests from 2018
Source and lineageConfirmedScanned, with manual lineage for the field app
Decision recordedPartialInspections and change approvals named; work orders lack approver role before 2016
Permitted scopePartialCounsel reviewing client contracts; follow-up dated
Legacy inventoryAt riskSpreadsheet scheduled for archive; descriptions half migrated
Authorized contactConfirmedCEO

That is a sound metadata-level description. If the owner wants to explore licensing:

Disclose. You are a SourceX referral partner. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward that it funds separately and never deducts from the company's payout.

Check fit. 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. SourceX's current data needs, the rights review result and any offer stay unknown until SourceX reviews an application.

Introduce. Use the catalog rollout introduction email, after signing the Channel Partner Agreement. 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. Illustrative only: an $800,000 payout to the company on its first qualifying transaction would mean a USD 120,000 reward (15%, above the USD 50,000 plus 5% floor), and there is no cap per company. The rewards page lists every condition. Advisors working inside SAP programs can compare the SAP partner referral page.

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 checklist shows priority record groups keep their source, decision and scope through switch-off and the owner wants to talk, register as a partner, check who qualifies and read the program terms before introducing.

  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

A catalog does not delete anything. Why would context be lost?

The catalog itself rarely removes data, but rollouts often retire what came before: the spreadsheet inventory where stewards wrote what each dataset meant, a legacy data dictionary, or a source system replaced during the program. Some lineage stores also keep events for a limited window.

Who keeps the checklist?

The advisor keeps the record of answers at metadata level, shared only with the people who gave them. Decisions about archiving, exporting or retiring anything belong to the company.

What if the company has no switch-off date?

Then milestone three stays open with one item: confirm whether anything is being retired. Do not invent a deadline; an open milestone is a correct answer.

Sources

  1. learn.microsoft.com/en-us/purview/unified-catalog
  2. learn.microsoft.com/en-us/purview/data-gov-classic-lineage-user-…
  3. docs.databricks.com/aws/en/admin/system-tables/lineage
  4. w3.org/TR/prov-o
  5. refer.sourcex.si/terms

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