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.
| Holder | What it holds | What it may decide about licensing |
|---|---|---|
| Legacy system, on premises or with its vendor | The full history, live until cutover | Nothing; the vendor contract sets exit and deletion steps |
| Integrator or migration tool | Extracts and staging copies used to build and test the conversion | Nothing; its contract sets what happens to those copies at project end |
| New ERP | The converted subset: balances, open items and whatever history the strategy moves | Nothing beyond the subscription terms |
| Archive target | Closed detail kept readable after the legacy system goes, in a read-only instance, a warehouse or an archive service | Nothing; it keeps what the company tells it to keep |
| The company | Every copy above, as a matter of ownership | The 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.
| Field | What goes in it | Who supplies it | Keep out |
|---|---|---|---|
| 1. Company and decision-maker | Legal entity and its CEO, with the date checked | The company | The fund's view of who "really" decides |
| 2. Legacy system | System name, first year of history, record families it holds | Finance or IT lead | Screenshots, sample records |
| 3. Project phase and next gate | Current phase and the date of the next milestone | Project manager, through the company | Budget, integrator pricing |
| 4. Conversion scope | Draft or signed; the years and detail planned for the new ERP | CFO or project manager | Any suggestion to change it |
| 5. Legacy plan | Read-only period, archive target, planned switch-off date | IT lead | Any suggestion to extend or shorten it |
| 6. Copies outside the company | Integrator staging, archive vendor, legacy vendor | IT lead | Requests for access to any of them |
| 7. Duties to keep or delete | Tax retention, litigation holds, customer and employee data limits, as counsel states them | Counsel | The partner's own reading of the law |
| 8. Door | A, B or stop, and the reason | The CEO | Pressure toward a door |
| 9. Partner standing | Who will submit, and confirmation that the Channel Partner Agreement is signed | The partner | Promises about credit or reward |
| 10. Date and version | When each field was confirmed | Whoever confirmed it | Undated 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
| Stage | Custody | Control | The introduction |
|---|---|---|---|
| Selection and contracting | Legacy system only | The CEO approves the project | Too early, unless the CEO raises it |
| Design: data migration strategy drafted | Legacy system, plus first profiling extracts | The CEO, with counsel on duties to keep or delete | Door A: the brief goes to the CEO while the scope and the legacy plan are still drafts |
| Build: extract, cleanse, map | Integrator staging copies multiply | Unchanged | No asks |
| Mock loads and reconciliation | Repeated test loads into the new ERP | Unchanged | No asks |
| Cutover | The new ERP becomes the system of record | Unchanged | No asks |
| Hypercare | Both systems live; legacy mostly read-only | Unchanged | No asks until it formally ends |
| Legacy read-only period | Archive target loaded; integrator copies returned or deleted under its contract | The CEO, within tax and other retention duties | Door B: the updated brief goes to the CEO before the switch-off date is final |
| Legacy switch-off | Only the archive and the new ERP remain | Unchanged | Archive-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 shows | What the operations lead does |
|---|---|
| The CEO says yes at door A, with no hold or disposal conflict | Introduce, 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 build | Wait for door B |
| Counsel flags a hold or a deletion duty on a record family | That family is out; others can still be discussed |
| The legacy system is already switched off | Only the archive is in play, if the CEO wants a conversation |
| Full-time headcount never reached 50, even at the company's peak | Stop; the program's size test is not met |
| The CEO is not interested | Stop, 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.
| Date | Stage | What happened |
|---|---|---|
| 3 Feb 2026 | Design | The fund's operations lead sends the CFO a blank brief; the CFO fills in fields 2 to 7 |
| 17 Feb 2026 | Door A | The partner who holds the board seat passes the completed brief to the CEO, who answers "after go-live" |
| 4 May to 26 Jun 2026 | Build and mock loads | Nobody raises it |
| 6 Jul 2026 | Cutover | The cloud ERP goes live |
| 30 Sep 2026 | Hypercare ends | The project closes its defect list |
| 14 Oct 2026 | Door B | The 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.