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 stage | Who decides about licensing | Who usually knows the systems | Advisor's move |
|---|---|---|---|
| Preparing to sell, nothing signed | The company's CEO | The CEO, an IT lead or the controller | Ask the CEO first whether to raise the topic at all |
| Signed, not yet closed | The target's CEO, subject to what the signed documents say | The same team, now busy with closing | Transaction counsel reads the documents first; see licensing before closing |
| Closed as a stock sale | The acquirer's CEO | The retained team and the acquirer's integration lead | Reach the acquirer's CEO through someone that CEO trusts |
| Closed as an asset sale | The acquirer's CEO for purchased records; the selling entity's CEO for excluded ones | Split between buyer and seller | Ask 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. | Question | Usually answered by | Never ask for |
|---|---|---|---|
| 1 | Which record families does it hold: orders, work orders, tickets, claim notes, project files? | IT lead or controller | Sample records or screenshots |
| 2 | What are the first and last years of records in it? | IT lead | A query run against it |
| 3 | Roughly how much: thousands, hundreds of thousands or millions of records? | IT lead | An export to count them |
| 4 | Is it running, read-only, switched off with backups kept, or gone? | IT lead | Access to look for yourself |
| 5 | Who administers it today, by role? | IT lead | Credentials |
| 6 | Whose name is on its license or hosting contract, and when does that renew or end? | Controller | The contract itself |
| 7 | Can it still export, and in what general form: files, reports, a database copy or unknown? | IT lead | A test export |
| 8 | Do it or its records move with the deal, stay with the seller or get shut down? | CEO, with counsel's reading of the deal documents | The purchase agreement or its schedules |
| 9 | Will the buyer rely on the seller's systems for a transition period, and when does that end? | CEO or integration lead | The transition agreement |
| 10 | Is a shutdown, deletion or media-wiping date set? | IT lead | The decommissioning plan |
| 11 | Does it hold content that belongs to customers, or personal data about individuals? | CEO or counsel | Customer names or files |
| 12 | Has any of it ever been licensed to anyone for AI training? | CEO | The earlier agreement |
| 13 | Has anyone at the company been in touch with SourceX before, by application, account or email? | CEO | Copies of that correspondence |
| 14 | Whom would the CEO name as the internal sponsor for these records? | CEO | A 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 hold | Where it came from | Can it go in the referral note? |
|---|---|---|
| The old ERP was replaced in 2017 | The IT diligence report | Only if the CEO confirms it in answering question 4 |
| The CRM contract is in the seller's name | The software contract schedule | Only as the CEO's own answer to question 6 |
| Delivery tickets run from 2015 to today | The CEO, during the interview | Yes, with the date |
| The buyer plans to retire the warehouse system soon after closing | The integration plan you saw as advisor | No; ask the acquirer's CEO after closing |
| A large customer's drawings sit in the project system | The data room | No; 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 years | State today | Path through the deal | Clock |
|---|---|---|---|---|
| Green-screen ERP | Orders and returns, 2004 to 2017 | Read-only on a server the seller keeps | Excluded asset; stays with the selling entity | No date set |
| Field-service app | Delivery and job tickets, 2015 to today | Running | Moves to the buyer | No date set |
| Vendor-hosted CRM | Accounts and quotes, 2011 to today | Running; contract in the seller's name | Buyer uses it during the transition period | Access ends with the transition period |
| Email archive | Mailboxes, 2008 to today | Running in the seller's tenant | Stays with the seller | Retention 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.