Private equity · Carve-outs
A carve-out is a new company with a deadline.
It needs its own systems, its own data and its own reporting before the transition window closes. BSP plans the NetSuite side of the separation with the deal team, starts building before close, and runs the program through the first month-end.
TYPICAL CONSTRAINTS
FIXED TSA WINDOW · PARENT-HOSTED ERP · SHARED SERVICES · LEAN FINANCE TEAM
BSP APPROACH
BUILD DURING EXCLUSIVITY · SYSTEM INTEGRATOR + ERP PMO · REPORTING FROM FIRST CLOSE
RECOGNITION
2025 NETSUITE PE SPOTLIGHT · CARVE-OUT
The separation
More leaves the parent than the ERP.
Most carve-outs are scoped as a system migration. In practice, five things have to separate at once, and the ERP is where all of them meet.
Systems
The parent-hosted ERP, and every integration, portal and report that depended on it.
Data
History, open transactions and master records, extracted from an environment you no longer control and cleaned before they arrive.
Processes
Shared services the parent ran, from AP and procurement to approvals, now rebuilt for a smaller, standalone team.
Reporting
Lender, sponsor and regulatory reporting that has to work from the first close, not the third.
Ownership
A system the new company configures, pays for and changes on its own terms, with no access fees or dependency on a former parent.
Day One readiness
What has to be true the morning after close.
This is the standard we plan a carve-out against. If any line isn’t true on Day One, the business is still depending on its former parent, whatever the TSA says.
01 A standalone NetSuite account the new company owns
02 Entity and subsidiary structure built for add-ons
03 Chart of accounts designed for sponsor reporting
04 Opening balances, open AR and open AP migrated and reconciled
05 Customer, vendor and item records cleansed and loaded
06 Banking, payments and approvals working without the parent
07 Integrations to operational systems live, not deferred
08 User roles and controls in place for a smaller team
09 Lender and sponsor reporting package tested
10 A dated plan for the last day of parent system access
How we run it
01 · EXCLUSIVITY
Scope and architect
Map the TSA, the parent dependencies and the reporting the sponsor and lender need. Design the entity structure and start the build.
02 · BUILD
Configure and connect
Configure NetSuite, rebuild approvals, build integrations in parallel, and run test data loads that finance validates before anything is final.
03 · CUTOVER
Separate
Final production migration, user training and go-live, timed against the last day of parent system access rather than a project plan.
04 · FIRST CLOSE
Prove it
Support through the first month-end and the first lender package, then hand over to Operis managed services so the system keeps improving.
A point of view
Where carve-outs go wrong.
Carve-outs rarely fail because the software can’t do the job. They fail on sequencing, scope and time, and most of those failures are decided before the build begins.
Starting after close
A TSA measured in months leaves no slack for selection, design, migration and testing. The time you can recover is the time before the deal closes.
Rebuilding the parent
A carve-out needs a system sized for the business it has become, not a copy of the enterprise it left.
Leaving integrations for Phase 2
If an operating platform depends on the ERP, the integration is part of Day One. Deferring it means the separation works on paper and fails in operations.
Treating data as a final step
Migration from an environment you no longer control needs test loads and finance sign-off early, not a single weekend at the end.
Making ERP an IT workstream
In a carve-out, the ERP decides whether the company can report to its lender. It belongs on the deal plan, with the deal team.
“Our SAP environment was managed through our former parent organization, which meant our access to the system had a defined end date we needed to hit. There wasn’t a lot of room for delays. Staying on SAP past that window was going to cost us money every month we remained.”
Steve Yochum · Chief Executive Officer, Vault CPS
In practice
Two carve-outs, two exit windows met.
VAULT CPS · 6-MONTH SAP EXIT
Operational in six months.
Out of Ingram Micro’s SAP environment on time and 12.1% under budget, with a proprietary platform integrated from day one.
TRP LABORATORIES · ≤90-DAY TSA
Operational on Day One.
Separated from a $20B+ parent’s Oracle ERP, with the build started during a 60-day exclusivity window.
Common questions
What sponsors and CFOs ask us first.
How long does a NetSuite carve-out take?
The transition window usually sets the timeline, not the software. Our recent carve-outs worked to a TSA of 90 days or less and a six-month SAP exit. What’s achievable depends on scope, integrations, data quality and, above all, how early the work starts.
Can work begin before the deal closes?
Yes, and it should wherever the deal allows. At TRP Laboratories, implementation began during a 60-day exclusivity window, so the business could operate independently the day the deal closed.
Should we replicate the parent’s ERP setup?
Usually not. The parent’s system was built for a different company. We match the capabilities the business depends on and leave behind the complexity it doesn’t need.
Does the new company need its own NetSuite environment?
To be independent, yes. The business should own its account, configuration and data outright, rather than depend on any part of a former parent’s infrastructure.
What happens after go-live?
We support the first month-end close and the first lender and sponsor reporting cycle, then move the account to Operis managed services, with named people who keep improving the system as the business grows.
The best time to plan Day One is before you sign.
Share the transaction, the TSA terms and the systems the business depends on today. We’ll map what the separation involves and what it would take to hit the date.