ERP consolidation after acquisitions: what ledger and workflow history to keep

Why ERP history matters beyond the trial balance

The trial balance proves the numbers tie. It does not show how the business got there: who approved a purchase order above their limit, why a three-way match failed, which customer went on credit hold and why it was released, what the memo on a manual journal entry said, or how a bill of materials changed after a quality problem. That workflow trail lives only in the source ERP, and it is exactly what a summarized migration leaves behind.

In practice, ERP partners decide how much of it survives. Finance asks for balances and open items, the integration budget favors a clean cutover and the old license has an end date. Unless someone scopes an archive, years of operating history go with the old instance.

Roll-ups make the question bigger. PitchBook reported that the median holding period of US PE-backed companies still in portfolios reached 3.4 years at the end of 2024, the longest in more than nine years, with over 30% held at least five years. Longer holds can leave sponsors more time for add-ons, and each add-on arrives with its own ERP and its own history. The guide to value creation in extended hold periods covers why sponsors are looking harder at assets they already own.

Three migration depths and what each leaves behind

Most consolidations pick the first or second approach for sound reasons. The goal is not to migrate everything. It is to make sure whatever stays behind remains queryable, with its context intact, after the old license lapses.

Consolidation timeline: what to do and when

ERP cutovers follow the fiscal calendar and usually land on a period end or year end. Make the history decisions alongside the cutover plan, not after it.

The stretch between cutover and decommissioning is the useful window. The legacy instance is read-only, the archive has been tested, and leadership can decide what the preserved history is worth before the final license payment lapses. The sales side faces the same choice, covered in CRM consolidation after an acquisition.

What to keep: the workflow history checklist

Finance and close

• General ledger detail with journal entry memos, preparers and approvers
• Receivables and payables subledgers, including write-offs and their reasons
• Period close checklists, reconciliations and adjusting entries

Procure to pay

• Requisitions, purchase orders and their approval chains
• Three-way match exceptions and how each was resolved
• Vendor master change history, including changes to remittance details

Order to cash

• Quotes, sales orders, credit holds and releases
• Returns, credit memos and reason codes
• Customer master changes and pricing overrides

Operations

• Work orders, inventory adjustments with notes and cycle count history
• Bills of materials and engineering change history
• Project budgets, change orders and actuals

System context

• Audit trail and user role history
• Definitions of custom fields, workflows and saved reports
• Attachments such as scanned invoices, contracts and packing slips

Deep history across these areas, linked by record IDs, is what turns an ERP archive into more than a compliance copy. The ERP consultant referral overview explains how partners recognize companies where that depth exists.

Confidentiality limits

ERP data carries more confidentiality obligations than most systems. Customer pricing and vendor terms are often covered by contractual confidentiality clauses, payroll and HR modules hold employee personal data, and bank details are sensitive in any context. The company and its counsel set any licensing scope, and modules such as payroll are commonly excluded or redacted.

Licensing does not widen the consultant's remit. Keep the archive intact as part of the engagement and leave the ledgers where they are: nothing is extracted, sampled or described to outsiders. Redaction and de-identification rules are set between the company and SourceX before any work, and data moves only after an executed agreement and the company's authorization.

Who to talk to, and what to say

The CFO decides history depth and pays for the archive. The controller knows which records the auditors and tax advisers still rely on. The integration lead owns the cutover date. In a PE-backed roll-up, the sponsor's operating partner often sets priorities across every add-on. For how a newly installed finance leader orders these systems decisions, see the portfolio CFO first 90 days guide.

When an introduction fits

An introduction makes sense when the consolidated company, or the acquired entity on its own, has 50+ full-time employees at peak (contractors excluded), several years of documented operations, history across the ERP and connected systems, the right to license it and an executive who can authorize a license. A quick, non-binding check with the company fit checker is a reasonable first filter, and the who qualifies page covers the full baseline.

Skip it when the acquired entity's books were kept by an outside bookkeeper in a small accounting package with little operational detail, when the legacy data has already been purged, or when a court, trustee or lender controls the assets and has not been involved.

ERP partners who make the introduction earn 25% of the eligible platform fees SourceX collects from that company's licensing deals, with a cap of $100,000 per referred company. Nothing is payable until the buyer has paid and SourceX has its fee in hand, and rewards are not guaranteed. Check your consulting agreement and any vendor partner program rules before accepting a referral fee.

Next step

Add an archive sign-off line to the decommissioning checklist on your next consolidation. Then register as a partner so any introduction you make is attributed to you.