Home/Services/License Assignment
For buyers and deal teams

Software license assignment in M&A

Software license assignment in M&A decides which of a target's licenses move with the deal, which need a publisher's consent, and which the structure leaves behind, before those answers cost you after close.

Software license assignment in M&A is the question of whether the rights a target depends on actually transfer when the deal closes. A license is a contract, and contracts carry terms on assignment. Change of control and anti assignment clauses can trigger consent, termination, or repricing, and the deal structure, whether stock purchase, asset purchase, merger, or carve out, changes which clauses bite. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and assignment is where a buyer discovers, too late, that a critical license did not come with the company.

Software licenses by assignment outcome in a typical dealBar chart showing the share of a target's licenses that transfer freely, that require consent, and that are blocked or repriceable on assignment.0255075100MostTransferfreelySomeConsentrequiredFewBlocked orrepriced
Illustrative split of a target's software licenses by assignment outcome, from those that transfer freely to those that are blocked or repriced. Directional, varies by estate.

What software license assignment in M&A really involves

Assignment is the transfer of a contractual right from one party to another. In a deal, the buyer assumes that the target's software rights will simply come along with the business. Many do. But software agreements frequently restrict assignment precisely to control what happens in a transaction. An anti assignment clause may prohibit transfer without the publisher's written consent. A change of control clause may treat the deal itself as an assignment even when no contract is formally handed over. Until each agreement is read against the deal, the buyer does not actually know which rights it is acquiring.

The deal structure is decisive. In a stock purchase, the target entity remains the contracting party and only its ownership changes, which often avoids triggering an assignment clause, though a change of control clause may still apply. In an asset purchase, the contracts are assigned to a different legal entity, which typically engages anti assignment language and the consent it requires. A merger and a carve out each create distinct assignment questions. Reading every material agreement against the specific structure is what turns assumption into knowledge.

How deal structure affects software license assignment
Deal structureEffect on license assignment
Stock purchaseEntity unchanged, assignment often not triggered, change of control clause may still apply
Asset purchaseContracts assigned to a new entity, anti assignment clauses and consent commonly engaged
MergerSurviving entity inherits contracts, change of control provisions reviewed case by case
Carve outRights must be separated and reassigned, consent and new contracts frequently required

Why a missed assignment becomes the buyer's problem

When a license does not assign cleanly, the consequence lands on the buyer. The business may continue using software it no longer has the right to use, which is unlicensed usage a publisher can audit and charge for. Or the publisher may require consent and use that moment to demand a new commitment, a price uplift, or a renewal on its terms. Either way, the cost arrives after close, when the buyer has the least leverage and the most need. The seller, having completed the deal, has little incentive to help resolve it.

This is why assignment is reviewed before signing. As of June 2026, public reporting on inherited and disputed licensing, including SAP pursuing AB InBev for a figure in the region of 600 million dollars, illustrates how a licensing position grows once ownership changes and the rights were never properly transferred. A buyer who knows before signing which licenses need consent can seek that consent in advance, structure the deal to avoid the trigger, or price the risk into the offer and the indemnity. We provide commercial and licensing advisory, not legal advice, and recommend your own counsel for the interpretation of any contract term or clause.

How we assess assignment for the deal team

We inventory the target's material software agreements and read each one for assignment, anti assignment, and change of control language. We classify every agreement against the specific deal structure as freely assignable, consent required, or blocked, and we flag any that allow termination or repricing on the transaction. We rank the findings so the deal team focuses on the few licenses that could disrupt operations or move the price, and we recommend how to handle each: a consent sought early, a structural adjustment, or a protection written into the deal terms. Because we are independent and paid only by the acquirer, the assessment serves the buyer, not the publisher consent process or the seller timeline.

The assessment also separates the licenses that matter from the ones that do not. A small utility that assigns with a routine consent is not worth deal attention, while a single business critical platform with a termination right can stall the entire integration. We weight the findings by operational dependence and by cost so the deal team spends its limited time on the agreements that can actually move the deal or disrupt the business after close.

Key takeaways

  • A software license is a contract, and contracts carry terms that govern assignment.
  • Anti assignment and change of control clauses can require consent, block transfer, or trigger repricing.
  • Deal structure decides the assignment question: stock, asset, merger, and carve out each differ.
  • A missed assignment becomes the buyer's problem after close, when leverage is lowest.

Recommendations for buyers

  1. Inventory and read every material agreement. Assumption is not knowledge until each contract is reviewed.
  2. Classify against the deal structure. The same license assigns differently in a stock versus asset deal.
  3. Seek consent on your timeline. Approach publishers before close, not under post deal pressure.
  4. Write protections into the terms. Convert assignment risk into reps, warranties, or an indemnity.

Pair this with our change of control review service and the change of control pillar. In practice: a change of control clause renegotiated before close and a cross border acquirer that mapped hidden licensing gaps.

Frequently asked questions

What is software license assignment in M&A?
It is the question of whether a target's software rights transfer to the buyer when the deal closes, governed by assignment, anti assignment, and change of control clauses in each agreement.
Do all software licenses transfer in an acquisition?
No. Many transfer freely, but some require the publisher's consent and some are blocked or repriceable. Each agreement must be read against the specific deal structure.
How does a stock purchase differ from an asset purchase for assignment?
In a stock purchase the contracting entity is unchanged, so assignment clauses often do not trigger. In an asset purchase contracts are assigned to a new entity, which commonly engages anti assignment language.
What is the risk of a missed assignment?
The business may run software it no longer has the right to use, exposing it to a publisher audit, or the publisher may demand a new commitment when consent is sought after close.
Are you independent of software publishers?
Yes. We are paid only by the acquirer and hold no affiliation with any publisher or reseller.

Want to know which licenses actually transfer with the deal?

We assess software license assignment against your deal structure and flag the rights that need consent before close. Tell us about the deal and we respond within one business day.

Book a confidential call