What an M&A advisor should ask about legacy systems: a 14-question metadata interview that dates each old system, shows who will control it after the deal and stops before anyone opens a file

Short answer

Ask about the systems, never their contents. For each old system: which record families it holds and for which years, whether it still runs or sits read-only, who administers it, whose name is on the contract, whether it moves in the deal, when it will be switched off, and whether any of it was ever licensed for AI training. Ask the company's CEO, or the person the CEO names, once the CEO wants the conversation, and leave what the data room taught you out of it.

Visual briefFull-size diagram
A timeline from 2004 to 2027 with four Illustrative system bars: an ERP read-only since 2017 that stays with the seller, a field-service app that moves to the buyer, a CRM whose access ends with the transition period and an email archive in the seller's tenant, with a closing marker just after the bars end.
Illustrative asset sale. Systems, years and paths match the worked example on this page; no real company.

Legacy systems matter because a sale is exactly when they get retired, transferred or stranded, and because they often hold a company's oldest years. They do not matter as a selling point. An advisor who presents an old ERP as hidden deal value is guessing at a price SourceX has not offered and does not publish.

Who answers depends on where the deal stands

Authority moves at closing, and records can split along the deal's structure. SourceX's screening page puts an acquired company's decision with the acquirer's CEO and says the structure of a sale decides who holds the records afterward.

Deal stageWho decides about licensingWho usually knows the systemsAdvisor's move
Preparing to sell, nothing signedThe company's CEOThe CEO, an IT lead or the controllerAsk the CEO first whether to raise the topic at all
Signed, not yet closedThe target's CEO, subject to what the signed documents sayThe same team, now busy with closingTransaction counsel reads the documents first; see licensing before closing
Closed as a stock saleThe acquirer's CEOThe retained team and the acquirer's integration leadReach the acquirer's CEO through someone that CEO trusts
Closed as an asset saleThe acquirer's CEO for purchased records; the selling entity's CEO for excluded onesSplit between buyer and sellerAsk each side only about the records it now holds

Records left behind as excluded assets stay with the selling entity, and its own CEO decides for them; the excluded assets guide covers the kinds of records that tend to stay.

Why old systems matter to a licensing review, and why they are not deal value

SourceX's process starts with systems. Its process page says a company lists its systems, years of history and what can be exported; that SourceX focuses on companies with 50+ full-time employees at peak; that companies which qualify name five or more systems; and that no records are shared at that stage. Two of the fit signals it lists are historical depth and clear ownership. A legacy system is often where the early years live, and a sale is often the moment it is retired or left behind.

The same page limits what an advisor may claim. Every supplier confirms its data has not been licensed for AI training before. Pricing stays indicative until the company signs a Dataset Deal Confirmation with SourceX, and final value depends on actual Acquisition Partner demand and due diligence. The interview gathers facts for a possible introduction; it produces no number for a teaser, a CIM or a price negotiation. The listing claims checklist shows where that line sits in marketing materials.

The legacy-system metadata interview

Fourteen questions in four groups, asked once per system. Every answer is a description: a name, a year, a yes or no, a role. The right-hand column is the line nobody crosses.

No.QuestionUsually answered byNever ask for
1Which record families does it hold: orders, work orders, tickets, claim notes, project files?IT lead or controllerSample records or screenshots
2What are the first and last years of records in it?IT leadA query run against it
3Roughly how much: thousands, hundreds of thousands or millions of records?IT leadAn export to count them
4Is it running, read-only, switched off with backups kept, or gone?IT leadAccess to look for yourself
5Who administers it today, by role?IT leadCredentials
6Whose name is on its license or hosting contract, and when does that renew or end?ControllerThe contract itself
7Can it still export, and in what general form: files, reports, a database copy or unknown?IT leadA test export
8Do it or its records move with the deal, stay with the seller or get shut down?CEO, with counsel's reading of the deal documentsThe purchase agreement or its schedules
9Will the buyer rely on the seller's systems for a transition period, and when does that end?CEO or integration leadThe transition agreement
10Is a shutdown, deletion or media-wiping date set?IT leadThe decommissioning plan
11Does it hold content that belongs to customers, or personal data about individuals?CEO or counselCustomer names or files
12Has any of it ever been licensed to anyone for AI training?CEOThe earlier agreement
13Has anyone at the company been in touch with SourceX before, by application, account or email?CEOCopies of that correspondence
14Whom would the CEO name as the internal sponsor for these records?CEOA promise that the sponsor will agree

Groups run in order: what it holds (1 to 3), its state today (4 to 7), its path through the deal (8 to 10), rights and history (11 to 14). Three questions carry extra weight.

  • Question 12 is a stop question. A supplier confirms to SourceX that its data has not been licensed for AI training before, so a yes ends the conversation for that system.
  • Question 13 is a credit question. Section 3 of the terms makes a company with an earlier application, relationship or valid introduction a duplicate, and it counts any earlier lead, account or email correspondence as a relationship. A yes means no partner will be credited, though the company can still talk to SourceX.
  • Question 10 sets the clock. NIST's media sanitization guideline describes sanitization as a process that makes access to the target data infeasible for a given level of effort. Once a retired system's storage has been wiped that way, there is nothing left to discuss. A dated shutdown is the only real urgency this interview can surface.

Questions 4 to 7 mirror what the company is asked when it applies. The transition services agreement explainer helps with question 9, and system decommissioning after an acquisition with question 10.

