Private equity and portfolios
Distribution roll-ups: consolidating ERP and customer data across acquisitions
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Distribution roll-up ERP consolidation works best in a fixed sequence: check rights for each acquired entity, map customer, item and vendor masters with a crosswalk that keeps legacy IDs, then archive each old ERP in full before its license or server goes away. Skipping the rights check or the crosswalk is what usually breaks history later.
Key takeaways
- Run the rights check per acquired entity before records move, because each purchase agreement and customer contract sets its own limits.
- Keep a crosswalk from every legacy customer, item and vendor ID to the new master, or years of history become impossible to link.
- Migrate what is open and active, and archive closed history in full, including notes, attachments and user-defined fields.
- Export each archive while the legacy vendor contract is live and the people who ran the system are still on staff.
- A consolidated history with intact crosswalks is a stronger base for analytics, AI tools and any later data licensing.
Why is ERP consolidation harder in a distribution roll-up?#
ERP consolidation is harder in a distribution roll-up because each add-on arrives with its own system, its own numbering and its own contracts, and the platform has to merge them while orders keep shipping. A buy-and-build platform may run NetSuite or Acumatica at the center while add-ons sit on Epicor, Infor, SAP Business One or a long-serving on-premise system.
The same customer often appears under different account numbers at several branches. The same manufacturer part carries different SKUs, pack sizes and units of measure. Contract pricing, rebate tracking and ship-to structures differ by entity. Integration teams under pressure to report combined numbers tend to move open orders and balances quickly and leave history for later, and later is where history gets lost.
Step one: check rights for each acquired entity#
The rights check for each acquired entity establishes what the platform may do with that entity's records before anything is copied, merged or deleted. Owning the company does not settle every question, because the deal structure, customer contracts and vendor terms all shape what can move and how it can be used.
Record the answers per entity in a short rights memo. The memo travels with that entity's archive, so a later question about analytics, AI tools or licensing does not restart the review from scratch.
| Rights question | Where to look | Why it matters |
|---|---|---|
| Was the deal a stock or an asset purchase? | Purchase agreement and its schedules | In an asset deal, only listed records and assigned contracts transfer, and some contracts need the customer's consent to assign; in a stock deal, contracts stay with the entity but change-of-control clauses may apply |
| Do customer contracts limit use of order data? | National account agreements, supply agreements, confidentiality clauses | Some contracts restrict use of order details to fulfilling the order |
| What does the legacy ERP vendor allow? | Subscription terms, hosting agreement, termination clauses | Export rights and read-only access after termination vary by vendor and contract |
| What notice did customers and employees receive? | Website privacy notices, employee handbooks, email policies | Notices shape how personal details inside records may be used |
| Are there supplier confidentiality terms? | Line card agreements, rebate programs, special pricing authorizations | Supplier cost and rebate data is often confidential to the distributor |
Step two: map customer, item and vendor masters#
Master data mapping links every legacy customer, item and vendor record to its counterpart in the target ERP, and the crosswalk it produces is the integration artifact that keeps history usable. Without a crosswalk, an invoice in an add-on's old system cannot be tied to the same customer in the new one, and trends by account or product break at the acquisition date.
Mapping involves judgment calls, such as whether two similar accounts are one customer or two. Log who made each decision and why, because auditors and a future buyer's diligence team may ask.
- Customer master: match accounts across entities, keep the legacy account ID on the new record and preserve ship-to and bill-to hierarchies.
- CRM and contacts: merge contacts and opportunities from each entity's CRM or shared inboxes, keep the source-system ID and carry over email opt-outs so nobody who unsubscribed is mailed again.
- Item master: map legacy SKUs to one item per manufacturer part, convert units of measure and pack sizes, and record every conversion rule.
- Vendor master: merge duplicate suppliers and keep the legacy vendor ID for purchase history and rebate claims.
- Pricing: move active contract prices and price matrices, and archive expired agreements with their effective dates.
- Open transactions: migrate open orders, open purchase orders and open receivables with references to legacy document numbers.
- Crosswalk storage: keep the mapping tables as governed records with a named owner, not in an analyst's personal spreadsheet.
What should migrate, and what should stay in the archive?#
Open and active data should migrate to the target ERP, and closed history should stay in a complete, read-only archive with the crosswalk attached. Loading every closed transaction into the new ERP is costly and clutters the system, while dropping closed history loses the record that analytics, AI tools and diligence teams rely on.
Order notes and exception comments need special care. They often sit in free-text fields or attachment tables that standard migration templates skip, and they hold the reasoning behind substitutions, credits and rush orders.
| Data | Migrate to the target ERP | Keep in the archive |
|---|---|---|
| Customers and ship-tos | Active accounts with legacy IDs | Inactive accounts and full change history |
| Items | Active SKUs mapped to the new item master | Discontinued items and old unit conversions |
| Orders and invoices | Open orders and open receivables | Closed orders, invoices and credit memos |
| Notes and attachments | Notes on open orders | All order notes, emailed attachments and exception comments |
| Pricing | Current contract pricing | Expired price agreements with effective dates |
| Audit trails | Rarely | User change logs and approval histories |
Step three: archive old ERPs before access ends#
Archiving an old ERP means exporting its full tables, notes and attachments into storage the platform controls, and verifying the export, before the subscription, hosting contract or server goes away. Standard reports and summary extracts are not an archive, because they drop the detail and the links between records.
The right moment to archive is before the integration team decommissions the system, not after an auditor or a buyer asks for history that no longer exists.
- Confirm the termination date of the legacy subscription or hosting agreement and any post-termination export period.
- Export raw tables, including user-defined fields, free-text notes, attachments and audit logs.
- Capture the schema and a data dictionary while the people who ran the system are still employed.
- Record row counts and date ranges per table, and compare them to the live system before shutdown.
- Store the archive read-only, with access controls and the entity's rights memo alongside it.
- Set retention for tax, audit and contract purposes with the CFO and advisers before deleting anything.
Who signs off each gate before a legacy ERP is switched off?#
Each gate before a legacy ERP is switched off needs a named owner and a piece of evidence, because integration teams move on and the questions arrive later from auditors, lenders or a buyer. A one-page gate log per acquired entity is enough, as long as it is kept with the archive.
The operating partner does not need to run these gates, only to insist that none is skipped when the ERP renewal date gets close.
| Gate | Usual owner | Evidence that closes it |
|---|---|---|
| Rights memo | Counsel with the deal team | A short memo per entity listing restricted customers, supplier terms and vendor export rights |
| Crosswalk | Master data owner in finance or IT | Versioned customer, item and vendor mapping tables with a log of judgment calls |
| Open transactions | Controller | Open orders, open payables and receivables reconciled to the legacy system at cutover |
| Archive | IT or integration lead | Table list, row counts, date ranges and schema notes compared with the live system |
| Retention | CFO with advisers | A retention schedule and any legal holds recorded for the entity |
| Decommission | Integration lead, approved by the operating partner | Sign-off that every gate above is closed before the subscription or server ends |
Illustrative: a building products roll-up with four ERPs#
Illustrative: a fictional building products distribution platform runs Acumatica and has acquired three regional distributors, on SAP Business One, Epicor and a green-screen system on an IBM i server. The operating partner sets a rule that no legacy system is switched off until its rights memo, crosswalk and archive are signed off.
The rights check finds that one add-on's largest customer contract limits use of order details to fulfillment, so that customer's records are tagged in the archive. Item mapping shows the same fastener sold under several SKUs with different pack sizes, and the conversion rules are stored with the crosswalk. On the IBM i system, order notes live in a separate file that the standard migration tool ignored, so the archive team exports that file on its own.
When the platform later considers data licensing, the archive already shows which years and record families exist for each entity, which customers are restricted and how legacy IDs map to current accounts.
Where licensing fits after consolidation#
Consolidated archives are a practical starting point for data licensing, because a roll-up's combined history of orders, exceptions and customer service can span more regions, product lines and situations than any single distributor holds. Each acquired entity's records keep their own rights trail, even when they ship in one package and even if the entity was later merged into the platform.
SourceX works through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The rights memos and crosswalks from integration feed the Rights and Preparation steps, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization for each entity's records. Nothing is shared during the initial fit check, and the platform approves every step.
Frequently asked questions
Should a roll-up move onto one ERP or run several with a reporting layer?
Both paths can work if the crosswalk is maintained. Some platforms keep add-ons on their own ERP for a period and consolidate reporting in a data warehouse. The data steps stay the same either way: a rights check per entity, mapped masters with legacy IDs, and a complete archive whenever a system is retired.
Who should own the crosswalk tables after integration?
A named owner in finance or IT, usually whoever governs master data for the platform. The crosswalk should live alongside the ERP, be versioned when mapping decisions change and be included in data room materials when the platform is sold.
Can a legacy ERP vendor limit access to our own data?
Vendor contracts differ. Some include export rights and a period of access after termination; others limit exports to standard formats or charge for assistance. Read the agreement before giving notice of termination, and plan the export while the subscription is still active.
Do we need customer consent to merge customer data across entities?
Sometimes. The answer turns on each entity's customer agreements, the privacy notices it used and any laws that may apply to personal information in the records. Business contact details and order history are often handled under existing agreements, but national account or confidentiality clauses can restrict use. Counsel should review the question entity by entity.
How long should archived ERP data be kept?
Retention depends on tax, audit, contract and legal hold requirements, which vary by entity and situation. Set retention with the CFO and advisers, and avoid deleting archives by default, because closed history often has later uses in diligence, analytics and licensing.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.