TSA Data Migration Timeline for PE Portfolios
A Transition Services Agreement (TSA) is a post-close contract in which the seller of a business temporarily continues to run IT, HR, finance, or other back-office functions for the divested company until it can stand on its own. In a private equity carve-out, the TSA is a countdown clock: the day it expires, the portfolio company must own its data, applications, and infrastructure entirely, or pay steep penalties to keep the lights on. Getting the TSA data migration timeline right is therefore less an IT project and more a value-protection exercise. The core challenge is that the technical work of moving data is rarely the hard part. The hard part is the sequencing, the dependency discovery, and the identity untangling, all compressed into a fixed window set by lawyers and dealmakers rather than engineers. A portfolio company that starts planning in month four of a nine month agreement has already lost the game. This guide lays out a realistic timeline, the phases that actually consume the calendar, the cost drivers PE sponsors should model, and the approaches that keep a carve-out on schedule. According to PortMux research on carve-out separations, the single strongest predictor of an on-time TSA exit is not budget or headcount but how early discovery begins. Firms that map dependencies in the first 30 days routinely finish with weeks to spare. Those that wait pay for it in extension fees and rushed cutovers.
- KEY TAKEAWAY
- The TSA clock, not the technical complexity, is what determines success in a portfolio carve-out, and every week of delayed discovery compresses the safe migration window. PE firms that build a reverse timeline from the TSA exit date and fund a dedicated separation team routinely exit on schedule, while those that treat migration as a background IT task face extension fees that can exceed 150 percent of the original monthly service charge.
- COST / TIMELINE RANGE
- A typical mid-market PE carve-out TSA data migration runs 6 to 12 months and costs 250,000 to 2,000,000 dollars depending on data volume, application count, and integration complexity. TSA extension fees, when triggered, commonly add 125 to 200 percent to the original monthly service charge, which is why exiting on schedule protects both timeline and returns.
- PORTMUX RECOMMENDATION
- Build your migration plan as a reverse timeline anchored to the TSA exit date, and start discovery in the first 30 days after close, not after the deal noise settles. Never rely on a TSA extension as your fallback plan, because extension fees are punitive and the parent is under no obligation to grant one.
What Is a TSA Data Migration Timeline in a PE Portfolio Context?
A TSA data migration timeline is the phased schedule a portfolio company follows to move all data, applications, and infrastructure off the former parent's systems before the Transition Services Agreement expires. It spans from deal close (Day 1) through full standalone operation, and it is anchored to a contractual exit date rather than an internal preference. Missing that date triggers financial penalties.
In private equity specifically, this timeline carries direct return implications. Every month the portfolio company depends on the parent's systems, it pays a TSA service charge that erodes EBITDA. Every month past the exit date, those charges escalate. The migration timeline is where deal thesis meets operational reality.
The scope typically covers four workstreams running in parallel: data (databases, file shares, historical records), applications (ERP, CRM, custom line-of-business systems), infrastructure (compute, networking, cloud tenancy), and identity (Active Directory, single sign-on, email). Each has its own critical path, and identity is almost always the hidden constraint because so many systems depend on it.
Carve-out transactions grew to represent roughly 20 percent of global M&A deal value in recent years (source: Bain Global M&A Report, 2026), which means separation planning is now a core PE competency rather than an edge case. A well-built timeline turns a chaotic scramble into a predictable, milestone-driven program.
How Long Does a TSA Data Migration Take for a Carve-Out?
A typical mid-market PE carve-out TSA data migration takes 6 to 12 months from close to full standalone operation, with larger or more integrated businesses running 12 to 18 months. The exact duration depends on data volume, the number of shared applications, integration complexity, and how entangled identity systems are with the parent. Discovery alone consumes the first third of that window.
The reason ranges are so wide is that two carve-outs of identical revenue can have wildly different technical footprints. A business that ran on a clean, separable SaaS stack might exit in six months. A business deeply woven into the parent's on-premise ERP and shared data center might need eighteen. The TSA data migration timeline is driven by dependencies, not headcount.
Roughly 70 percent of carve-out IT separation delays trace to identity, integrations, and undocumented application dependencies rather than raw data transfer (source: Gartner research, 2026). This is why experienced separation teams frontload discovery. You cannot schedule what you have not mapped.
The migration itself is the easy 20 percent. The 80 percent that kills timelines is discovering what actually connects to what, especially the integrations nobody documented because the parent company built them years ago.
Ryan Loiacono, Founder, Untapped Connections
A practical rule of thumb from PortMux carve-out data: allocate one third of the total window to discovery and planning, one third to build and test, and one third to migration waves and stabilization. Compressing the discovery third to save time is the most common and most damaging shortcut.
The Phases of a TSA Migration Timeline
A TSA migration timeline breaks into five sequential phases: discovery and dependency mapping, target design, build and configuration, migration waves, and cutover with decommission. Each phase has a clear exit criterion, and skipping ahead before the prior phase is genuinely complete is the leading cause of failed cutovers and last-minute extensions.
Phase 1: Discovery and dependency mapping (months 1 to 3)
Inventory every application, data store, integration, and identity dependency tied to the parent. Document data volumes, compliance requirements, and which systems the business truly needs versus what can be retired.
Phase 2: Target state design (months 2 to 4)
Design the standalone architecture: which systems move as-is, which get replaced with SaaS equivalents, and how identity, email, and networking will be rebuilt independently.
Phase 3: Build and configuration (months 3 to 7)
Stand up the target environment, configure new tenancy, and build integrations. This phase runs long and overlaps with testing.
Phase 4: Migration waves and testing (months 5 to 10)
Move data and applications in prioritized waves, validating each before proceeding. Run parallel operations where risk demands it.
Phase 5: Cutover and decommission (months 9 to 12)
Execute final cutover, confirm the business runs entirely on standalone systems, and formally exit the TSA before the deadline. Poorly planned data migrations fail or overrun budget in as many as 83 percent of cases (source: Gartner research, 2026), which underscores why phased, criteria-gated execution matters.
Approach Comparison: Migration Strategies for PE Carve-Outs
There are four common approaches to a carve-out TSA migration, and the right one depends on your TSA runway, data complexity, and appetite for risk. Lift-and-shift is fastest but carries technical debt, while a full re-platform is cleanest but slowest. Most successful PE carve-outs use a hybrid, migrating critical systems first and modernizing selectively.
| Approach | Timeline | Risk | Best For |
|---|---|---|---|
| Lift and shift (rehost as-is) | 4 to 7 months | Medium | Short TSA windows and clean, separable systems |
| Re-platform to SaaS | 9 to 15 months | Medium to high | Portfolios planning bolt-ons and long-term modernization |
| Hybrid (migrate critical, modernize selective) | 6 to 12 months | Medium | Most mid-market PE carve-outs |
| Extend TSA and delay | Ongoing | High (cost) | Emergency fallback only, never a primary plan |
The hybrid approach dominates in PortMux carve-out engagements because it balances the TSA deadline against the temptation to modernize everything at once. Trying to re-platform the entire estate inside a nine month TSA is how deals blow through both timeline and budget. Move first, modernize after you are safely off the parent.
The global data migration market is projected to exceed 46 billion dollars by 2032, growing at roughly 20 percent annually (source: Fortune Business Insights, 2026), reflecting how much of enterprise IT work is now movement rather than net-new build.
Step-by-Step: How to Build a Reverse TSA Timeline
The most reliable way to plan a carve-out migration is to build the timeline backward from the TSA exit date, not forward from close. This forces every milestone into a deadline-driven sequence and immediately exposes whether your runway is realistic. Here is the process PortMux recommends for portfolio companies in the first 30 days after close.
- Confirm the hard TSA exit date and any extension terms. Read the agreement carefully for notice periods, extension fees, and service-specific end dates that may differ from the master date.
- Anchor the exit date and subtract a buffer. Set your internal target 4 to 6 weeks before the contractual deadline to absorb slippage.
- Work backward through the five phases. Assign end dates to cutover, migration waves, build, target design, and discovery, in that reverse order.
- Stress-test the discovery window. If discovery cannot start within 30 days of close, your entire schedule is already compressed; escalate immediately.
- Fund and name a dedicated separation lead. Do not layer migration onto existing IT staff who are running the business.
- Lock milestone gates with go/no-go criteria. No phase begins until the prior phase meets its exit checklist.
This reverse method surfaces timeline risk in week one instead of month five. If the math does not work, you learn it while you still have options: negotiate a longer TSA up front, add resources, or reduce migration scope.
What Drives the Cost of a TSA Migration?
TSA migration cost is driven primarily by application count, data volume, integration complexity, and the duration of parallel running, not by revenue size alone. A mid-market carve-out typically spends 250,000 to 2,000,000 dollars on the separation program, and the largest single variable is how long the company keeps paying TSA service charges while it migrates.
The cost equation has two sides that pull against each other. Moving faster costs more in project resources but less in TSA charges. Moving slower saves on the project but bleeds EBITDA through monthly service fees and risks triggering extension penalties. The optimal point is exiting cleanly a few weeks before the deadline.
- TSA service charges: the monthly cost of the parent running your systems, often marked up above cost.
- Extension fees: commonly 125 to 200 percent of the base monthly charge, designed to be punitive.
- Migration labor and tooling: internal separation team plus specialists and migration software.
- New standalone infrastructure: cloud tenancy, SaaS licenses, and identity systems.
Every month you sit on a TSA past your realistic exit date is a month you are financing the seller's mark-up out of your own returns. The math almost always favors investing in a faster, cleaner exit.
Ryan Loiacono, Founder, Untapped Connections
PortMux advises modeling both the project cost and the cumulative TSA burn side by side, because sponsors who only look at the project budget consistently underinvest and then overpay through extended service charges.
How PortMux Approaches Portfolio Carve-Out Migrations
PortMux approaches carve-out TSA data migration timeline planning by anchoring every program to the exit date, frontloading discovery, and running data, applications, infrastructure, and identity as coordinated parallel workstreams. The goal is a predictable, milestone-gated program that exits the TSA on schedule while positioning the portfolio company for future bolt-ons.
The methodology starts with a rapid dependency map in the first 30 days, because unmapped integrations are the number one cause of blown timelines. From there, PortMux builds the reverse schedule, identifies the critical path (usually identity and email), and sequences migration waves so the highest-risk systems are validated earliest, not left for the final scramble.
Companies that begin separation planning within 30 days of close are significantly more likely to exit their TSA on time than those that wait (source: PortMux research, 2026). Speed of start, not size of team, is the differentiator PortMux sees repeatedly across portfolio engagements.
For PE sponsors managing multiple portfolio companies, a repeatable separation playbook compounds in value. Each carve-out refines the templates, dependency checklists, and vendor relationships, turning a one-off crisis into an operational muscle. That repeatability is where PortMux focuses, so the second and third carve-outs move faster and cost less than the first.
Bottom Line
A TSA data migration timeline in a PE portfolio is a value-protection deadline disguised as an IT project. The Transition Services Agreement sets a hard exit date, and the firms that hit it consistently do three things: they start discovery within 30 days of close, they build the schedule backward from the exit date, and they fund a dedicated separation lead instead of overloading existing staff. The technical migration is rarely the constraint. Discovery, identity, and undocumented dependencies are.
Most mid-market carve-outs run 6 to 12 months and cost 250,000 to 2,000,000 dollars, with extension fees of 125 to 200 percent waiting for anyone who misses the deadline. Treat the TSA clock as the immovable object it is, plan against it early, and never make an extension your primary fallback. PortMux research shows that early, deadline-anchored planning is the clearest path to exiting on schedule and protecting the deal thesis.