Home/Services/Carve Out Separation
For buyers and deal teams

Carve out software license separation

Carve out software license separation untangles the shared licenses a divested business depends on, prevents stranded cost on both sides, and gives the new entity its own clean entitlement from day one.

Carve out software license separation is the part of a divestiture that decides whether the new business can actually run on the software it inherits. In a carve out, the divested unit rarely owns its own licenses. It runs on the parent enterprise agreements, shared instances, and volume contracts that were never written to split. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and a carve out forces that exposure into the open because the shared estate must now be divided. Separating the licenses cleanly protects both the buyer of the unit and the seller who keeps the rest.

Carve out software license separation sequenceTimeline showing the five stages of carve out license separation from mapping shared entitlement through to a clean standalone estate.1Map sharedentitlement2Identifyseparable rights3Negotiatenew contracts4Run TSAbridge5Stand upclean estate
The five stages of carve out license separation, from mapping shared entitlement to a clean standalone estate. Stages overlap in practice.

What carve out software license separation involves

The first task is to see what is actually shared. A divested business unit typically runs on a mix of dedicated licenses, shared enterprise agreements, and instances that serve the whole parent. Most of the value and most of the risk sits in the shared layer, because those rights do not automatically follow the unit out of the door. We map every publisher relationship the unit depends on and classify each one as separable, requiring a new contract, or blocked by an anti assignment clause that needs publisher consent.

From that map we build the separation plan. Where rights can transfer, we transfer them. Where they cannot, we negotiate new agreements for the standalone entity, ideally before the deal closes so the unit is not exposed on day one. Where a transition service agreement is needed to bridge the gap, we scope it tightly so it does not become an open ended cost. The goal is a divested business that runs on its own entitlement, with no surprise audit waiting and no parent contract it is silently still consuming.

License categories in a carve out and how each is handled
License category in the unitSeparation approach
Dedicated licenses owned by the unitTransfer with the entity where terms allow
Shared enterprise agreement entitlementSplit or replace with a new standalone contract
Rights blocked by anti assignment clausesSeek publisher consent or negotiate a fresh agreement
Usage bridged under a TSAScope tightly with a defined exit date and entitlement
Parent instances the unit silently consumesIdentify, price, and replace before TSA exit

Why shared licenses are the hidden risk in a carve out

The danger in a carve out is the entitlement nobody can see. Because the unit has been running inside the parent, it has been consuming software under contracts it does not hold and may not even be aware of. When the parent stops providing that access, the unit must either have its own agreement in place or it is suddenly running unlicensed. A change of control and anti assignment clauses can trigger consent, termination, or repricing, and a carve out involves both a change of control for the unit and the assignment of rights that were never meant to move. The deal structure, whether stock purchase, asset purchase, or a true legal separation, changes which clauses bite and how hard.

Separation also protects the seller. If shared licenses are split carelessly, the parent can be left paying for entitlement the divested unit took with it, or holding exposure for usage that has walked out the door. As of June 2026, the public record on inherited licensing disputes, including SAP pursuing AB InBev for a figure in the region of 600 million dollars, shows how large an unmanaged licensing position can become once ownership changes. Clean separation keeps both sides out of that position. 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 separate the estate without leaving stranded cost

We separate from the entitlement up. We quantify what the unit consumes before any contract is touched, so the new agreements are sized to real usage rather than a copy of the parent footprint. We negotiate the standalone contracts against that measured demand, which keeps the new entity from overbuying and keeps the parent from carrying stranded license cost after the unit leaves. We scope every transition service agreement with a defined exit so the bridge does not become a permanent line item. Because we are independent and paid only by the acquirer, the separation plan serves the buyer of the unit rather than the convenience of the seller or the publisher.

Key takeaways

  • A divested unit usually runs on shared parent contracts that do not automatically follow it out.
  • The shared entitlement layer holds most of the value and most of the risk in a carve out.
  • Anti assignment and change of control clauses decide which rights can move and which need consent.
  • Clean separation prevents stranded cost for the seller and unlicensed usage for the buyer.

Recommendations for buyers

  1. Map the shared layer first. The risk lives in entitlement the unit consumes but does not hold.
  2. Size new contracts to measured usage. Build the standalone estate from real demand, not the parent footprint.
  3. Resolve consent early. Anti assignment clauses can block transfer, so engage publishers before close.
  4. Bound every TSA. Give each transition service a defined exit so the bridge does not become permanent cost.

Pair this with our carve out and TSA service and the carve outs and TSA pillar. In practice: a divested estate stood up in 60 days and shared licenses separated cleanly.

Frequently asked questions

What is carve out software license separation?
It is the process of untangling a divested business unit from the parent's shared software contracts and giving it its own clean entitlement, so it runs licensed from day one.
Why are shared licenses a problem in a carve out?
Because the unit consumes software under contracts it does not hold. When the parent stops providing access, the unit must have its own agreement or it is suddenly running unlicensed.
Do software licenses transfer automatically in a divestiture?
Often not. Anti assignment clauses can block transfer and a change of control can trigger consent or repricing. Each contract must be assessed against the deal structure.
What is a TSA in this context?
A transition service agreement lets the unit keep using parent software for a defined period after close. It should be tightly scoped with a clear exit so it does not become a permanent cost.
Are you independent of software publishers?
Yes. We are paid only by the acquirer and hold no affiliation with any publisher or reseller.

Carving out a business that runs on shared licenses?

We separate a divested unit's software cleanly, size its new estate to real usage, and bound the TSA. Tell us about the deal and we respond within one business day.

Book a confidential call