Skip to content

Logistics and distribution

Asset vs stock deals: who gets the data when a distributor or 3PL is sold

By SourceX Editorial · Reviewed by Noah Loul ·

Short answer

When a distributor or 3PL is sold, who gets the data depends on the deal structure. In a stock deal records, contracts and data obligations stay with the same company under new owners. In an asset deal only the records the purchase agreement lists transfer, many contracts need consent to assign, and customer privacy promises can limit what moves.

Key takeaways

  • A stock purchase changes the owner but not the entity, so records and obligations stay where they are.
  • An asset purchase transfers only what the agreement lists, so books, records and system data need express treatment.
  • Client contracts in an asset deal often need consent to assign; in a stock deal, change-of-control clauses may still apply.
  • Privacy notices and contract promises about customer data can follow that data to the buyer.
  • Sellers usually keep copies of some records after an asset sale for tax and legal purposes, under limits.

Who gets the data in each deal structure?#

The data follows the entity in a stock deal and follows the purchase agreement in an asset deal. When a buyer acquires the shares or membership interests of a distributor or 3PL, the company that created and holds the records keeps existing, so its WMS history, ERP records and contracts stay put, together with its obligations.

When a buyer acquires assets instead, the seller entity remains with its former owners and transfers a defined list of assets. Records move only if the asset purchase agreement includes them, usually through definitions of books and records, customer lists or intellectual property. Anything not listed stays behind.

Mergers and other structures have rules of their own. This explainer covers the two most common forms; counsel will advise which structure fits a given deal.

Side-by-side comparison of what transfers#

The comparison below summarizes how the most common data questions usually play out. Individual agreements can change any row, so treat it as a map of issues to raise, not a set of answers.

Side-by-side comparison of what transfers
IssueStock purchaseAsset purchase
Ownership of recordsStays with the company, which the buyer now controlsOnly records listed as purchased assets transfer
Customer and client contractsRemain in place; change-of-control clauses may give counterparties rightsMust be assigned; many require counterparty consent
Software and SaaS licensesUsually stay; some vendor terms address change of controlTypically need vendor consent or a new agreement
EDI trading partner setupsStay with the company; partners may need notice of new ownershipNeed new agreements or setup under the buyer
Privacy commitments to customersStay with the company and keep binding itMay limit what customer data transfers and how the buyer uses it
Existing data licensesContinue as company contractsTransfer only if assigned; the seller may remain bound
Liabilities from past data useGenerally stay with the companyGenerally stay with the seller unless assumed, subject to successor liability rules
Seller access after closingNone unless agreedSeller often keeps copies for tax, legal and wind-down needs

How an asset purchase agreement defines the data#

An asset purchase agreement defines the data through its lists of purchased and excluded assets. Look for definitions of books and records, customer lists, supplier lists, business information and intellectual property, and check that they reach electronic records in the WMS, TMS and ERP rather than only paper files.

Exclusions matter just as much. Sellers commonly keep tax records, records about excluded assets, privileged communications and records they must retain by law, and the agreement may let the seller keep copies of transferred records for those purposes under a confidentiality covenant.

  • Confirm that purchased records include system data and archives, not just current files.
  • Check whether history from former customers is included or excluded.
  • Look for a covenant limiting how the seller may use retained copies after closing.
  • Note any transition services arrangement in which the seller keeps running systems for a period.
  • Agree who receives system exports at closing, and in what format.

Customer lists, personal data and privacy carry-over#

Customer lists in an asset sale are often the most valuable records and the most constrained. Many privacy notices say that customer data may transfer in a merger or sale of assets, and that wording matters; where a notice made narrower promises, those promises may limit what the buyer receives or how it may use the data.

For B2B distributors and 3PLs, much of the customer data is business contact information, but consumer delivery addresses, ship-to records and driver or employee files can be personal information. State privacy laws may apply to the transfer depending on the facts, and those questions are assessed deal by deal with counsel.

A 3PL's client data adds a further layer. The 3PL may not own its clients' records at all, so it can pass them on only as far as each client agreement allows, and a contract that is not assigned can trigger return-or-destroy obligations.

Stock deals still carry data questions#

A stock deal avoids most assignment problems but not every data question. Change-of-control clauses in client agreements and software licenses can give the counterparty a right to terminate, renegotiate or receive notice, and obligations stay too: past use of client data, existing licenses and privacy commitments keep binding the company the buyer now owns.

That is why buyers in stock deals ask for representations about data. Expect to confirm that the company has complied with its contracts and privacy notices, holds the rights to use its records as it does, and has disclosed every data license. Documentation that supports those answers is worth assembling before the letter of intent.

Illustrative: a distributor sells one division#

Illustrative: a fictional industrial distributor runs a bearings and power transmission division alongside its core MRO business, all on one Epicor instance. It agrees to sell the division to a strategic buyer through an asset sale, while the rest of the company stays with the founding family.

Counsel defines purchased records as the division's customer accounts, order history, quotes and supplier records, extracted from the shared ERP by division code. The family company keeps copies for tax and warranty purposes under a confidentiality covenant. Customers on signed supply agreements receive consent requests, while transactional customers move to the buyer's terms going forward. The company had earlier licensed de-identified order exception records from both divisions; that license stays with the seller, and the agreement records that division records delivered before closing remain within it.

Data questions to settle early in either structure#

Data questions are easier to settle at the letter-of-intent stage than in the final week before closing. Raising them early lets counsel draft definitions that match how the business actually stores its records.

  • Which systems and archives hold the records, and which entity owns each subscription.
  • Whether history from former clients and customers transfers, stays or is deleted.
  • Which consents are conditions to closing and which can follow afterward.
  • How existing data licenses, vendor data-sharing terms and benchmark programs are disclosed and treated.
  • What copies the seller keeps, for which purposes and under what confidentiality terms.

How SourceX approaches records after a sale#

SourceX treats the supplier as the entity that holds the records and the rights at the time of the license. In the Rights stage of the SourceX five-step transaction, a company that was acquired, sold a division or bought assets from another business maps which records it holds, under which agreement, and with which limits.

That analysis is recorded in the SourceX Evidence Packet under provenance and licensing rights, so a later acquirer, lender or buyer of the data can see how each package was supported.

Frequently asked questions

Can a seller license data after an asset sale?

Only records it still holds and is permitted to use. Retained copies are often limited to tax, legal and wind-down purposes, and a confidentiality covenant may bar other uses. Records that transferred generally belong to the buyer. Counsel should review the purchase agreement before any license of retained records.

Does the buyer inherit a data license the seller signed?

In a stock deal, yes, because the license is a company contract. In an asset deal, only if the license is assigned to the buyer, which may need the licensee's consent. The purchase agreement should address existing licenses expressly so neither side is surprised after closing.

Are customer lists treated differently from other records?

Often. Customer lists can be valuable trade secrets and can contain personal information, so purchase agreements usually name them specifically, and privacy notices may affect their transfer. Non-solicitation and non-compete terms in the deal often relate to them as well.

What happens to data during a transition services period?

The seller may keep running systems for the buyer for an agreed time. The agreement should say who owns records created during that period, how they are kept apart from the seller's own data and when they are handed over. Confidentiality and security terms are a standard part of these arrangements.

Who keeps records needed for old tax audits after an asset sale?

Usually the seller keeps or retains access to records it needs for its own tax filings and audits, and the agreement often gives each side access to the other's records for that purpose. Check the access and cooperation clauses, because the systems holding those records may now belong to the buyer.

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify