Software due diligence for stock vs asset purchases is a different exercise depending on the structure, because the deal structure decides which contract clauses bite and which licenses survive the transaction. A stock purchase usually carries the target estate intact, so the priority is finding the exposure and the change of control clauses that travel with the entity. An asset purchase often breaks the licenses, because they do not transfer automatically and may need consent or repurchase. Treating the two the same way is one of the most common and costly errors in software due diligence.
The distinction matters because the same software estate can produce a very different bill depending on how the deal is papered. In a stock deal the buyer inherits the contracts and the latent compliance gaps with them. In an asset deal the buyer may have to re license software it thought it was acquiring, turning a transfer into a purchase. Knowing which structure is on the table tells the diligence team where to look first.
Software due diligence for stock vs asset purchases
In a stock purchase the target entity survives the deal, so its software agreements generally continue under their existing terms. The risk is twofold. First, many agreements contain a change of control clause that can require consent, allow termination, or trigger repricing when ownership changes. Second, the buyer inherits every latent compliance gap in the estate, because nothing resets at close. In an asset purchase the buyer acquires selected assets rather than the company, and software licenses usually do not transfer with them. Anti assignment clauses can block the move, and the buyer may need the publisher consent or a fresh license to keep using the software lawfully.
The change of control question is central to both structures, but it bites differently. The mechanics of how these clauses operate are covered in our change of control material, and the practical point for diligence is to read every material agreement for the trigger and the remedy. A clause that merely requires notice is a formality. A clause that allows the publisher to terminate or reprice on a change of control is a negotiating lever the seller has handed to a third party.
Why an asset deal can cost more than expected
The hidden cost in an asset purchase is re licensing. When licenses do not transfer, the buyer faces a choice: obtain consent to assign, which the publisher may grant only at a price, or buy new licenses for software already running in the business. Either way the publisher holds leverage, because the buyer needs continuity of use from day one. Quantifying that re license cost during diligence, rather than discovering it after close, is what keeps it from becoming a surprise. The method for putting a number on it is described in quantifying software audit exposure before you sign.
Why a stock deal carries inherited risk
The hidden cost in a stock purchase is the opposite: nothing changes hands, so every latent compliance gap comes with the entity. If the target has under licensed Oracle on a virtualised cluster or unlicensed SAP indirect access, the buyer now owns that exposure in full. As of mid 2025, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million in disputes tied to indirect and inherited licensing, a reminder that inherited exposure in a stock deal can be very large. The way these gaps stay hidden is explained in how latent licensing exposure hides from diligence.
Key takeaways
- Deal structure decides which clauses bite: a stock deal carries the estate, an asset deal can break the licenses.
- In a stock purchase the buyer inherits every latent compliance gap, because nothing resets at close.
- In an asset purchase licenses usually do not transfer and may need consent or repurchase at the publisher price.
- Change of control clauses matter in both structures, but the remedy ranges from a notice to a termination right.
- Reading the contracts against the structure tells the diligence team where the cost will land.
How structure changes the diligence plan
Because the structures expose different risk, the diligence plan should change with them. For a stock purchase the team prioritises measuring the inherited compliance position and finding the change of control clauses that could be triggered by the deal. For an asset purchase the team prioritises mapping which agreements transfer, which require consent, and what a fresh license would cost for the software that does not move. The contract reading discipline behind both is set out in reading a target software contracts in due diligence.
Where a carve out raises the stakes
A carve out is the structure where deal type matters most, because the separated business may lose access to the parent group wide and shared agreements that it relied on. Software licensed at the group level does not follow the carved out unit automatically, so the buyer can face a standalone re license cost across an entire stack. Identifying those shared agreements early is the difference between a clean separation and a transition that overruns on cost. The deal team should treat the carve out as the highest risk structure for licensing continuity and scope the diligence accordingly.
Recommendations for buyers
- Confirm the deal structure before scoping, because it decides where licensing risk lands.
- In a stock purchase, measure the inherited compliance position and map every change of control clause.
- In an asset purchase, identify which licenses transfer, which need consent, and the cost to re license the rest.
- Quantify the re license or settlement cost during diligence so it can be priced or made a condition of close.
- Treat a carve out as the highest risk structure and find the shared and group wide agreements first.
Matching the diligence to the structure is what makes the software due diligence method precise rather than generic. The full workstream is delivered through our software due diligence service.