When a portfolio company is being carved out of a corporate parent, the IT separation is the workstream most likely to blow the close date, the first 100 days, or both. The revenue systems the business runs on, CRM, marketing automation, order management, billing, the data warehouse feeding every board metric, usually live inside the seller’s estate under shared licenses, shared instances, and shared identity. On day one after signing, none of that is guaranteed to belong to the buyer. A transition services agreement (TSA) buys time, but every month on that TSA is a cost line, a dependency on a seller who has no incentive to move fast, and a risk that the standalone forecast the deal was underwritten on never materializes.

The person accountable for revenue operations in the new standalone entity inherits this problem whether or not they scoped it. This guide is written for the operating partner or portfolio executive who has to decide whether to bring in a carve-out IT separation consultant, what to have them do, and how to judge whether the work is actually protecting enterprise value or just billing hours against a Gantt chart.

1. The commercial problem a carve-out creates, stated plainly

A carve-out is not an acquisition of a clean company. It is the extraction of a business unit from systems that were never designed to let it leave. The seller’s IT organization built for one entity, not two, and the separation cost, timeline, and risk are all real drivers of the return, not IT housekeeping.

Three commercial consequences sit under the technical work:

• TSA exit is a cash and risk clock. The parent typically provides shared services for a fixed period at a markup. Every extra month is EBITDA the deal model did not assume, plus operational fragility while the buyer runs revenue systems it does not control.
• Standalone cost is often understated at signing. The seller allocated IT cost on a shared basis. Standalone, the new entity pays for its own licenses, its own security stack, its own infrastructure, frequently at a worse rate because it lost the parent’s volume discounts.
• Revenue continuity is on the line. If the CRM cutover corrupts pipeline data or the billing system misfires during migration, the damage lands in the numbers the sponsor reports to its own LPs.

Bain’s annual private equity report has repeatedly documented how much value creation now depends on operational execution rather than multiple expansion, which is exactly where a botched separation destroys the plan. You can read Bain’s ongoing coverage in its Global Private Equity Report, and McKinsey’s private capital research tracks the same shift toward operating-driven returns.

2. What the consultant is actually there to decide

The mistake is to hire a carve-out IT separation consultant as a project manager who runs a checklist. The value is in the decisions they force early, before money and TSA months are committed. A strong engagement produces a small set of consequential choices, each with an owner and a cost attached.

Separate, clone, or rebuild

For every material system the business runs on, there are only three paths. Clone the parent’s instance and take a copy. Migrate onto a standalone system the buyer stands up new. Or keep running on the parent’s system under TSA and cut over later. The consultant’s job is to recommend the path per system, with the cost and TSA-duration consequence of each, not to default everything to a lift-and-shift that looks cheap and ages badly.

What comes off the TSA first

Not all systems carry equal risk on a TSA. Identity, email, and anything touching customer data or revenue recognition are the ones you want off the seller’s estate soonest. The consultant should sequence the exit by risk and cost, not by whatever is technically easiest.

Where the standalone run-rate actually lands

The single number the operating partner needs is the true standalone IT cost, licenses, infrastructure, security, headcount, once the parent is gone. This should reconcile against the deal model’s assumption. If it is materially higher, that is a finding, and it is far better surfaced in the first month than in month nine.

3. Scope the engagement before you scope the spend

A carve-out IT separation runs across several parallel tracks, and the operating partner should be able to name them before agreeing a fee. Vague scope is where budgets leak. A useful engagement is bounded around these workstreams:

• Discovery and dependency mapping. An inventory of every system the carved-out business uses, which are shared with the parent, and what each depends on. This is the evidence base for every later decision.
• TSA design and exit planning. Which services stay on the TSA, for how long, at what cost, and the exit sequence that retires them.
• Migration and cutover. The actual moves, staged, with rollback plans for the revenue-critical systems.
• Standalone stand-up. New tenants, new identity, new security stack, new contracts, so the entity can operate without the parent.

This is the same discipline that a serious technology due diligence effort applies before the deal closes. If diligence was done well, the separation consultant inherits a map. If it was thin, the first weeks of the engagement are spent rebuilding that map at a worse time. For the revenue-systems side of that inventory specifically, the framing in data strategy consulting for portfolio companies is useful for deciding what to keep, replace, or retire.

Match the scope to the deliverable, not the title

