An IT carve-out is the work of separating a business unit’s technology from its parent company when the unit is sold, spun off or otherwise divested. It covers networks, user accounts and email, applications and their data, cloud and data center resources, vendor contracts and support. Because the unit often runs on shared systems right up to closing, a carve-out usually relies on a transition period in which the seller keeps providing services while the new owner builds or buys its own.
At a glance
- A carve-out separates a unit’s systems, data, contracts and services from a parent that keeps running its own.
- The unit often depends on shared parent systems at closing, so separation is phased.
- A transition services agreement (TSA) commonly lets the seller keep supporting the unit for a set period.
- Vendor contracts may need to be assigned or novated, split, or replaced, depending on their terms.
- TSA deadlines, data separation and license transfers drive much of the cost and risk.
What problem it solves
Inside a large company, a business unit rarely has its own IT. It shares the parent’s network, identity system, email, ERP, help desk, security tools and vendor contracts. When the unit is sold, both sides need a clean break: the seller must stop supporting and exposing a business it no longer owns, and the buyer must make sure the unit keeps operating without interruption.
A planned IT carve-out turns that break into a sequence of steps with owners, dates and costs. Without one, the unit may face outages at closing, the seller may keep paying for services it no longer uses, and either side may hold data it shouldn’t. A structured approach also gives the buyer a realistic budget and timeline, which is why it is usually scoped during IT due diligence.
How it works
Inventory and entanglement. The team lists which systems, data, users, sites, licenses and contracts belong to the unit, which are shared, and which stay with the parent. IT asset management records make this faster; gaps make it slower.
Day-one plan. The minimum changes needed at closing are defined: access controls, legal entity names, critical services that must keep running, and data the buyer may and may not see.
Transition services. Services the seller will keep providing after closing are written into a transition services agreement (TSA) with scope, service levels, fees and end dates.
Target environment. The buyer either integrates the unit into its existing IT or builds a new standalone environment, often using cloud services and a managed service provider (MSP) to move quickly. Applications and data move through a planned cloud migration or data center migration.
Contracts. Each vendor agreement is reviewed. For some, the rights can be assigned under their assignment clause and duties delegated, often with the vendor’s consent, but the seller stays liable unless the vendor agrees to a novation that transfers the whole contract and releases it; others are split between the parties or replaced with new contracts. Master services agreements often hold the terms that matter. Software licenses frequently cannot transfer without vendor approval.
Cutover and exit. Users, sites and systems move to the new environment in waves, and TSA services are ended as each is replaced.
For buyers standing up a separated network quickly, our managed network services page covers options for design, rollout and ongoing operations.
When it matters for buyers
- Divesting a business unit. The seller needs a plan to separate cleanly and end transition services on time.
- Buying a carved-out unit. The buyer inherits the separation work and the TSA deadlines.
- Negotiating the deal. TSA scope, length and fees, and who pays for separation, are commercial terms.
- Spinning off a company. A spin-off faces the same separation work without a buyer’s existing IT to absorb it.
- Reviewing contracts. Shared circuits, licenses and cloud accounts need a decision for each.
Questions to ask vendors
- Can our contract be assigned, novated or split between the parent and the divested unit, and what consent is needed?
- Can licenses transfer to the new owner, and on what terms?
- How quickly can you provide standalone services for the unit at its sites?
- Can you support a phased cutover aligned to TSA end dates?
- For service partners: what similar carve-outs have you run, and what did day one look like?
- How will data belonging to the unit be separated, exported and deleted from shared systems?
How it differs from post-merger IT integration
An IT carve-out pulls a unit’s technology out of a parent environment. Post-merger IT integration brings two environments together, consolidating networks, identity, applications and vendors. A buyer of a carved-out unit may do both in sequence: separate the unit from its former parent, then integrate it into the buyer’s own IT, sometimes in a single migration where the TSA allows.