Salesforce orgs split by configuration, not by command line.

Org inventory and target org strategy.

Salesforce separation starts with a complete org inventory. The production org. The sandboxes covering Developer, Developer Pro, Partial Copy, and Full Copy. The cloud editions in use covering Sales Cloud, Service Cloud, Marketing Cloud, Experience Cloud, Commerce Cloud, Revenue Cloud, and Salesforce Industries. The package install footprint covering managed packages, unmanaged packages, and unlocked packages. The customizations covering Apex classes, Apex triggers, Visualforce pages, Lightning Web Components, Flows, and Process Builder.

The seller typically runs one production org covering multiple business units. Newco data sits as accounts, contacts, opportunities, cases, and custom records associated with Newco business units, record types, or page layouts. The separation extracts Newco data and rebuilds it in a new org that Newco contracts directly with Salesforce. Salesforce does not provide an in place org split as a standard service. The result is a configured new org with selective data migration.

Target org strategy is shaped by carve out timeline and Newco operating model. A clone approach takes a sandbox refresh of the seller production, removes seller data, and converts to a new org. A greenfield approach implements a new org with a target data model and selective data migration. A hybrid approach combines both, taking the seller configuration as a baseline and rebuilding what does not fit.

A clean inventory and target strategy decision unlocks every downstream Salesforce decision. The licensing structure. The configuration migration approach. The data migration plan. The integration redesign. The pattern aligns with the TSA exit IT separation sequence and the broader carve out IT plan.

Licensing and the Salesforce commercial.

Salesforce licensing is structured around user licenses by edition and add ons. Sales Cloud, Service Cloud, and the optional clouds carry separate license counts. The seller agreement does not transfer in a carve out. Newco signs a direct subscription with Salesforce covering the editions in scope, the user count, and the sandbox count. The negotiation is a one shot opportunity. Salesforce reads the situation as a captive buyer with carve out timing pressure.

The preparation covers user counts by license type, add on selection covering CPQ, Field Service, Pardot, and the Marketing Cloud tools, sandbox counts, and the BATNA. Where Newco can credibly select a different CRM platform such as HubSpot or Microsoft Dynamics 365 Sales, the negotiation has leverage. Where Newco has chosen to stay on Salesforce to preserve sales productivity, leverage comes from the commercial structure including term length, price holds, and ramp schedules.

Implementation services are the second commercial. Newco selects a Salesforce Summit or Crest Consulting Partner. Selection criteria include carve out experience, fixed-fee willingness, senior team continuity through the program, 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 org 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 subscription costs that the seller is not actually incurring. The audit discipline runs through the TSA audit rights framework.

Org build and configuration migration.

Org build is the central engineering activity. The implementation partner provisions the new Newco org and configures it from a baseline Salesforce template. The data model, the record types, the page layouts, the validation rules, the security model, and the user provisioning 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 Apex classes, Apex triggers, Visualforce pages, Lightning Web Components, Flows, and Process Builder flows. The customizations are packaged using Salesforce DX, unlocked packages, or change sets and deployed to the Newco org. Where customizations were authored without good versioning discipline, the migration becomes a code review exercise that has to be planned and budgeted explicitly. Process Builder flows that have been deprecated by Salesforce are rebuilt as Flow Builder flows during the migration.

Profile and permission set configuration are the most consequential pieces from a security perspective. The Newco profiles are rebuilt with explicit permissions, restricted field level security, and approval routings. Sharing rules and role hierarchy are configured to match the Newco organizational structure. A security configuration error is the most common source of post go live remediation work.

Reporting and analytics migrate through reports, dashboards, and CRM Analytics datasets. Where the seller used external reporting tools that connect to Salesforce via APIs, those connections are rebuilt in the Newco org with new credentials and refreshed data models.

Data migration and integration redesign.

Data migration covers accounts, contacts, opportunities, cases, custom records, attachments, files, and historical activity. Salesforce data migration uses Data Loader, Bulk API, or third-party tools. The sequence loads master data first followed by transactional records. Each domain has a defined extract, transform, and load process with data quality checks and reconciliation reports against the seller source.

Record ID continuity is the technical challenge. Salesforce assigns new record IDs at insert time. The migration preserves cross record relationships through external ID fields and lookup remapping. Activity history, email logs, and file attachments are migrated with the parent records. Where activity history exceeds the migration window economic threshold, the older activity is archived rather than migrated.

Integrations are the workstream that most carve outs underestimate. Salesforce connects to dozens of third-party systems. The marketing automation platform, the ERP for order management, the CPQ tool if separate, the contract management system, the e-signature platform, the data enrichment provider, the dialer and conversation intelligence tools, and the customer service platforms. Each integration is inventoried, tested, and rebuilt in the Newco environment using middleware or direct API connections.

Identity integration is the final piece. The Newco org authenticates against Newco identity provider through SAML or OIDC. User provisioning maps from Newco directory groups into Salesforce profiles and permission sets. The identity boundary is locked before sales team training begins so that test users have the right downstream access.

Cutover, sales continuity, and stabilization.

Cutover is the window where the sales team and the service team move from the seller org to the Newco org. The window is typically planned for a weekend with a defined freeze on data updates in the seller org Friday afternoon and Monday morning go live in Newco. The runbook covers data freeze, final delta migration, user notification, integration cutover, and assignment rules activation. The runbook is rehearsed twice before the actual cutover.

Sales continuity is the most sensitive piece. The pipeline data migrates with stage assignments and forecast categories preserved. Open opportunities continue to progress in the new org without re entry of deal information. Marketing automation continuity is preserved through dual write during the transition window where possible. The user adoption plan covers training, quick reference guides, and embedded support during the first two weeks.

Service team continuity is preserved through case migration with status, owner, and customer associations intact. Knowledge articles migrate after review for content relevance. SLAs and entitlements are configured before go live so that incoming cases route correctly from minute one.

Stabilization runs for 60 to 90 days. The first month of new pipeline activity in the new org is the gate that confirms steady state. Production issues get triaged within defined service-level commitments. The TSA exit certification for CRM services follows successful stabilization. The discipline runs through the TSA exit milestones framework.

Cost discipline and where carve outs go wrong.

Salesforce separation programs run between $500K and $4M depending on cloud scope, customization volume, integration count, and data volumes. The cost dispersion reflects the platform breadth. The economic discipline is to scope tightly to required clouds, 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 managed package re entitlement, custom code refactoring, and integration discovery. The fix is the disciplined inventory before contract signing, the early package vendor outreach for re entitlement quotes, 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 late identification of integration ownership, delays in marketing automation re entitlement, and unclear data scope for activity history. 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. Salesforce supports the revenue operating model. Delays propagate to forecast accuracy.

A clean Salesforce separation produces a Newco that runs its own org with licensed entitlements, supported customizations, and the optionality to evolve the revenue 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.