What Is a Divestiture? | M&A Glossary

What is a divestiture? It is the sale or disposal of a business unit by its parent company. Where a carve out describes the deal from the buyer point of view, a divestiture describes it from the seller side. The software challenge is the mirror image of the buyer problem. As the divested unit leaves, the parent is left with agreements that were sized for the combined organisation and now carry capacity no one uses. Managing a divestiture well means separating the shared estate cleanly and reclaiming the cost left behind.

The seller side of a software separation

In a divestiture the parent has to decide which software the departing unit takes, which stays, and how the shared agreements are split. The unit may have been running on the parent enterprise licenses, shared infrastructure and centrally managed systems. As it leaves, the parent must stop providing what it is not permitted to provide, while continuing essential services under a transition services agreement until the buyer is ready. Getting this wrong exposes the parent to a compliance claim for extending licenses it no longer has the right to share.

Stranded cost after a divestiture

The most common and most overlooked consequence of a divestiture is stranded cost. The parent agreements were sized for the whole organisation. When the unit departs, its share of the licenses does not leave with it. The parent keeps paying maintenance and subscription fees on entitlement that has no users behind it. Nothing breaks, so the cost sits unnoticed in the budget. Some agreements even auto renew at the old volume, locking the inflated baseline in for another term. Reclaiming this cost means resizing each agreement to the organisation that remains.

Managing a divestiture cleanly

The disciplined approach is to map what the departing unit uses against what the parent agreements entitle, so both the transfer and the stranded cost are visible. The parent then resizes its agreements at the right point in each renewal cycle and confirms it is not extending licenses it cannot share during the transition. Done well, a divestiture ends with the parent paying only for what it still uses and the buyer running a clean standalone estate. This is commercial and licensing advisory, not legal advice.

Divestiture versus carve out
Aspect	Divestiture	Carve out
Point of view	Seller and parent	Buyer and acquirer
Main software risk	Stranded and over licensed cost	Under licensed gap on new entity
Key action	Resize agreements to remaining org	Procure or assign licenses for the unit
Shared tool	Transition services agreement	Transition services agreement

Key takeaways

A divestiture is the sale of a business unit, the seller side of a carve out.
The parent is left with agreements sized for the whole organisation and now oversized.
Stranded cost is the most overlooked consequence and hides because nothing breaks.
Clean management means resizing each agreement to the organisation that remains.

Recommendations for buyers

Map departing usage against entitlement. Make the transfer and the stranded cost visible on every agreement.
Protect the transition. Confirm the parent is permitted to provide each service it bridges under a TSA.
Resize at renewal. Reset each agreement to the remaining organisation at the cleanest commercial moment.
Stop the auto renewals. Give notice in time so the inflated baseline is not locked in for another term.

Related reading: see the M&A software glossary hub, plus carve out and transition services agreement.

Frequently asked questions

What is the difference between a divestiture and a carve out?

They describe the same separation from opposite sides. A divestiture is the seller selling a unit. A carve out is the buyer acquiring it. The seller worries about stranded cost, the buyer worries about an under licensed gap.

What are stranded license costs in a divestiture?

Entitlements the parent keeps paying for after the divested unit stops using them. Because the agreements were sized for the combined organisation, the departed unit share is left behind with no users behind it.

Can a parent keep providing software to the divested unit?

Only within what the underlying licenses allow, usually for a limited transition period under a transition services agreement. Extending licenses beyond that right can expose the parent to a compliance claim.

When should a parent resize its agreements after a divestiture?

At each renewal point. Resizing at renewal resets the baseline cleanly and produces a durable saving, rather than chasing a one off mid term credit that may not be available.

Request a confidential software M&A risk assessment.

Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.

Talk to a software M&A advisor