Private equity and portfolios
Legacy ERPs from acquired plants: archive, migrate or license?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A legacy ERP from an acquired plant rarely needs one answer: migrate open data, archive closed history read-only, and assess a vetted subset of quality and maintenance records for licensing. Decide before the server or transition services agreement ends, and check rights first, since carve-out terms, customer-owned designs and export controls limit what can be kept or licensed.
Key takeaways
- Archive, migrate and license are not exclusive choices; most plant ERPs end with a mix of all three.
- Migrate what the plant needs to run after cutover, and archive the rest in full before access ends.
- A carve-out plant may depend on the seller's ERP under a transition services agreement, so the export deadline can be set by someone else.
- Customer-owned drawings and ITAR- or EAR-controlled jobs are excluded from licensing and should be segregated while the archive is built.
- NCRs, CAPAs, maintenance work orders and quote histories are the plant records most worth keeping beyond compliance.
What are the options for an acquired plant's legacy ERP?#
An acquired plant's legacy ERP has three options: migrate its data into the group's system, archive it read-only, or license a prepared subset of its records to AI developers. The options are not exclusive. A common outcome is to migrate open orders, routings and active part masters, archive closed history, and assess the strongest record families for licensing.
The decision usually lands on the group COO or an operating partner during integration, when the pressure is to retire the old system and stop paying for it. Plants bought as add-ons often run older on-premise ERPs, with quality records in a separate QMS or spreadsheets and maintenance in a standalone CMMS, so the question covers more than one database.
The decision table: archive, migrate or license#
The decision table compares the three options on when each fits, what each requires and what goes wrong if it is skipped. Most plants apply all three to different parts of the same system.
Licensing is the option integration plans usually leave out, because it is not part of a standard cutover checklist. Assessing it early is light work: the first review covers which record families exist, how many years are accessible and what restrictions apply, without moving any files.
| Option | Fits when | Requires | Risk if skipped |
|---|---|---|---|
| Migrate | Data is open or active: orders, purchase orders, routings, BOMs, part masters, open quality holds | Field mapping, a part number crosswalk and validation against live plant operations | The plant cannot build or ship cleanly after cutover |
| Archive | Data is closed but must be retained or may be useful later | Full table exports, notes and attachments, schema documentation and read-only storage | History disappears when the server or license ends |
| License | Records are company-owned, linked to outcomes and free of customer or export restrictions | Rights review, privacy preparation and supplier approval | Records with possible outside value are deleted before anyone has assessed them |
Rights checks to run before choosing an option#
Rights checks decide which plant records can be migrated, kept or licensed, and the answers differ between a stock purchase, an asset purchase and a carve-out. A carve-out plant may still run on the seller's ERP under a transition services agreement, in which case the seller controls access and effectively sets the export deadline.
Record each answer per plant. Counsel assesses the hard cases, such as whether inspection data on a customer's part is the plant's own record or the customer's confidential information.
- Purchase agreement: which records, systems and contracts transferred, and whether the seller kept copies or rights in shared data.
- Transition services agreement: the end date for system access and which extracts the seller must provide, in what format.
- Customer agreements: ownership of drawings, specifications and tooling, plus quality agreements and purchase order terms that limit use of part and inspection data or set how long quality records must be kept.
- Export controls: jobs involving ITAR- or EAR-controlled technical data are segregated, excluded from licensing and kept in an archive area with access limited to authorized staff.
- ERP, QMS and CMMS vendor terms: export rights, read-only licenses and access after termination.
- Employee and labor records: personnel data in HR, time and attendance modules is handled under applicable law and any labor agreements.
What does a plant archive need beyond the ERP tables?#
A plant archive needs the traceability, quality and maintenance records that sit around the ERP, because warranty claims, customer audits and field failures ask for them long after cutover. Many of these records live outside the ERP database, so a clean table export can still leave the most important history behind.
Ask the quality manager and the maintenance lead, not only IT, where each item lives. Paper travelers and inspection sheets scanned to a shared drive are easy to miss and hard to recover once the drive is wiped.
- Lot and serial genealogy linking material receipts, work orders, inspections and shipments, so a defective lot can still be traced to customers.
- PPAP packages, first article inspections and control plans for parts the plant still supplies or may have to support under warranty.
- Gauge calibration records, which show that the inspection results in the archive were taken with controlled equipment.
- Engineering change orders and routing revisions, so the archive shows which process produced a given lot.
- The CMMS asset register, work order history and preventive maintenance schedules, with equipment IDs that still match the machines on the floor.
- MES or machine logs and scanned travelers, where they exist, tagged to the job and part number they belong to.
Which plant records are worth keeping beyond compliance?#
Plant records worth keeping beyond compliance are the ones that capture decisions and outcomes: why a part failed, what the team changed and whether the fix held. Minimum retention comes from customer quality agreements, the plant's quality system, tax rules and product liability exposure, which the quality lead and counsel set together; business value decides what else deserves a place in the archive.
These same records interest AI developers building quality, maintenance and production planning tools, which is why the license option deserves a look before anyone prunes the archive. Records tied to customer-owned designs stay segregated regardless of their value.
| Record family | Typical source | Why it has value |
|---|---|---|
| Nonconformance reports and MRB dispositions | QMS, ERP quality module, spreadsheets | Links a defect to a disposition decision and its cost |
| Corrective and preventive actions | QMS or CAPA logs | Shows root cause analysis and whether the fix held |
| Maintenance work orders | CMMS or ERP maintenance module | Connects equipment symptoms to repairs and downtime |
| Quote-to-order history | ERP quotes, estimating tools, CRM | Shows how jobs were priced, revised, won or lost |
| Production schedule changes | ERP or MES scheduling logs | Records how planners handled shortages and rush orders |
| Supplier corrective actions | QMS and purchasing records | Tracks supplier quality problems through to resolution |
Illustrative: a machining plant on an aging on-premise ERP#
Illustrative: a fictional industrial holding group acquires a precision machining plant that runs an aging on-premise ERP, keeps NCRs and CAPAs in a separate QMS database and logs maintenance in a standalone CMMS. The group runs a cloud ERP and wants the plant cut over and the old server retired.
The group COO migrates open orders, routings, active part masters and open quality holds. Closed jobs, invoices and the full QMS and CMMS histories go to a read-only archive with a part number crosswalk. The rights review finds that some jobs used customer-owned drawings and a handful were export controlled, so those job folders are tagged and kept out of any licensing scope.
The remaining NCR, CAPA and maintenance histories link defects and breakdowns to root causes and fixes across many years. Lot genealogy and calibration records are exported from the QMS so that open warranty claims can still be answered. The group assesses the quality and maintenance histories for licensing, and the plant manager signs off that no daily tool still depends on the old server before it is retired.
What order should the cutover follow before the plant server is retired?#
The cutover for a legacy plant ERP should run from system inventory to rights to export, with server retirement last. Letting an IT contract date or a TSA end date drive the order is how plants lose history they later need for warranty claims, customer audits or a sale.
Give one person ownership of the whole sequence, usually the group's integration lead, and have finance and the plant manager confirm each step. The plant manager's sign-off matters most, because only the plant knows which inspection spreadsheet or tooling log is still used every shift.
- Map every system the plant touches: ERP, QMS, CMMS, MES, scheduling spreadsheets and shared drives, with who uses each one daily.
- Pin the hard dates, such as the TSA end date, the vendor renewal and the server's end of support; the earliest one sets the plan.
- Run the rights checks and tag restricted job folders, such as customer-owned designs and export-controlled work.
- Cut over open orders, routings, part masters and open quality holds, and run the plant on the group system through a full month-end close.
- Export the full history, including the traceability and quality records above, check it against the live system and store it read-only with the part number crosswalk.
- Run a metadata-only licensing assessment on the archived NCR, CAPA, maintenance and quote histories.
- Retire the server and cancel licenses only after the integration lead, finance and the plant manager sign off.
How SourceX approaches legacy plant archives#
SourceX assesses the license option without asking for files: the fit check covers systems, record families, years of history and known restrictions. Archives stay in the group's own storage or ship on encrypted drives, because SourceX does not host multi-terabyte datasets.
A plant archive that moves forward is handled through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Customer-owned designs and export-controlled work are excluded, personal and confidential details are removed during preparation, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization for the plant's records.
Frequently asked questions
Can we keep the legacy ERP running read-only instead of exporting?
Sometimes, if the vendor offers a read-only license and the server is still supported. That defers the problem rather than solving it: hardware ages, the people who understand the system leave and access can lapse at renewal. An exported, documented archive is easier to search, govern and hand to a buyer.
Who owns quality data about a customer's parts?
Often the plant owns its own inspection records, NCRs and CAPAs, but customer quality agreements and purchase order terms can claim rights in, or restrict use of, data about their parts, specifications and drawings. Read those documents, and treat anything tied to customer-owned designs as excluded from licensing until counsel confirms otherwise.
Can licensing plant records affect customer relationships?
It can, if customer material is included or a customer learns of it unexpectedly. The risk is managed by removing customer-identifying details and customer-owned material, following confidentiality terms in quality agreements and purchase orders, and deciding early whether any key customer should be told. A licensed package focuses on how the plant handled defects, maintenance and planning, not on who its customers were.
What if the seller still hosts the plant's data?
Then the transition services agreement governs access and extracts. Request full table exports, notes and attachments early, confirm the format in writing and verify what you receive while the seller's team can still answer questions. Shared databases may need the seller's help to separate the plant's records from its own.
Is an older ERP's data too messy to be useful?
Messy structure matters less than linked content. Older systems often hold years of free-text notes on defects, repairs and order changes. If records connect an issue to a decision and an outcome, they can be prepared and documented even when field formats are inconsistent.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.