A carve-out IT separation consultant can mean anything from a solo advisor writing a separation plan to a team running the cutover. Decide which you are buying. A planning engagement produces decisions and a costed roadmap. An execution engagement produces migrated systems and a retired TSA. Pay for the one you need, and do not let a planning fee quietly expand into an open-ended execution engagement without a re-scope and a fixed deliverable.

4. How to sequence the work across the deal timeline

The separation is not a single event. It maps onto the deal calendar, and the consultant’s plan should be legible against these triggers.

Before signing, during confirmatory diligence

The separation cost and complexity should be estimated here, not discovered later. This is where the standalone run-rate and TSA duration get their first honest numbers. Getting this wrong distorts the model the sponsor funds. The relationship between diligence findings and the number you commit to is the whole point of doing RevOps due diligence before you fund the number, and IT separation is the same logic applied to systems.

Day one and the first 100 days

On day one, the business must operate. The TSA covers what has not been separated yet. The first 100 days are where the separation plan turns into sequenced execution, the highest-risk systems come off the TSA first, and the standalone stack starts to stand up. This is the window where a separation either builds momentum or stalls into a long, expensive TSA. The broader playbook for that window is worth aligning to, and DevriX frames it in its first 100 days guidance.

Through TSA exit

The end state is a fully standalone entity off the seller’s systems, with the TSA retired on or ahead of schedule. Every month pulled forward is direct cost saved and risk removed. This is the metric the engagement should ultimately be judged on.

5. The revenue systems deserve their own workstream

General IT separation consultants are strong on infrastructure, identity, and networking. They are frequently weak on the systems that actually generate and record revenue, the CRM, marketing automation, CPQ, billing, and the data pipelines that feed reporting. For a RevOps-accountable executive, this is the part that will hurt most if it is handled as a footnote.

Why CRM and billing cutovers carry outsized risk

Migrating a CRM is not moving files. Pipeline stages, custom objects, automation, integrations, and years of historical data all have to arrive intact, or the sales team loses trust in the system on day one and the board metrics stop reconciling. Billing carries revenue-recognition exposure, which is why the AICPA’s guidance on revenue matters is worth keeping in view during any cutover that touches how revenue is captured. The AICPA and CIMA resources are a reasonable reference point for the accounting side of that risk, and where public reporting is involved, the SEC framing on disclosure controls is relevant.

Where the platform decision gets made

A carve-out is one of the rare moments where a company is standing up its revenue stack from a clean sheet. That is an opportunity, not just a cost. If the parent ran a bloated, over-customized instance, the standalone entity does not have to inherit it. The decision to rebuild on a cleaner platform belongs in the separation plan, and the trade-offs are the same ones covered in HubSpot implementation for a portfolio company and, at portfolio scale, in HubSpot for a private equity portfolio. The underlying data layer decision is covered in data platform implementation in a portfolio company.

6. How to judge the consultant before you sign

Commercial buyers do not need to be told what a carve-out is. They need a way to tell a credible separation consultant from an expensive one. A few tests separate the two quickly.

They talk in TSA months and run-rate, not tickets

Ask what the engagement moves. The right answer is stated in TSA months retired, standalone run-rate landed against the deal model, and revenue systems migrated without incident. If the answer is a list of activities, meetings held, documents produced, servers touched, that is the vendor register, not an outcome. Activity is not the deliverable.

They produce a costed, sequenced plan early

A strong consultant delivers a per-system decision, separate, clone, or rebuild, with cost and TSA-duration attached, within weeks, not months. If the first deliverable is a discovery report with no recommendations and no numbers, the engagement will drift.

They have done the revenue systems, not just the infrastructure

Press specifically on CRM and billing migrations. A consultant who is fluent on networking and identity but hand-waves the revenue stack has left the highest-risk workstream unowned. The same due-diligence rigor applies to picking the consultant as to picking any external partner, and the criteria in how to choose a RevOps agency for portfolio companies transfer directly.

They separate planning from execution honestly

Be wary of a consultant who wants to plan and then execute their own plan without a re-scope. That is not automatically wrong, continuity has value, but it should be a decision, with a fixed execution deliverable and a fixed fee, not a slide into open-ended time and materials.

7. How to judge the work once it is running

The engagement is live. The operating partner needs a small set of indicators that show whether it is protecting enterprise value or drifting. Governance research from the Harvard Law School Forum on Corporate Governance and the M&A coverage in Harvard Business Review both reinforce that post-close execution discipline is where deals are won or lost, and separation is a large part of that discipline.

TSA exit is on or ahead of schedule

The clearest signal. If TSA exit dates are slipping quietly, cost is accruing and risk is extending. This should be a standing item at every board or steering meeting, with actual against plan.

