Software companies
Does an acquirer inherit your data licensing agreements?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
An acquirer usually inherits your data licensing agreements in a stock purchase, because the contracting company stays the same, unless a change of control clause gives the other party a consent or termination right. In an asset sale, each license must be assigned, and anti-assignment clauses usually require consent. Mergers fall in between and turn on drafting and governing law.
Key takeaways
- Deal structure sets the starting point: stock sales keep contracts in place, asset sales require assignment.
- Change of control and anti-assignment clauses decide whether the counterparty can block the transfer or walk away.
- An affiliates definition can quietly widen who may use licensed data after a licensee is acquired.
- Licensors often negotiate a termination right if the licensee is acquired by a competitor.
Short answer: deal structure decides the starting point#
Whether an acquirer inherits a data licensing agreement depends first on deal structure and then on two clauses: assignment and change of control. In a stock purchase the company that signed the license keeps existing under new ownership, so the agreement continues unless a clause says otherwise.
In an asset purchase, the buyer takes only the contracts assigned to it, and most licenses prohibit assignment without consent. Where a license is silent, some courts treat licenses of intellectual property as personal to the licensee, so a transfer without consent can still be challenged. Mergers sit in between: whether a merger counts as an assignment can depend on the merger form, the governing law and the exact wording.
The question runs in both directions. A software company may be the licensor whose own business is being sold, or the licensor whose licensee, an AI developer, is being acquired. The protections differ, so each case gets its own section below.
How each deal structure treats an existing data license#
Each deal structure produces a different default for an existing data license. Drafting can override any of them, which is why the clause column matters more than the effect column.
Many licenses define assignment to include a change of control. That single definition turns a stock purchase, which would otherwise leave the contract untouched, into an event that needs the counterparty's consent.
| Deal structure | Default effect on the license | Clause to check first |
|---|---|---|
| Stock purchase | Contract stays with the same entity | Change of control: notice, consent or termination rights |
| Reverse triangular merger | Target survives; often treated like a stock purchase | Change of control and any operation of law language |
| Forward merger into the acquirer | Target ceases to exist; may be treated as an assignment | Anti-assignment clause and governing law |
| Asset purchase | License must be assigned to the buyer | Anti-assignment and consent requirements |
| Carve-out sale of a product line | Only licenses tied to the transferred assets move | Scope definitions and partial assignment rights |
The clauses that decide what happens#
Seven clauses decide what happens to a data license in a sale. Read them together, because a permissive assignment clause can be undercut by a strict change of control clause in the same agreement.
- Assignment: whether either party may assign without consent, and whether consent may not be unreasonably withheld.
- Operation of law: whether transfers by merger or by operation of law count as assignments.
- Change of control: whether a sale of the company triggers notice, consent or a termination right, and how control is defined.
- Successors and assigns: confirms that permitted successors take both the benefits and the obligations.
- Affiliates: who besides the named licensee may use the data, and whether that group grows after an acquisition.
- Exclusivity: whether an exclusive grant survives a sale and binds the acquirer's other businesses.
- Deletion and survival: which obligations continue if the license ends because of the transaction.
When your licensee is the one being acquired#
When the licensee is acquired, the licensor's risk is that its records end up with a new owner it never chose, possibly a competitor. If the license lets the licensee share data with affiliates, an acquisition can add a long list of new affiliates overnight.
Licensors commonly protect themselves with a termination right on a change of control of the licensee, an affiliates definition fixed at signing, and an obligation to delete licensed data when the license ends. Models already trained are harder to address, because deleting the data does not remove what a model learned, so the license should state plainly what happens to them.
Notice obligations help too. A clause requiring the licensee to tell the licensor promptly about a pending change of control gives the licensor time to decide whether to consent, renegotiate or exit.
When your own company is being sold#
When the software company that licensed its records is being sold, every data license becomes a diligence item. The acquirer will ask for a schedule listing scope, term, exclusivity, remaining delivery obligations and any restriction on the company's future use of its own records.
Exclusive licenses draw the most attention, because they can limit what the combined business does with records it now owns. Non-exclusive, time-limited licenses with clear deletion terms are easier to carry through a sale. If the license promises refreshes, the acquirer will want to know who performs them, from which systems, and whether those systems survive the integration.
Prepare the schedule before the sale process starts. Pull each signed license, the delivery records and any consent letters into one folder, so the answers come from documents rather than from memory during a compressed diligence window.
Protections to negotiate before any sale is on the table#
Transfer protections are easiest to negotiate at signing, when neither side is under deal pressure. Licensors and licensees want different protections, and a balanced license usually gives each side some of what it asks for.
Keep the protections proportionate to the license. A short, non-exclusive license of redacted engineering records needs less machinery than a multi-year exclusive grant, and over-engineered transfer terms can make the license itself harder to sign.
| Concern | Protection | What it prevents |
|---|---|---|
| Licensee acquired by a competitor | Termination right on the licensee's change of control | Your records feeding a rival's products |
| Affiliate creep | Affiliates defined as of the signing date | New owners' businesses gaining use rights |
| Your own sale blocked | Free assignment to a successor of your whole business | A licensee veto over your exit |
| Trained models in new hands | Stated rules for models after termination or transfer | Disputes over what deletion covers |
| Surprise transfers | Prompt notice of any pending change of control | Learning of a transfer after it closes |
Illustrative: a construction estimating software company is acquired#
Illustrative: a fictional construction estimating software company licensed redacted issue histories and code reviews to an AI developer under a non-exclusive license with a refresh obligation. A larger software group agrees to buy the company through a stock purchase.
Counsel finds that the license defines assignment to include a change of control, so the licensee's consent is required even though the contracting entity does not change. Because the license is non-exclusive and the licensee wants the refreshes to continue, consent is requested early and given. The acquirer confirms it will keep running the refreshes from the same issue tracker and repositories, and the disclosure schedule lists the license with its deletion terms.
How SourceX records transfer terms#
SourceX records each license's assignment, change of control and affiliate terms in the SourceX Evidence Packet, next to provenance, permitted use, the privacy record and release authorization. That gives a future acquirer and the original parties one record of who may use the data and within which limits.
Because the supplier approves every step of the SourceX five-step transaction, a later consent request can be checked against what was actually approved rather than reconstructed from email.
Frequently asked questions
Does a change of control clause apply if only a minority stake is sold?
Usually not, but the definition decides. Many clauses define control as majority voting power or the ability to direct management. Some include board control or transfers across a series of transactions, so a staged sale can trigger them. Read the definition rather than assuming.
Can the licensee assign our license to its acquirer without asking?
Only if the license allows it. Many data licenses prohibit assignment without consent but permit assignment to a successor of the entire business. If you want a veto, say so expressly and cover mergers and transfers by operation of law.
What happens to models trained before the acquisition?
That depends on the license. Some let trained models survive termination while requiring deletion of the underlying data; others restrict use of models in new hands. Without clear wording, expect a dispute, so settle the point at signing.
Will a buyer of our company want to cancel our data licenses?
Some buyers prefer to remove exclusive or long-term licenses that limit their plans, while others value the revenue. Non-exclusive licenses with clear terms rarely become a sticking point. Disclose them early so they are priced in rather than discovered late in diligence.
Do these rules differ by state?
Yes. Whether a merger counts as an assignment, and how anti-assignment clauses are enforced, can depend on the contract's governing law and the states where the companies are organized. Counsel should review the specific agreement under its chosen law.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.