How to make a referral during an ERP migration: two doors, one no-ask stretch, and a migration-window introduction brief that keeps custody, control and the ask on separate lines

Short answer

Make the referral through the portfolio company's CEO, at one of two doors in the project: while the data migration strategy is still a draft, or after hypercare has ended and before the legacy system is switched off. Between those doors the project team is extracting, loading and reconciling data, and a referral has no place on that critical path. Throughout, the integrator and the data team hold copies, the CEO decides, and the introduction never changes what history is converted, archived or deleted.

Visual briefFull-size diagram
Legacy ERP history from 2012 to 2026 splits three ways: open items and two years into the new ERP, closed detail from 2012 to 2024 into a read-only archive, and records past retention to disposal; door A marks the split before the scope is signed and door B sits on the archive branch after hypercare and before switch-off.
Illustrative migration. Years and the split follow the worked example on this page; the doors are when to ask the CEO, not places in the data.

A VC portfolio operations lead usually learns about an ERP migration from a board budget line, a hiring plan for a project manager or a request to recommend an integrator. Each of those is a reason to know the project's calendar. None of them makes the fund, the integrator or the steering committee a route into the company's records, and being venture-backed has no bearing on fit: size, history, rights and the CEO's authority are tested the same way for every company.

Where the history sits while the project runs, and whose yes counts

During a migration the same history exists in several places at once.

HolderWhat it holdsWhat it may decide about licensing
Legacy system, on premises or with its vendorThe full history, live until cutoverNothing; the vendor contract sets exit and deletion steps
Integrator or migration toolExtracts and staging copies used to build and test the conversionNothing; its contract sets what happens to those copies at project end
New ERPThe converted subset: balances, open items and whatever history the strategy movesNothing beyond the subscription terms
Archive targetClosed detail kept readable after the legacy system goes, in a read-only instance, a warehouse or an archive serviceNothing; it keeps what the company tells it to keep
The companyEvery copy above, as a matter of ownershipThe CEO decides, within any retention duty, hold or contract

Holding a copy never carries the decision. The CEO decides whether the company discusses licensing any of its history. The CFO who sponsors the project, the project manager, the integrator's engagement lead and the steering committee all shape the migration, and none of them stands in for that decision. Neither does the fund's board seat. SourceX's who-qualifies page is plain that what a fund learns through board packs or information rights gives it grounds to ask the CEO and nothing more, so no project detail from board materials travels anywhere except back to the company.

Tax rules make the same point from the other side. Rev. Proc. 98-25, the IRS procedure on machine-sensible records, says that "A taxpayer's use of a third party (such as a service bureau, time-sharing service, value-added network, or other third party service) to provide services in respect of machine-sensible records does not relieve the taxpayer of its recordkeeping obligations." An integrator or archive vendor holding the data changes who has the files, not who answers for them.

The migration-window introduction brief

The brief is one page that the operations lead drafts and the company corrects. It exists so the CEO can answer a single question with the project's real dates in view, and so nobody later has to reconstruct who knew what, and when.

FieldWhat goes in itWho supplies itKeep out
1. Company and decision-makerLegal entity and its CEO, with the date checkedThe companyThe fund's view of who "really" decides
2. Legacy systemSystem name, first year of history, record families it holdsFinance or IT leadScreenshots, sample records
3. Project phase and next gateCurrent phase and the date of the next milestoneProject manager, through the companyBudget, integrator pricing
4. Conversion scopeDraft or signed; the years and detail planned for the new ERPCFO or project managerAny suggestion to change it
5. Legacy planRead-only period, archive target, planned switch-off dateIT leadAny suggestion to extend or shorten it
6. Copies outside the companyIntegrator staging, archive vendor, legacy vendorIT leadRequests for access to any of them
7. Duties to keep or deleteTax retention, litigation holds, customer and employee data limits, as counsel states themCounselThe partner's own reading of the law
8. DoorA, B or stop, and the reasonThe CEOPressure toward a door
9. Partner standingWho will submit, and confirmation that the Channel Partner Agreement is signedThe partnerPromises about credit or reward
10. Date and versionWhen each field was confirmedWhoever confirmed itUndated statements

Fields 4 and 5 matter most, and they are the two the brief must never try to influence. How much history to convert is a finance and operations decision. SourceX's own guide to ERP history and archives argues that retention obligations, not the migration budget, should decide how long archived history stays readable. A referral that nudges either field has stopped being a referral.

Project stages against custody, control and the ask

StageCustodyControlThe introduction
Selection and contractingLegacy system onlyThe CEO approves the projectToo early, unless the CEO raises it
Design: data migration strategy draftedLegacy system, plus first profiling extractsThe CEO, with counsel on duties to keep or deleteDoor A: the brief goes to the CEO while the scope and the legacy plan are still drafts
Build: extract, cleanse, mapIntegrator staging copies multiplyUnchangedNo asks
Mock loads and reconciliationRepeated test loads into the new ERPUnchangedNo asks
CutoverThe new ERP becomes the system of recordUnchangedNo asks
HypercareBoth systems live; legacy mostly read-onlyUnchangedNo asks until it formally ends
Legacy read-only periodArchive target loaded; integrator copies returned or deleted under its contractThe CEO, within tax and other retention dutiesDoor B: the updated brief goes to the CEO before the switch-off date is final
Legacy switch-offOnly the archive and the new ERP remainUnchangedArchive-only conversations, if the CEO wants one

