NetSuite OneWorld looks tidy. The TSA exit is still a configured rebuild.

Account inventory and the OneWorld scope.

NetSuite separation starts with an account inventory. The production account. The sandbox accounts. The OneWorld subsidiary structure where applicable. The modules in use covering Financials, Inventory, Order Management, CRM, SuiteAnalytics, SuitePeople, and SuiteCommerce. The customizations covering SuiteScript, SuiteFlow, custom records, custom fields, saved searches, and workflows. The role permissions, the segregation of duties controls, and the user provisioning model.

In a OneWorld account the seller runs multiple subsidiaries inside a single tenant. Newco subsidiaries sit inside that structure with shared chart of accounts segments, shared item masters, shared customers, and shared vendors. The separation extracts Newco subsidiaries cleanly while preserving transactional integrity and tax filing continuity. NetSuite does not support an in place subsidiary spin out as a standard service. The result is a configured rebuild on a new Newco account with selective data migration.

The scope boundary defines what Newco takes and what stays. Newco subsidiary transactions move with Newco. Shared master data including customers, vendors, and items is filtered and rebuilt. Customizations that benefit Newco move with Newco. Customizations that only serve the seller stay. The boundary is finalized in the first 30 to 45 days of the runway and reflected in the data migration design and the role configuration.

A clean inventory and boundary decision unlocks every downstream NetSuite decision. The account licensing strategy. The customization migration approach. The integration redesign. The first close in the new account. The pattern aligns with the TSA exit ERP separation framework and the carve out finance plan.

Licensing and the new account commercial.

NetSuite licensing is straightforward in shape. Oracle NetSuite sells subscription seats by module with a base account fee and add on modules. The seller agreement does not transfer. Newco signs a direct subscription covering the modules in scope, the user count, and the sandbox count. The negotiation is a one shot opportunity. Oracle NetSuite reads the situation as a captive buyer with carve out timing pressure.

The preparation covers user counts by role, module selection, add on tools in use such as SuiteBilling, SuiteProjects, and SuitePromotions, and the BATNA. Where Newco can credibly select a different ERP platform such as Sage Intacct or Microsoft Dynamics 365 Business Central, the negotiation has leverage. Where Newco has chosen to stay on NetSuite to compress the carve out timeline, leverage is thin and has to come from the commercial structure.

Implementation services are the second commercial. Newco selects a SuiteCloud Alliance Partner from the NetSuite ecosystem. Selection criteria include carve out experience, fixed-fee willingness, senior team continuity, and clean contractual remedies for delay. The implementation contract is fixed fee for defined deliverables with disciplined change control. Hourly time and materials is not the engagement model.

Where the seller is willing to extend account access through a TSA period, the TSA pricing is negotiated to a cost-plus or fixed-fee structure with a defined exit ramp. The seller cannot bill Newco a mark-up on NetSuite subscription costs that the seller is not actually incurring. The audit discipline runs through the TSA vendor cost pass-through audit framework.

Account build and customization migration.

Account build is the central engineering activity. The implementation partner configures the new Newco account from a baseline NetSuite template. The chart of accounts, the subsidiary structure, the accounting periods, the tax codes, the item master schema, the customer and vendor records, the price levels, and the locations are configured to match the Newco operating model. The configuration mirrors the seller where appropriate and adjusts where Newco operating decisions diverge.

Customization migration covers SuiteScript code, SuiteFlow workflows, custom records, custom fields, saved searches, and KPIs. The customizations are packaged using SuiteCloud Development Framework and deployed to the Newco account. Where customizations were authored without SDF discipline, the migration becomes a code archaeology exercise that has to be planned and budgeted explicitly. The pattern is consistent across NetSuite separation programs.

Role configuration and segregation of duties are the most consequential pieces from an audit perspective. The Newco roles are rebuilt with explicit permissions, restricted record access, and approval routings. SOX controls are tested against the new role configuration before user provisioning. A role configuration error is the most common source of post go live remediation work and audit findings.