Two notebooks: the deal file and the referral note

An advisor in a sale learns far more about a company's systems than any referral needs, and all of it belongs to the engagement and the client who shared it. Keep two notebooks. The deal file holds what the engagement gave you. The referral note holds only answers the CEO gave or approved for this purpose, each with a date.

A fact you holdWhere it came fromCan it go in the referral note?
The old ERP was replaced in 2017The IT diligence reportOnly if the CEO confirms it in answering question 4
The CRM contract is in the seller's nameThe software contract scheduleOnly as the CEO's own answer to question 6
Delivery tickets run from 2015 to todayThe CEO, during the interviewYes, with the date
The buyer plans to retire the warehouse system soon after closingThe integration plan you saw as advisorNo; ask the acquirer's CEO after closing
A large customer's drawings sit in the project systemThe data roomNo; question 11 lets the CEO say it in their own words

The test is where a fact came from, not how sensitive it looks. A harmless-seeming detail that came from the data room still stays in the deal file.

One asset sale, four systems (Illustrative)

Illustrative: the company, its systems, the years and the deal are invented to show how the interview reads; none of it describes a real transaction.

A 280-person regional building-supply distributor is selling its operating assets to a larger group. With the CEO's agreement, the sell-side advisor runs the interview with the CEO and the IT manager in one hour. Every answer stays at metadata level.

System (Illustrative)Records and yearsState todayPath through the dealClock
Green-screen ERPOrders and returns, 2004 to 2017Read-only on a server the seller keepsExcluded asset; stays with the selling entityNo date set
Field-service appDelivery and job tickets, 2015 to todayRunningMoves to the buyerNo date set
Vendor-hosted CRMAccounts and quotes, 2011 to todayRunning; contract in the seller's nameBuyer uses it during the transition periodAccess ends with the transition period
Email archiveMailboxes, 2008 to todayRunning in the seller's tenantStays with the sellerRetention review planned after closing

Three consequences follow. The ERP's fourteen years stay with the selling entity, so after closing its CEO, not the buyer's, decides about them, and only if that entity can show the size, history and rights SourceX screens for. The field-service records become the buyer's, and the acquirer's CEO decides. The CRM carries the only real clock, and the person who can act before it runs out is the target's CEO today or the acquirer's CEO after closing. Nobody saw a record, and the advisor's note lists what was not asked: no contracts, no exports, no customer names.

Choosing a route that leaves the deal alone

Raise the idea with the CEO only, at a moment the CEO picks, and not during exclusivity or the closing crunch unless the CEO asks. If the answers point to a possible fit, the company applies through your partner link, or you submit a written introduction the CEO has approved, having signed the SourceX Channel Partner Agreement first. Do not join SourceX's calls with the company, forward anything from the deal file or let the conversation touch price or deal terms.

Write your limits down as you go: the date the CEO agreed, who answered which question, and the questions you chose not to ask. If question 12 or 13 comes back yes, record it and stop. If closing is days away and authority is about to move, wait and ask the acquirer's CEO afterward, unless the target's CEO wants to proceed and transaction counsel is comfortable. Your own engagement letter may limit outside fees; when an existing engagement limits outside referral fees covers that check. For the acquirer's side of keeping old systems readable, the main SourceX site has a guide to preserving legacy systems and archives after an acquisition.

Fit facts SourceX screens before anything else

The interview is wasted on a company that fails the basic screen. Check these at the level of descriptions: a full-time workforce that reached 50 or more at its peak, with contractors left out; years of records the company created itself; the right to license them, which client-owned material usually defeats; and a CEO who wants the conversation. 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 stays unknown until SourceX reviews the company: whether its records fit a current program, whether customer contracts or the deal documents limit them, and what a license would cover.

Where the interview misleads

  • Memory is not an inventory. An IT manager's "2004" may be the go-live year rather than the first surviving record. SourceX completes the inventory with the company; the interview only points.
  • Rights are not settled here. Customer contracts, privacy and the deal documents are read by counsel and in SourceX's review, not by the advisor.
  • Paths change. A transition period can be cut short or extended, and a system marked "moves to buyer" can still be retired soon after.
  • The data room leaks in. The most common failure is an advisor answering a question from memory of the deal file. If the CEO did not say it, it is not in the note.
  • A system may already be gone. Wiped storage cannot be restored, and no interview revives it.

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.

When the interview shows records the company holds and a CEO who wants to explore them, register for a partner link, compare the company against who qualifies and read the attribution and duplicate sections of the program terms before anything is submitted. The overview for M&A advisors and the guides library cover other transaction moments.

  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

Can an advisor run the interview without telling the CEO why?

No. The CEO decides whether the company discusses licensing at all, and SourceX's screening page treats introductions made without the decision maker's knowledge as usually not a fit. Explain the reason first; the CEO chooses whether the interview happens.

Should legacy records appear in a CIM or teaser as a source of value?

No. SourceX keeps any price indicative until the company signs a Dataset Deal Confirmation, and final value depends on demand and due diligence. Describing old records as deal value is a guess the advisor cannot support.

What if the records are about to be wiped?

Tell the person who decides about them, now: the target's CEO before closing, the acquirer's CEO after, or the selling entity's CEO for excluded records. A dated shutdown is real urgency; once storage is sanitized, nothing can be licensed.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r…

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