When a portfolio company signs an LOI to sell a division, the technology separation becomes a schedule risk with a dollar cost attached. Every day the carved-out unit stays dependent on shared systems, the seller runs a transition service agreement it would rather exit, and the buyer holds back purchase price against separation milestones that slip. That is the live problem in front of an operating partner or a portfolio CFO the week the deal is announced: who owns the plan to untangle ERP, CRM, identity, email, data warehouses and licensing before the TSA clock runs out, and how do you tell a competent divestiture technology separation consultant from a firm that will bill hours and hand you a Gantt chart nobody can execute.
This guide is written for the buyer with budget, not for someone learning the field. It covers what to decide before you scope the engagement, how to structure it, and the specific evidence that separates real operators from résumé consultants.
1. Decide what you are actually buying before you scope it
A separation engagement is not one thing. It splits into three jobs that require different skills, and firms that are strong at one are often weak at the others. Name which you are buying before you take a single pitch.
The three jobs inside a separation
- Separation planning. Building the workstream map, the dependency register, the TSA schedule and exit criteria, the Day 1 cutover sequence. This is the plan.
- Execution and cutover. Standing up the standalone stack, migrating data, cutting identity and email, and actually exiting each TSA line. This is the build.
- TSA governance. Managing the service catalog, the pricing, the exit milestones and the disputes between buyer and seller during the transition window. This is the referee role.
A consultant who only does the first hands you a deck and disappears at cutover, which is exactly where separations fail. Confirm the firm owns the plan through to the last TSA line exiting, not to Day 1. The broader mechanics of the service agreement itself are worth reading separately in this walkthrough of transition service agreement consulting.
The commercial context matters here. Carve-outs are a persistent share of deal activity, and firms like Bain & Company in its annual private equity report and McKinsey’s private capital research have long tracked separations as one of the harder value-capture problems in the asset class. Deal volume data from PitchBook and Preqin reinforces that divestitures are not a rare event in a portfolio, so the decision is repeatable and worth getting a repeatable answer to.
2. Build the decision on evidence, not on the org chart
Before you scope the engagement, the consultant should be able to produce a baseline: what systems the divested unit shares with the parent, who owns each, and what the cleanest cut looks like. If the firm cannot describe the shape of that separation inventory in a first conversation, they will learn it on your budget.
Insist on three artifacts as the entry price for the engagement:
- A dependency register that lists every shared system, the direction of the dependency, and the estimated effort to break it.
- A TSA exit schedule tied to that register, with each service line, its cost, and its planned exit date.
- A risk register that names the failure modes with owners, not a generic list.
This is the same discipline you would apply to technology due diligence before signing, just run in reverse: instead of assessing an asset you are buying, you are documenting an asset you are splitting. The good news is that if diligence was done well, much of this inventory already exists.
3. Judge the consultant on how they handle the hard parts
Separations fail in predictable places. Ask the firm to walk you through how they handle each, and listen for whether they have done it or read about it.
Identity, email and licensing
The moment the carved-out unit needs its own domain, its own directory and its own software licenses, entitlement negotiations and cutover sequencing get ugly. A firm that has run this will describe the sequence without prompting and will flag where per-seat license transfers get expensive.
ERP and CRM data
Deciding what data moves, what stays and what gets cloned is where separations either finish clean or leave the divested unit crippled. This is closely related to the reverse problem of CRM and ERP integration post merger, and a consultant who understands both directions is worth more than one who has only ever merged systems.
The TSA exit itself
The seller wants out of the TSA fast to stop carrying the cost and the risk. The buyer wants the TSA long enough to stand up its own stack safely. A strong consultant manages that tension against milestones instead of letting it turn into a dispute. Governance frameworks discussed at the Harvard Law School Forum on Corporate Governance and case analysis in Harvard Business Review’s M&A coverage both make the same point in different words: the transition period is where value quietly leaks.
4. Structure the engagement around exit criteria, not activity
The failure mode in consulting is paying for activity: hours logged, meetings held, slides produced. In a separation, activity is not the deliverable. The deliverable is each TSA line exited on or ahead of schedule, at or under cost, with the divested unit fully operational on its own stack.
Tie the engagement to milestones with money attached:
- Signed dependency register and TSA exit schedule accepted by both buyer and seller.
- Day 1 readiness confirmed with a defined cutover runbook.
- Each TSA service line exited against its planned date, with variance reported.
- Final separation confirmed, TSA fully wound down.
This is the same buying discipline used to evaluate any portfolio integration partner. The judging criteria in this piece on how to buy and judge a 100 day integration plan consultant transfer almost directly, and the sequencing logic overlaps with the first 100 days playbook operating partners already run.
5. Watch the revenue systems, not just the back office
Separation projects are often scoped as an IT and finance exercise, and the revenue stack gets treated as an afterthought. That is a mistake. When CRM, marketing automation and the reporting layer are split badly, the divested unit loses pipeline visibility on Day 1 and the seller’s forecast on the retained business goes dark at the same time.
If your consultant does not have a clear plan for the revenue systems, bring in someone who does. The judging frameworks in this guide on how to judge a marketing operations consultant in private equity and this one on running outsourced RevOps for a portfolio company cover the revenue-side questions a pure infrastructure separation team will miss.
The financial reporting consequences are real. Accounting bodies such as AICPA & CIMA and, for registrants, filing rules from the U.S. Securities and Exchange Commission shape how the divested unit must report standalone, and market data providers like S&P Global Market Intelligence track how frequently carve-outs get restructured when the separation is done poorly. Industry coverage in Private Equity International, Buyouts and PE Hub, along with separation research from BCG’s principal investors and private equity practice, all reinforce that a clean cut protects the multiple on both sides of the deal.
6. A next-step checklist for the buyer
Before you sign a scope with any divestiture technology separation consultant, confirm the following:
- The firm owns the plan through the last TSA line exiting, not just to Day 1.
- They can produce a dependency register, a TSA exit schedule and a named-owner risk register as the entry price.
- They can describe identity, licensing, ERP and CRM cutover sequencing from experience, not theory.
- The engagement is priced against exit milestones with money attached, not hours.
- The revenue stack has an owner in the plan, not just IT and finance.
- Variance is reported against plan on every milestone, so slippage is visible early.
For a fuller view of how these engagements sit inside a broader portfolio program, the buying guides on hiring a marketing operations consultant in a PE-backed company and buying marketing as a service for portfolio companies apply the same evidence-first standard used here.
A separation done right protects purchase price on the sell side, gets the divested unit operational without a visibility gap, and closes the TSA before it turns into a running cost. If you want a separation and post-close integration team that scopes to exit criteria and owns the plan through the last TSA line, review the private equity program from DevriX and GrowthShuttle.