Reporting and analytics migrate through saved searches, datasets, and SuiteAnalytics workbooks. Where the seller uses external reporting tools that connect to NetSuite via ODBC or RESTlets, those connections are rebuilt in the Newco environment with new credentials and refreshed data models.

Data migration and integration rebuild.

Data migration covers master data, open transactions, and historical balances. Master data first. Customers, vendors, items, employees, chart of accounts, and locations. Each domain has a defined extract, transform, and load process using CSV imports or SuiteTalk APIs with data quality checks and reconciliation reports. Master data migrates before transactions because transactions reference it.

Open transactions migrate next. Open sales orders, open purchase orders, open work orders, open inventory transfers, open invoices, and open receivables. The transactions are loaded with original document dates, amounts, and references so that aging reports remain accurate. Historical transactions typically migrate as opening balance journals rather than line level transactions. The historical detail stays in a read only export available for audit and tax inquiries.

Integrations are the workstream that most carve outs underestimate. NetSuite connects to a wide third-party landscape. The CRM if separate, the EDI provider, the bank for cash management, the payroll provider, the expense tool, the e-commerce platform, the warehouse management system, and the tax engine. Each integration is inventoried, tested, and rebuilt in the Newco environment using SuiteTalk, RESTlets, or middleware. The integration rebuild is sized in the original scope, not discovered late.

Identity integration is the final piece. The Newco account authenticates against Newco identity provider through SAML 2.0. User provisioning is mapped from Newco directory into NetSuite roles. The identity boundary is locked before financial close testing begins so that test users have the right downstream access. The pattern aligns with day one identity readiness planning.

Close parallel, cutover, and hypercare.

The financial close is the gate on the NetSuite separation. The first Newco close has to land accurately, on time, and with correct intercompany eliminations and tax reporting. The path runs through configuration validation, mock month end runs, parallel closes against the seller production, and a final cutover decision. Each parallel close compares trial balance, P&L, and balance sheet to the seller output and reconciles the variance.

One to two parallel closes are typical. The first parallel identifies configuration gaps, mapping errors, and integration mismatches. The second parallel validates the fixes and confirms readiness for cutover. Where variance persists after two parallels, the carve out PMO and the controller decide whether to extend the TSA period or accept controlled go live with manual reconciliation.

Cutover is the window where transactions move from the seller account to the Newco account. The window is typically aligned to a month end or quarter end to simplify financial reporting. The cutover runbook covers transaction freeze, balance migration, opening balance loads, integration switching, and the first day of new transaction processing. The runbook is rehearsed twice before the actual cutover.

Hypercare runs for 30 to 60 days. The first two month end closes in the new account are the gate that confirms steady state operation. Production issues get triaged within defined service-level commitments. The TSA exit certification for finance services follows successful close of the second month end. The discipline runs through the TSA exit milestones framework.

Cost discipline and where carve outs go wrong.

NetSuite separation programs run between $400K and $3M depending on scope, customization volume, and integration count. The cost dispersion is narrower than ERP heavyweights because the platform is more standard and the implementation effort is more predictable. The economic discipline is to scope tightly to required modules, hold the implementation partner to fixed fee, and avoid customization migration that does not serve the Newco operating model.

The most common cost overruns trace to customization recreation, integration discovery, and undocumented saved searches. The fix is the disciplined inventory before contract signing, the early customization discovery phase that scores each customization on business value and complexity, and the change control process that prices every scope addition in writing. Where these controls are in place, the program lands within the original budget plus or minus 10 percent.

The most common timeline overruns trace to delayed master data extracts, late confirmation of integration redesign decisions, and unclear ownership of the chart of accounts mapping. The fix is the explicit dependency map maintained by the PMO with named owners on both sides and a weekly governance rhythm that escalates blocks within 48 hours. The pattern aligns with carve out 100 day plan governance.

A clean NetSuite separation produces a Newco that runs its own account with licensed entitlements, supported customizations, and the optionality to evolve the finance operating model on Newco timeline. The discipline runs through the TSA exit acceleration program and is delivered under a Fixed Fee + Portfolio Retainer engagement model.

More on platform separation.