Asset sale vs stock sale: what happens to data rights and existing licenses?

What changes hands in each structure?#

In a stock sale the buyer acquires the shares of the company, while in an asset sale it acquires selected assets and assumes selected liabilities. That single difference decides how records, and the contracts around them, move.

In a stock sale, the entity that owns the CRM, the help desk, the ERP and every contract stays exactly as it was; only its owner changes. In an asset sale, a buyer entity takes title to the assets listed in the purchase agreement and steps into the contracts validly assigned to it. Mergers sit between the two: in a reverse triangular merger the target survives, so its contracts usually stay put much as in a stock sale, but some contracts treat any merger or change of control as an assignment, and courts have not read every merger form the same way.

Asset sale vs stock sale for data rights, side by side#

The two structures differ on ownership, consents and what the seller keeps. The table shows the general pattern; the purchase agreement and each underlying contract decide the specific outcome.

What happens to data licenses in a stock sale?#

Data licenses in a stock sale stay in force because the contracting company has not changed, but change-of-control clauses can still give the other side choices. A vendor may be allowed to terminate or reprice a subscription when the customer is acquired, and an AI developer holding a license from the target may have negotiated rights if the supplier comes under a competitor's control.

The new owner also inherits every obligation the company already carries. Exclusivity it granted, deletion audits it agreed to, revenue it must share and warranties it gave about the delivered records all remain with the entity after closing.

Buyers therefore ask for a schedule of every outbound data license in the purchase agreement, with representations that the list is complete. Sellers who kept clean license files and delivery records answer that request quickly; those who did not tend to find the gaps during diligence.

Do existing data licenses transfer in an asset sale?#

Existing data licenses transfer in an asset sale only if they are assigned to the buyer, and many licenses restrict assignment without the other party's consent. Both directions matter: licenses you granted to AI developers, and licenses you hold from vendors and partners.

Inbound terms deserve the same attention. Where a contract is silent, many US courts have held that a non-exclusive patent or copyright license is personal to the licensee and cannot be assigned without the licensor's consent, so silence is not permission. A SaaS subscription may not be assignable either, and export rights under it may end with the subscription, so plan exports before closing rather than after.

• 1Anti-assignment clauses, and whether they treat a sale of substantially all assets as an assignment.
• 2Change-of-control clauses that let the counterparty terminate or renegotiate.
• 3Exclusivity granted to a licensee, which binds whoever holds the records if the license transfers.
• 4Deletion and return obligations that termination of the license may trigger.
• 5Payment terms, including who receives fees that fall due after closing.

Which privacy promises travel with the data?#

Privacy promises generally travel with personal information when it moves to a new owner. A buyer of customer records is commonly expected to honor the privacy notice under which they were collected, and material changes may require notice and, under some laws, consent.

Several state privacy laws, including California's, treat a transfer of personal information as part of a merger or acquisition differently from an ordinary sale, on the basis that the acquirer keeps using it consistently with the promises made at collection. Regulators press the same point in distressed sales: in 2015 the FTC recommended that RadioShack's customer data go only to a buyer bound by RadioShack's privacy policy, and in 2025 the FTC chairman wrote that any purchaser of 23andMe's assets should agree to be bound by its privacy policies.

Check whether the seller's privacy notice mentions transfers in a merger, acquisition or sale of assets. Where it is silent or restrictive, both the transfer of personal information and any later licensing need careful review. Employee records add their own layer through handbooks, workplace communication policies and state laws that may apply.

De-identifying records before a later license reduces how much of this the buyer carries forward, but it does not remove the obligations attached to the original records still held in the acquired systems.

What should an operating partner check before licensing acquired records?#

An operating partner should confirm that the platform actually holds clear rights to an acquired company's records before offering any of them for license. The answer sits in the deal documents, not in the systems.

• 1The purchase agreement's asset schedule: are the relevant records, systems and intellectual property listed?
• 2Representations about data, privacy compliance and existing licenses, and how long they survive.
• 3Transition services terms covering access to systems that stayed with the seller.
• 4Licenses the seller granted before closing, including any exclusivity.
• 5Customer, vendor and employee terms that came across with the records.
• 6Credit agreement and investor consents that apply to licensing intellectual property.

Illustrative: a roofing platform with one stock deal and one asset deal#

Illustrative: a fictional private equity-backed commercial roofing platform has completed two add-ons. The first was a stock purchase, so the company kept its entity, its Procore projects, its estimating history and every customer contract. The second was an asset purchase from a retiring founder, with project records exported to the platform at closing.

When an AI developer asks about inspection, estimate and warranty-claim histories, the operating partner starts with the stock-acquired company. Its records, contracts and privacy notice are unchanged, and the only open question is whether any customer contract has change-of-control or data-use terms.

For the asset-acquired company, counsel finds that the asset schedule covered project files but not the warranty claims database, which stayed with the seller's entity. The platform obtains a written assignment of those records from the seller before including them in any later package.

How SourceX handles acquired records#

SourceX checks chain of title in Rights, the second step of the SourceX five-step transaction, before any preparation work begins. For an acquired company that means reading the transaction structure, the asset schedule and any licenses that came with the records.

What the review finds is written into the provenance and licensing rights sections of the SourceX Evidence Packet. A later acquirer of the platform can then follow how the supplier came to hold the records without rebuilding the history from deal files.