Divestiture

What Is Divestiture?

Divestiture is the sale or disposal of a business unit, subsidiary, or asset. From a data standpoint, every divestiture requires a decision, negotiated as part of the deal terms, about which records transfer to the buyer, which stay with the seller, and which need to be accessible to both parties for some period afterward; typically for tax history, ongoing litigation, or contractual obligations that predate the sale.

This decision has to be made at the record level, not the system level, because the divested unit rarely operated on its own dedicated, easily separable infrastructure. More often it shared an ERP, a CRM, or a file system with the rest of the parent organization, meaning its data has to be identified, extracted, and separated out of systems the seller will keep running for its remaining business. The buyer needs a clean, complete copy of everything relevant to the unit they just acquired; the seller needs to retain what it’s still legally obligated to keep, without handing over data unrelated to the deal.

What the seller retains after the sale almost always ends up in an archive rather than a live system, since the seller has no ongoing operational need for a divested unit’s historical data, only a retention obligation. Keeping a full live application running indefinitely just to satisfy that obligation is the exact cost the archiving decision is meant to avoid, which is why divestiture-related data separation projects are one of the most common triggers for a compliance-driven archiving initiative.

Key Points

• A record-level separation. Because divested business units rarely run on fully dedicated infrastructure, their data typically has to be identified and extracted out of shared systems rather than simply handed over as-is.
• Retention terms are negotiated as part of the deal. What data transfers, what’s retained by the seller, and what both parties need shared access to for a defined period are typically specified in the transaction agreement itself.
• The seller’s retained data usually becomes archival. Historical records the seller must keep for tax, litigation, or regulatory reasons after the sale have no ongoing operational purpose, making them a natural fit for an archive rather than a live system.
• A common trigger for compliance-driven archiving. Divestiture data separation projects frequently prompt an organization’s first serious investment in structured archiving, since the deal creates a hard deadline the organization can’t ignore.
• Distinct from, but related to, a carve-out. Divestiture is the corporate transaction; the technical work of separating and archiving data is the carve-out execution that supports it.

Common Use Cases

🏢 Separating divested unit data from a shared ERP

A parent company selling a division extracts and separates that division’s financial and operational data from a shared ERP instance, delivering a clean data set to the buyer while archiving what the seller must retain for its own tax and regulatory purposes.

⚖️ Litigation hold continuity after a sale

When ongoing litigation involves the divested business unit, both buyer and seller need continued, defensible access to relevant historical records, typically preserved in an archive that survives independently of whichever party’s systems the data originally lived in.

📄 Retaining tax history after divestiture

Following the sale, the seller retains several years of tax filings and financial records tied to the divested unit’s pre-sale operations in a compliant archive, satisfying regulatory retention requirements without keeping a full duplicate of the original system running.

Divestiture vs. Related Concepts

Divestiture is closely related to two other M&A and disposition terms.

CARVE-OUT

The operational and IT execution work, separating systems and data, required to complete a divestiture. Divestiture is the business transaction; carve-out is how it actually gets done technically.

M&A DATA MIGRATION

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

DATA DISPOSITION

The broader framework for deciding whether data is retained, archived, or destroyed at end-of-life. A divestiture triggers data disposition decisions specifically for the records tied to the business unit being sold.