The no-ask stretch is long on purpose. From build until hypercare closes, finance and IT are reconciling balances and fixing defects against a go-live date, and the company has little room for anything new. Section 2 of the program terms credits the first valid introduction of a new company inside a 90-day attribution window, and only once the company submits a verified application, so an introduction made in cutover month can use up its window before anyone at the company has time to apply. Section 3 adds that a company already in contact with SourceX in any form is a duplicate, which is worth checking before door A if the CFO has already filled in a form or emailed SourceX on their own.

Preservation duties come before both doors. Under 26 CFR 1.6001-1(e), records the tax rules require "shall be retained so long as the contents thereof may become material in the administration of any internal revenue law." Rev. Proc. 98-25 adds that retained machine-sensible records "must be capable of being processed," and that the taxpayer "must promptly notify its District Director if any machine-sensible records are lost, stolen, destroyed, damaged, or otherwise no longer capable of being processed." A legacy switch-off is therefore a tax-records decision first, settled by the CFO and the company's advisers. Litigation holds and customer or employee data limits sit beside it, and counsel states them for field 7. The guide to legacy ERP archiving compares the archive options a CFO weighs at that point.

Door A, door B or a stop

What the company says or showsWhat the operations lead does
The CEO says yes at door A, with no hold or disposal conflictIntroduce, using the brief as the company's own record of dates
The CEO says "after go-live"Diary door B and say nothing in between
The strategy is already signed and the project is in buildWait for door B
Counsel flags a hold or a deletion duty on a record familyThat family is out; others can still be discussed
The legacy system is already switched offOnly the archive is in play, if the CEO wants a conversation
Full-time headcount never reached 50, even at the company's peakStop; the program's size test is not met
The CEO is not interestedStop, and do not raise it again at the next milestone

One growth-stage migration through the brief (Illustrative)

Illustrative. The company and its dates are invented, and the example implies no result.

A 210-person equipment rental company, backed by a growth fund, is moving from the on-premises ERP it has run since 2012 to a cloud ERP. The plan converts open items and two fiscal years of detail, sends closed detail from 2012 to 2024 to a read-only archive, and disposes of records past their retention period under the company's own policy.

DateStageWhat happened
3 Feb 2026DesignThe fund's operations lead sends the CFO a blank brief; the CFO fills in fields 2 to 7
17 Feb 2026Door AThe partner who holds the board seat passes the completed brief to the CEO, who answers "after go-live"
4 May to 26 Jun 2026Build and mock loadsNobody raises it
6 Jul 2026CutoverThe cloud ERP goes live
30 Sep 2026Hypercare endsThe project closes its defect list
14 Oct 2026Door BThe updated brief reaches the CEO, with the archive loaded and switch-off planned for 31 Mar 2027; she agrees to a first conversation

The conversation did not change the conversion scope, the archive design or the switch-off date; the CFO and the company's tax advisers set all three. Whether SourceX's review finds the archived history relevant to a current program, and whether anything is ever licensed, are questions the example leaves open.

What could make this approach wrong

  • Projects slip. ERP timelines move, and a long hypercare can squeeze door B against a fixed switch-off date. The brief records dates; it cannot hold them.
  • Retention cuts both ways. Tax rules such as 26 CFR 1.6001-1 can keep history readable for years, while privacy and contract duties can require employee or customer detail to be deleted. Either can take a record family out of any conversation.
  • Rights inside an ERP are mixed. Customer orders, supplier invoices and payroll lines sit beside the company's own transactions, and SourceX's screening asks for rights to license without breaching client confidentiality, employee privacy or third-party contracts.
  • Demand is not measured here. Whether a current program wants ERP history from a given industry is decided in SourceX's review, not by the project calendar.
  • Copies tempt people. Staging extracts and archive exports are convenient and nobody's to offer. One request for a file, from anyone at the fund, costs the trust a CEO needs to say yes.

Methods note. The stages follow phases common to ERP data migrations. The custody, control and introduction columns apply SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, 26 CFR 1.6001-1 and Rev. Proc. 98-25, all checked on 2026-10-27. Stage lengths and the example are Illustrative. Nothing here measures how often CEOs choose door A or door B, how long hypercare runs or how often ERP history is licensed, and no such figures have been published. A platform team can start measuring by logging the date of each brief, the door the CEO chose and the stage the project had reached.

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 a portfolio CEO wants the conversation at door A or door B, create a partner account, confirm the company's facts against who qualifies and read the program terms, which require a signed Channel Partner Agreement before any submission. For the project itself, see how much history to bring into a new ERP, what follows hypercare and integrator confidentiality clauses; for the wider portfolio view, the venture platform teams overview and the guides hub.

Timing a referral around a migration is partner work; readers deciding whether SourceX itself merits an investment can request its investor materials through the SourceX investor overview.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

  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

Should the integrator raise the referral, since its team sees the data every day?

No. The integrator holds staging copies under its contract and has no say over licensing; the CEO decides. If someone at the integrator knows the CEO well, that person can ask whether the CEO wants a conversation, but nothing is drawn from the project's copies.

Can a referral be a reason to keep more history in the archive?

No. How much history is converted and kept is set by finance, operations and retention duties. The referral never argues for changing that scope, and a brief that tries to has stopped being a referral.

What if the project is cancelled and the company stays on its old ERP?

Then there is no switch-off date putting pressure on anyone. Ask the CEO once, at a calm moment, and record the answer and its date in the brief.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. ecfr.gov/current/title-26/chapter-I/subchapter-A/part…
  4. irs.gov/pub/irs-drop/rp-98-25.pdf
  5. sourcex.si/insights/erp-migration-how-much-history-to-m…
  6. sourcex.si/investors

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