What Is a Carve Out? | M&A Glossary

What is a carve out? It is a deal where the buyer acquires part of a larger company, a division or business unit, rather than the entire entity. The defining software challenge is separation. The carved out unit has usually been running on shared licenses, shared systems and shared agreements that belong to the parent. Pulling it out cleanly means untangling that shared estate, and the licenses rarely transfer automatically. A carve out is therefore one of the highest risk deal types for inherited software exposure.

Why software makes carve outs hard

In a standalone company the software estate is the company own. In a carve out the estate is shared. The unit being sold may rely on the parent enterprise agreements with Microsoft, Oracle, SAP and others, on shared infrastructure, and on systems administered centrally. None of that is guaranteed to come with the unit. Many agreements restrict use to the parent organisation, so the carved out business cannot simply keep using them. The buyer often has to procure new licenses, negotiate assignments, or run a transition services agreement while it builds a standalone estate.

The shared license problem

The core issue is that shared licenses do not split neatly. An enterprise agreement sized for the parent organisation includes the carved out unit usage inside one entitlement. Separating it raises two risks at once. The buyer can be left under licensed, running software it has no entitlement for under the new entity. The parent can be left over licensed, paying for capacity the departed unit no longer uses. Both are real costs, and both are invisible unless someone maps usage against entitlement on each agreement before and after separation.

How buyers should approach a carve out

The work is to inventory every shared agreement the unit depends on, determine which can transfer and which must be replaced, and sequence the separation so there is no day when the unit is running unlicensed software. A transition services agreement usually bridges the gap, but it has to end with a fully licensed standalone estate. Mapping this before signing turns a carve out from a source of latent exposure into a planned separation. This is commercial and licensing advisory, not legal advice.

Carve out software separation checklist
Area	Question	Typical outcome
Shared agreements	Which licenses does the unit rely on	Inventory of dependencies
Transfer rights	Which can be assigned to the buyer	Consent list to obtain
New procurement	What must the buyer license itself	Standalone agreements
Transition	How is the gap bridged	TSA with a hard end date

Key takeaways

A carve out acquires part of a company, so the software estate is shared and must be separated.
Shared enterprise licenses rarely transfer automatically and often cannot be used by the new entity.
Separation creates risk on both sides: an under licensed buyer and an over licensed parent.
A transition services agreement bridges the gap but must end in a fully licensed standalone estate.

Recommendations for buyers

Inventory the shared estate before signing. Map every agreement, system and service the unit depends on.
Separate transfer from replacement. Decide which licenses can be assigned and which must be bought new.
Plan the TSA exit. Use the transition period to stand up a standalone estate with a hard end date.
Watch both sides. Protect the buyer from an under licensed gap and help the parent reclaim stranded cost.

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

Frequently asked questions

Why is a carve out riskier than buying a whole company?

Because the software estate is shared with the parent rather than self contained. Separating shared licenses, systems and agreements creates exposure that does not exist when the buyer acquires a standalone entity.

Do shared software licenses transfer in a carve out?

Not automatically. Many enterprise agreements restrict use to the parent organisation, so the carved out unit usually needs assignments, new licenses, or a transition services agreement to keep running.

What is the parent risk in a carve out?

Being left over licensed. Agreements sized for the combined organisation keep carrying the departed unit capacity, so the parent pays for entitlement with no users behind it until the agreements are resized.

How long does a carve out separation take?

It depends on the size of the shared estate, but the licensing separation typically runs across the transition services agreement period, which is scoped in months. The aim is a clean standalone estate by the TSA end date.

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