Manufacturing
Selling a manufacturing business: what to do with quality and maintenance history
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
When you sell a manufacturing business, its quality and maintenance history normally goes with the business, so any plan to license that history has to be made before closing. Decide early whether to license before the sale, negotiate a carve-out right in the purchase agreement, or leave the records to the acquirer, and disclose whichever path you choose.
Key takeaways
- In a stock sale the records stay with the company you sell; in an asset sale the purchase agreement decides which records transfer and which copies the seller keeps.
- Copies a seller keeps for tax or legal purposes are usually bound by confidentiality covenants, so they are not automatically licensable.
- Licensing before closing turns the history into a contract the acquirer will see and review in diligence.
- A carve-out license right exists only if the purchase agreement grants it, and it is easiest to negotiate before the letter of intent.
- Customer-owned drawings, customer-identifying quality data and export-controlled work stay out of any license.
Who owns quality and maintenance history after the sale?#
Quality and maintenance history belongs to whoever owns the business records after closing, and that depends on the deal structure. In a stock or membership interest sale, the company itself changes hands, so its QMS, CMMS and ERP records stay with it and pass to the acquirer. In an asset sale, books and records are usually listed among the purchased assets, and the seller often keeps copies for tax, accounting and legal defense.
Retained copies are rarely free to use. Purchase agreements commonly include confidentiality covenants that restrict how a seller uses information about the business it sold, and noncompete terms can add further limits. Treat any plan to reuse retained records as a question for your M&A counsel, not an assumption.
Which records carry value beyond the sale?#
The records with value beyond the transaction are the ones that pair a production problem with a decision and an outcome. An acquirer reads them as evidence of process control and hidden liabilities. AI developers may read the same records as training and evaluation material for quality, maintenance and planning models.
| Record | Why an acquirer cares | Why an AI developer may care | Usual limit |
|---|---|---|---|
| NCRs and dispositions | Defect trends and customer exposure | Expert judgment on real defects | Customer names and part identities |
| CAPAs and 8D reports | Whether root causes were actually fixed | Structured problem-solving narratives | Customer complaints quoted verbatim |
| SPC and CMM records | Process capability on key characteristics | Measured process behavior and reactions to drift | Characteristics defined on customer drawings |
| Inspection images | Evidence of inspection discipline | Labeled examples of real defects | Customer-owned part geometry |
| Maintenance work orders and PM history | Asset condition and deferred maintenance | Failure-to-repair sequences on real equipment | Technician names and OEM manual content |
| Warranty claims and returns | Field quality and reserves | Failure modes linked to production history | End-customer personal details |
What are the options for the history: license, carve out or leave it?#
Owners selling a manufacturing business have three practical paths for its quality and maintenance history, and the right one depends on timing and on how much the acquirer cares about the records. Each path needs to be disclosed and documented, because bidders and their counsel will ask.
A fourth outcome happens by default when nobody decides: the acquirer consolidates the plant onto its own ERP and QMS, archives only what it needs, and the older history quietly disappears. If the records matter to you, raise them before the letter of intent, while every term is still open.
| Path | How it works | When it fits | What to watch |
|---|---|---|---|
| License before closing | The company licenses a defined, prepared package before the sale, and the license becomes a disclosed contract | The sale is not imminent and the team can support a review | Exclusivity, term and continuing obligations show up in diligence |
| Carve-out license right | The purchase agreement lets the seller keep a copy of a defined record set and license it | The acquirer wants the operating business, not the data rights | Must be negotiated and drafted; the acquirer may ask for limits or a share |
| Leave it to the acquirer | All records and rights transfer, and the acquirer decides what to do | The deal is close to signing or the records carry heavy customer limits | Any value in the history goes to the acquirer |
How do you build a retention and licensing schedule before a sale?#
A retention and licensing schedule for a sale lists each record family with who keeps it, how long it must stay readable and whether it could be licensed. Building it before the sale gives the acquirer a clean diligence answer and shows you exactly what you are handing over.
- List each record family by system: ERP, MES, QMS, CMMS, SPC software, shared drives and paper archives.
- Note the retention driver for each one: tax and audit, customer quality agreements, warranty terms, product liability exposure or internal policy.
- Mark who will hold each record after closing under the expected deal structure.
- Flag customer-owned content such as drawings, specifications, PPAP files and customer-supplied data.
- Flag export-controlled work and any program covered by government contract terms.
- Mark each remaining family as a licensing candidate, a candidate after preparation, or excluded.
- Review the schedule with M&A counsel before any version of it goes into the data room.
Customer ownership and confidentiality limits#
Customer ownership and confidentiality terms set the outer boundary of any license, before or after a sale. Purchase orders, supply agreements and quality agreements often state that drawings, specifications and tooling designs belong to the customer and that information exchanged is confidential. NCRs and CAPAs that quote a customer's complaint or show a customer's part can carry those obligations with them.
Preparation can often separate the manufacturer's own know-how from customer property by removing customer names, generalizing part identifiers and excluding drawings, while keeping defect descriptions, dispositions and root causes. Whether that is enough under a specific contract is a question for counsel reviewing the actual agreements, deal by deal.
Illustrative: a die caster plans ahead of a sale#
Illustrative: a fictional second-generation owner of an aluminum die casting company plans to sell to a larger strategic acquirer. The company keeps NCRs and CAPAs in a QMS, die maintenance history in a CMMS, X-ray images for porosity checks, and SPC records on critical dimensions.
Before the letter of intent, the owner builds a retention and licensing schedule. The castings are customer-designed, so drawings, dimensional characteristics and the X-ray images are excluded pending a contract review. Die maintenance history and CAPA narratives, with customer identities removed, are records the company controls.
Counsel confirms the company controls those records, and the owner licenses a prepared package of die maintenance and CAPA records before marketing the business, on a non-exclusive, time-limited basis. The executed license goes into the data room with its scope and exclusions documented, and the acquirer's counsel reviews it like any other customer contract.
How SourceX handles history ahead of a sale#
SourceX treats a pending sale as a constraint to plan around, not a reason to rush. The fit check uses metadata only, so an owner can learn whether the history is a licensing candidate without sharing files.
If the owner proceeds, the SourceX five-step transaction runs Supply, Rights, Preparation, Approval and Delivery, with the owner deciding at each one. The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, which is the document an acquirer's counsel will want to see. Because the records are licensed rather than sold outright, the company still owns them, and the acquirer inherits a clear, documented contract.
Frequently asked questions
Will licensing data lower the price an acquirer pays?
That depends on the acquirer and the terms. A time-limited, non-exclusive license with clear exclusions is usually easier for a bidder to accept than an exclusive or open-ended one. Disclose it early, document exactly what was licensed, and ask your sell-side adviser how likely bidders will read it.
Can I license the records after the sale closes?
Only if you hold the rights to do so. In most deals the records and the right to use them transfer with the business, and seller copies are restricted by confidentiality covenants. A carve-out right in the purchase agreement, or the acquirer's written consent, is usually what makes a post-closing license possible.
When should bidders hear about the history?
Early enough that it shapes the deal rather than surprising it. An existing license belongs in the data room. If you want a carve-out right, raise it before the letter of intent, while terms are still flexible, and have counsel draft it into the purchase agreement.
What if the acquirer plans to shut down our QMS and CMMS?
Ask how and when the acquirer plans to migrate, and agree in the purchase agreement or transition services agreement who preserves the full history. Even if you keep no rights to it, a complete export with attachments protects both sides on warranty claims and product liability questions.
Are paper inspection records worth keeping for a sale?
Keep them if they are the only record of inspections on product still in the field, because they may be needed for warranty or liability questions. For licensing, paper records count only once they are scanned and indexed to a job or part, which is effort to weigh against the digital records.
Does a data license change what I represent in the purchase agreement?
It may. Purchase agreements commonly include representations about material contracts, intellectual property and the handling of data, and a data license must be listed and described accurately against them. Expect questions about data use in diligence, and keep the license, its exclusions and its supporting documentation ready for the acquirer's counsel.
Related resources
- InsightCan roofing contractors sell their data to AI companies?
- InsightCustomer complaint logs: what AI learns from how you resolve them
- InsightAcquiring a company that already licenses its data: what to check
- SolutionData monetization: earning revenue from data you already have
- IndustryHealthcare administration data
- QuestionDo AI companies buy private business data?
See if your company qualifies
A short company assessment. No data uploads are needed.