What Is a Carve Out and Why Software Is the Hard Part

What is a carve out and why software is the hard part is the first question a buyer of a divested business should be able to answer with precision. A carve out is the separation of a business unit, division or product line from a larger parent so it can be sold or stood up on its own. The legal and financial separation is well understood. The part that consistently runs late, costs more than expected and creates inherited licensing exposure is software, because the carved out unit almost never owned its software in its own name.

What is a carve out and why software is the hard part

In most carve outs the divested unit ran on the parent technology estate. Its enterprise agreements, volume licenses, cloud tenants and data centre contracts sit with the parent, negotiated for the whole organisation. When the unit leaves, it cannot simply take a share of those agreements with it. The licenses were granted to the parent legal entity, and many contain terms that prevent transfer without the publisher consenting. The unit therefore arrives at its new owner with applications it depends on and very little of its own entitlement to run them.

That is the heart of why software is the hard part. A factory, a building or a customer contract can usually be assigned with manageable effort. Software entitlement is governed by license terms that were written to protect the publisher, and a change of ownership is exactly the event those terms were designed to control. The result is that the software workstream, not the legal or financial one, tends to set the critical path for the whole separation.

Why shared licenses do not simply transfer

Parent enterprise agreements are sized and priced for the parent. A divested unit using a slice of an Oracle, SAP, Microsoft or VMware agreement holds no separate entitlement to that slice. To run the same software after separation, the unit must obtain its own licenses, either by negotiating an assignment of part of the parent agreement, which the publisher must usually approve, or by buying fresh entitlement at standalone pricing that is almost always higher than the parent enjoyed.

This is where stranded cost appears on one side and shortfall on the other. The parent can be left paying for capacity the divested unit used but no longer needs, while the unit faces relicensing at a price it never budgeted. Neither side benefits from discovering this late, yet standard diligence frequently treats software as an information technology detail rather than a commercial exposure that should shape the deal.

Anti assignment and change of control clauses

Two contract terms do most of the damage. Anti assignment clauses prevent a license being transferred to another entity without the publisher agreeing, which means the carved out unit cannot simply inherit the parent entitlement. Change of control clauses are triggered when ownership changes and can allow a publisher to require consent, reprice the agreement or, in some cases, terminate it.

Which clause bites depends on how the deal is structured. A stock purchase that moves an entire legal entity may preserve some agreements but still trigger change of control terms. An asset purchase that moves applications and people without the contracting entity usually forces fresh licensing because the licenses stay behind. A carve out that stands up a brand new entity has nothing in its own name at all and must license from scratch. This is commercial and licensing advice rather than legal advice, and the specific clauses should be read with the buyer own counsel.

The transition services agreement and the software clock

Because the unit cannot separate its software instantly, the parent usually continues to provide certain systems and services for a defined period under a transition services agreement, or TSA. The TSA keeps the lights on while the unit builds its own estate. It is also a clock. TSA software services are typically priced at a premium and run for a limited term, so every week the separation takes is a week of paying the parent to bridge the gap.

The TSA is where an unmapped software estate becomes expensive. If the unit does not know exactly which applications it depends on, which licenses must be replaced and how long each replacement will take, the TSA extends, costs rise and the exit slips. A disciplined carve out treats the TSA exit on software as a project with a critical path, not an open ended safety net.

Stranded cost on one side, shortfall on the other

A carve out creates a mirror image problem. The parent is often left with stranded software cost: capacity, user counts or contractual commitments that were sized to include the divested unit and that cannot be reduced until the next renewal, if at all. The unit, meanwhile, faces a licensing shortfall, because it must acquire entitlement it never separately held. Both are real money, and both are easier to manage when they are quantified before signing rather than discovered during separation.

For the buyer specifically, the shortfall is the priority. The price to relicense the carved out estate at standalone rates, the cost of any TSA period needed to bridge the work, and the risk of a publisher consent being refused or repriced are all inputs that belong in the valuation. Found early, they shape the price and the structure. Found late, they become an unbudgeted cost in the first year of ownership.

How buyers should approach the software in a carve out

The discipline is the same one that protects buyers across software in M&A: map before you commit. Trace every application the unit depends on, identify the entitlement behind each one and whether it sits with the parent, and test the relevant anti assignment and change of control clauses against the deal structure. From that map, size the relicensing cost, the consents required and the realistic TSA duration, then build those into the negotiation.

This work connects directly to software due diligence before signing and to a structured separation afterward. It also links to the wider carve out and TSA playbook, because the same map drives the consent strategy, the TSA service catalogue and the exit timeline. A carve out is only as clean as the software separation underneath it, and the software separation is only as clean as the map it starts from.

The recurring lesson

Across carve outs, the pattern repeats: the legal and financial work finishes on schedule and the software work runs long, because the entitlement that the divested unit needs was never held in its own name and the contracts that govern it were written to resist exactly this moment. Buyers who treat software as the critical path, quantify the relicensing and consent exposure before signing, and manage the TSA exit as a project consistently separate faster and at lower cost than those who treat it as an information technology afterthought.