Standalone run-rate is converging on the model

The true standalone IT cost should be firming up, not drifting upward with each new discovery. Surprises should shrink over time. If they are growing, the discovery phase was incomplete.

Revenue systems cut over without incident

No corrupted pipeline, no broken billing run, no reporting gap. A clean CRM cutover is measured by the sales team continuing to work and the board metrics continuing to reconcile the day after. This is where the RevOps maturity of the standalone entity gets tested, and the framing in the RevOps maturity assessment that survives a board meeting is a useful lens for what “good” looks like afterward.

The risk register is shrinking

A healthy separation closes risks faster than it opens them. If the register only grows, the plan was optimistic and the reset should happen now, not at TSA expiry.

8. Common ways carve-out separations go wrong

The failure modes repeat across deals. Knowing them lets the operating partner ask the right question early.

• The TSA becomes the plan. When separation stalls, the easy path is to extend the TSA. Each extension is cost and dependency, and the parent has no reason to help you leave. PitchBook and S&P Global both track how integration and separation timelines correlate with deal outcomes, and their research hubs, PitchBook and S&P Global Market Intelligence, are worth watching on that theme.
• Revenue systems treated as an afterthought. Infrastructure gets the attention, the CRM and billing get migrated last and fastest, and that is where the damage lands.
• Standalone cost discovered late. The model assumed the parent’s allocated cost. The real number arrives in month nine and blows the EBITDA plan.
• No single owner. Separation crosses IT, RevOps, finance, and legal. Without one accountable owner and clear decision rights, workstreams stall between functions.
• Buying capacity instead of a resourced team. A single advisor cannot run a full cutover. If the entity is staffing the separation itself, the model in data team as a service in private equity is a cleaner way to buy resourced capability than hiring against an uncertain timeline.

A note on shortcuts

Under TSA-exit pressure, teams sometimes look for shortcuts that create their own problems later, from skipping data validation to gaming customer-facing systems during migration. The general lesson from cases like why incentivized reviews trigger platform penalties applies here too, a shortcut that saves a week can cost a quarter.

9. The decision checklist

Before signing a carve-out IT separation consultant, the operating partner or portfolio executive should be able to answer each of these.

• Scope. Is this a planning engagement, an execution engagement, or both, and is the deliverable of each written down and fixed?
• Per-system path. Will the consultant deliver a separate/clone/rebuild recommendation per material system, with cost and TSA-duration attached?
• TSA plan. Is there a costed, risk-sequenced TSA exit plan, and is the target exit date named?
• Standalone run-rate. Will the engagement produce a true standalone IT cost that reconciles against the deal model?
• Revenue systems. Are CRM, billing, and the reporting data layer owned as a distinct, high-priority workstream with rollback plans?
• Ownership. Is there one accountable owner with decision rights across IT, RevOps, finance, and legal?
• Judgment metrics. Is the engagement measured on TSA months retired, run-rate landed, and clean cutovers, not on activity?
• Evidence base. Does the plan build on real diligence, or is discovery starting from scratch at a bad time?

If most of these have clear answers, the engagement is scoped to protect enterprise value. If they do not, the fee is being committed to hope. The broader context for how these engagements fit a value-creation plan sits in DevriX’s private equity resources, and the RevOps-buying models in RevOps as a service in private equity map cleanly onto how to buy separation help.

10. What good looks like at TSA exit

The end state is unambiguous, and the operating partner should hold the engagement to it. The carved-out entity runs entirely on its own systems. The TSA is retired on or ahead of schedule, with the saved months recorded as realized cost avoidance against the plan. The standalone IT run-rate is a known, stable number that reconciles to the model. The revenue stack, CRM, billing, reporting, works, and the numbers the sponsor reports upward are trustworthy.

Everything in this guide is a commercial, technical, and operating lens on separation. It is not legal, tax, or valuation advice, and the accounting and disclosure implications of any revenue-system cutover belong with the entity’s own advisors. The distinction that matters for the buyer is between a consultant who retires the TSA and lands the run-rate, and one who bills against a plan that keeps the parent in the picture longer than it needs to be.

If a carve-out separation is in front of a portfolio company now, in diligence, approaching close, or already burning TSA months, the next step is to scope the separation as a bounded initiative with named decisions and a fixed deliverable rather than an open-ended IT project. Route the work through the DevriX and GrowthShuttle private equity practice to structure that separation sprint against the revenue systems and the TSA clock that actually move the return.