Carve-Out

What Is Carve-Out?

A carve-out is the separation of a specific business unit, subsidiary, or asset from a parent company’s systems and data, typically as part of a divestiture, spin-off, or partial sale. The IT dimension of a carve-out is the hard part: untangling a business unit’s data, applications, and infrastructure from a parent company’s shared systems, where years of consolidated ERPs, shared file systems, and common identity providers have blurred the line between what belongs to which entity.

Once separation is technically defined, the carve-out produces two parallel workstreams. The divested entity needs its data migrated to new, independent systems it will operate going forward. The parent company, meanwhile, is left with data belonging to the departed business that it can no longer operationally use but frequently still must retain; for tax history, prior litigation, or regulatory retention windows that predate the sale. That residual data is typically archived rather than migrated or deleted, since neither company wants to keep running a full application instance just to preserve records from a business unit that’s already gone.

Carve-outs run on fixed external deadlines, a Transition Services Agreement (TSA) with the acquirer typically sets a hard date by which the parent’s systems must stop serving the divested unit. Data separation and archiving work against that same clock, which is what makes carve-out IT projects notoriously tight compared to voluntary decommissioning work.

Key Points

• Driven by a corporate transaction. Carve-outs happen because of a divestiture, spin-off, or partial sale, the IT separation work is a consequence of the deal, not an independent initiative.
• Runs against a TSA deadline. Transition Services Agreements set a fixed date by which the parent’s systems must stop supporting the divested entity, creating a hard external deadline that most decommissioning projects don’t face.
• Produces two data destinations. The divested unit’s active data migrates to its own new systems; data the parent no longer needs operationally but must retain typically goes to an archive instead of being deleted or migrated.
• Data separation, not just data copying. Shared systems must be untangled at the record level, splitting a shared ERP’s data by legal entity is materially harder than a straightforward migration where everything moves together.
• Retention obligations survive the deal. Tax, litigation hold, and regulatory retention requirements on the divested unit’s historical data typically continue regardless of who now owns the underlying business.

Common Use Cases

🏢 Divesting a business unit from a shared ERP

A parent company sells a division that has operated inside a shared, consolidated ERP for years. Finance, HR, and operational data specific to that division is extracted, archived on the parent’s side for retention purposes, and separately migrated to standalone systems for the newly independent entity, all before the TSA-mandated cutoff.

📄 Preserving tax and regulatory history post-sale

After a carve-out closes, the parent company retains tax filings, regulatory correspondence, and financial records tied to the divested unit’s pre-sale history in a compliant archive, satisfying multi-year retention obligations without keeping the original shared systems running.

⚖️ Litigation hold continuity across a spin-off

When a spin-off involves ongoing or reasonably anticipated litigation tied to the separated business, both parties need continued, defensible access to relevant historical records, typically preserved in an archive rather than left inside a shared system neither party fully controls after separation.

Carve-Out vs. Related Concepts

Carve-out overlaps with, but isn’t identical to, two other M&A-adjacent terms.

DIVESTITURE

The broader corporate transaction; the sale or spin-off itself. A carve-out is the operational and IT separation work required to execute a divestiture; divestiture is the deal, carve-out is the disentanglement.

M&A DATA MIGRATION

The process of moving an acquired company’s data into the acquirer’s systems, which runs in the opposite direction of a carve-out. M&A migration consolidates; carve-out separates.

DATA DISPOSITION

The broader decision framework for what happens to data at end-of-life; retain, archive, or destroy. Carve-outs rely heavily on data disposition decisions to determine what the parent keeps, archives, or discards once the divested unit’s data has been separated out.