The single structural choice that decides how much software consent work a deal carries, and why the same estate can be low risk or high risk depending on it.
The choice between a stock vs asset purchase is one of the most important structural decisions in a deal, and it has a direct effect on software licensing that is often overlooked. In a stock vs asset purchase comparison, the key software question is which assignment and change of control clauses are triggered, because that determines how much publisher consent the transaction will require. A stock purchase generally keeps the licensed entity intact and reduces assignment risk, while an asset purchase moves contracts between entities and engages anti assignment language across the estate. The same portfolio of licenses can therefore be low risk or high risk depending purely on the structure chosen.
In a stock purchase, the buyer acquires the shares of the target company, and the company itself, including its contracts, continues to exist. Because the licensed entity does not change, anti assignment clauses, which respond to a license moving to a different entity, are generally not engaged. What can still apply is a change of control clause, because the ownership of the entity has changed even though the entity has not. The risk in a stock deal is therefore concentrated in change of control language and in any clause that addresses a change in ultimate ownership.
In an asset purchase, the buyer acquires specific assets and contracts, which are assigned from the seller entity to the buyer entity. Every software license in scope is being transferred, so anti assignment clauses are engaged across the estate. This makes an asset deal far more consent heavy, because each contract that requires consent to assign becomes a gating item for that system. The structural difference is not a nuance, it is the single biggest driver of how much software consent work a deal carries, and it should be modeled before the structure is fixed rather than discovered afterward. The detail of anti assignment language is set out in anti assignment clauses in software contracts.
A merger is a third structure that can carry features of both. Depending on which entity survives and on the precise wording, a merger can be treated as a change of control, as an assignment by operation of law, or as both. Some clauses are drafted specifically to catch a merger, including language that treats a merger as a deemed assignment regardless of which entity survives. This means a merger cannot be assumed to be clean simply because no contract is physically moved, and each agreement has to be read against the merger mechanics. The way a merger can breach a license is covered in how a merger can breach a software license, and the broader principle that structure can be used to limit problems is set out in how deal structure limits assignment problems.
| Structure | Anti assignment | Change of control | Consent burden |
|---|---|---|---|
| Stock purchase | Generally not triggered | Often triggered | Lower |
| Asset purchase | Triggered across estate | May also apply | Higher |
| Merger | May be deemed assignment | Often triggered | Variable, read wording |
| Carve out into new entity | Triggered, new entity needs contracts | May apply to parent | High |
Deal structure is usually decided on tax, liability, and accounting grounds, and software licensing rarely gets a seat at that table. That is a mistake when the software estate is large, because the consent burden of an asset deal can carry real cost and timeline risk that should weigh in the structure choice. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. A structure chosen without the software clauses in view can convert a manageable estate into a consent heavy programme, or expose the buyer to a clause that could have been avoided. The public record shows how large inherited licensing exposure can become, with SAP reportedly pursuing Anheuser Busch InBev for around 600 million dollars and Diageo for around 60 million pounds, both as reported and as of June 2026. Bringing the software clause analysis into the structure decision, with counsel on the legal interpretation and an advisor on the commercial measurement, lets the buyer choose with the exposure quantified rather than assumed.
Consider a target running a typical mid market software estate: an enterprise resource planning system, a database platform underneath it, a productivity and collaboration suite, a customer relationship system, and a handful of specialist applications. Under a stock purchase, the licensed entity is unchanged, so most of these contracts continue without an assignment, and the buyer focus narrows to whether any agreement contains a broad change of control trigger. Under an asset purchase, every one of those contracts is assigned, so each has to be checked for anti assignment language and consent obtained where required. The same five systems that were a light review under a stock deal become a multi contract consent programme under an asset deal. This is the practical reason the structure choice cannot be made without the software estate in view.
The contrast sharpens further where the estate includes products from the most consent sensitive publishers. As of June 2026, Oracle, SAP, Microsoft, and IBM are the most active in treating an ownership change as a moment to review entitlement, with Broadcom increasingly active across the former VMware estate and Salesforce and ServiceNow rising. An asset deal that assigns a large Oracle or SAP footprint carries materially more consent and true up risk than the same estate moved under a stock structure, simply because more clauses are engaged and more contracts are reopened.
In practice, bringing software into the structure decision means running a rapid clause and consent assessment early in diligence, before the tax and legal teams fix the structure. The assessment gives the deal team a comparative view: here is the consent burden under a stock structure, here it is under an asset structure, and here is the difference in cost, timeline, and risk. That comparison rarely overturns a structure chosen on strong tax or liability grounds, but it does ensure the software consequence is a known input rather than a surprise discovered after the structure is locked. Where the software difference is large, it can tip a finely balanced decision, and at minimum it lets the buyer plan the consent programme from the moment the structure is set. The legal interpretation of which clauses each structure triggers remains a matter for the buyer own counsel.
The structure assessment comes down to a short set of questions answered for the specific estate. Under a stock structure, the buyer asks which contracts contain a broad change of control trigger that fires on a change of ultimate ownership, since these are the clauses that survive a stock deal. Under an asset structure, the buyer asks which contracts contain anti assignment language and which of those require discretionary consent on critical systems, since these set the consent burden. Under a merger, the buyer asks which contracts deem a merger an assignment regardless of the surviving entity. The same contract may answer differently under each structure, which is exactly why the assessment has to be run against all the structures genuinely under consideration rather than the one the tax team currently favors.
The output is a comparative table the deal team can use, showing the consent count, the number of discretionary consents on critical systems, and the estimated cost and timeline under each structure. That comparison makes the software consequence visible alongside the tax and liability analysis, so the structure decision is made with full information. In most deals the software difference is one input among several, but in a software heavy target it can be large enough to shift the decision, and at a minimum it ensures the buyer plans the consent programme from the moment the structure is set rather than discovering its scale afterward. The legal interpretation of which clauses each structure triggers belongs with the buyer own counsel.
We model how stock vs asset purchase changes your software consent burden, so the structure decision is made with the licensing exposure quantified, not assumed.
Request a change of control clause review