Divestiture separates shared licenses cleanly
How a buyer carved a business unit out of a larger parent and untangled a shared software estate without leaving the new company running unlicensed or the parent paying for capacity it no longer used.
This case study is an anonymised composite drawn from representative engagements. It names no real parties and uses approximate figures to illustrate typical outcomes.
This divestiture separates shared licenses cleanly case study shows how a buyer acquiring a carved out business unit untangled software entitlements that the parent and the unit had shared under one master agreement. The risk in any divestiture of this kind is the same. The entitlements do not split automatically, so the unit can end up using software it no longer holds while the parent keeps paying for capacity it no longer needs. The buyer separated the estate deliberately, used a transition services agreement as a bridge rather than a destination, and entered standalone life fully licensed, avoiding roughly 1.6 million dollars in stranded and duplicate cost.
Inside the divestiture separates shared licenses cleanly case study
Situation
A buyer was acquiring a business unit being divested from a larger industrial parent. The unit ran the same core applications as the rest of the parent, all licensed centrally under a single enterprise master agreement in the parent's name. There was no separate contract for the unit, no record of how many licences it consumed, and no inventory of which systems would travel with it. The deal was structured as an asset purchase of the unit, which meant the parent's master agreement did not transfer with it.
Risk faced
Because the entitlements sat with the parent, the divested unit had no licences of its own on day one. If it kept running the applications after separation, as it had to in order to operate, it would be using software it was not entitled to, exposing the buyer to an audit and an unlicensed use claim. At the same time the parent was at risk of paying for an enterprise wide volume that now exceeded its reduced footprint, carrying stranded cost it no longer needed. Splitting the estate by guesswork would have left both sides wrong. The shared usage had to be measured before it could be divided.
Approach
We measured the unit's actual consumption of each application, separating it from the parent's usage so that entitlement could be assigned on evidence rather than estimate. We then structured a short transition services agreement that let the unit continue to operate under the parent's licences for a defined window, explicitly treating the TSA as a bridge and not a destination. In parallel we negotiated standalone entitlements for the divested unit at the right volume, and worked with the parent to reduce its own licence count to match its reduced footprint. The buyer's counsel handled the contractual mechanics of consent and transfer.
Outcome
The divested unit entered standalone life with its own licences, sized to verified consumption, before the transition window closed. It never ran unlicensed. The parent reduced its volume to match what it actually used, releasing stranded maintenance and subscription cost. Across both sides, roughly 1.6 million dollars of stranded and duplicate spend was removed, and the buyer avoided an audit exposure that an uncontrolled separation would almost certainly have created. The separation was clean because it was measured first and bridged deliberately, not improvised after close.
| Element | At separation | After clean split |
|---|---|---|
| Unit entitlements | None, used parent licences | Own licences, sized to use |
| Transition cover | Undefined | Time boxed TSA bridge |
| Parent volume | Enterprise wide, now excess | Reduced to actual footprint |
| Stranded and duplicate cost | ~$1.6M at risk | Removed |
Lessons for buyers
- Shared licences do not split automatically when a unit is divested.
- An asset purchase leaves the parent's master agreement behind, so the unit starts with nothing.
- A TSA is a bridge to a standalone position, never the destination itself.
- Measuring consumption first let both sides size entitlements correctly and remove 1.6 million dollars.
- Measure unit consumption first. Separate the unit's usage from the parent's before assigning any entitlement.
- Treat the TSA as a clock. Use the transition window to stand up standalone licences, and exit before it lapses.
- Size to verified use. Buy standalone entitlements against measured consumption, not against the parent's enterprise volume.
- Coordinate both sides. Reduce the parent's count as the unit gains its own, so neither carries stranded cost.
This outcome is the work of our carve out and TSA service, applied to the approach in the carve out and TSA guide. For the questions buyers ask most, see the FAQ below.
Frequently asked questions
What are shared licenses in a divestiture?
They are software entitlements held by the parent under a single master agreement and used by both the retained business and the unit being divested. When the unit separates, those entitlements cannot simply be split in two. The agreement defines who holds them, and using them after separation without consent can breach the licence.
Why is separating shared licenses risky?
Because the divested unit often keeps using software it is no longer entitled to, while the parent keeps paying for capacity it no longer needs. Both sides can end up exposed, the buyer to an audit for unlicensed use and the seller to stranded cost. A clean separation has to assign entitlement deliberately, not by default.
How does a TSA help with shared software?
A transition services agreement can let the divested unit keep using the parent's software for a defined period while a permanent licensing position is built. It buys time, but it is not a destination. The risk is letting the TSA lapse before the unit has its own entitlements, which leaves it running unlicensed.
Is this case study based on a real company?
No. It is an anonymised composite drawn from representative buyer side engagements. It names no real parties and uses approximate figures to illustrate a typical outcome rather than to describe a single identifiable transaction.
Separating shared software in a divestiture?
Request a confidential software M&A risk assessment. We separate shared entitlements cleanly and avoid stranded cost.