ServiceNow runs the IT operating model. It cannot stay with the seller.

Instance inventory and target architecture.

ServiceNow separation starts with a complete instance inventory. The production instance. The sub production instances for development, testing, and training. The platform modules in use covering ITSM, ITOM, ITAM, IRM, HRSD, CSM, SecOps, and the Now Platform App Engine where applicable. The CMDB schema and data. The customizations covering business rules, client scripts, UI policies, workflows, Flow Designer flows, and scoped applications. The integrations to monitoring, security, identity, and procurement systems.

The seller typically runs one production instance covering many business units. Newco data sits inside that instance as records associated with Newco companies, locations, and business services. The separation has two architecture patterns. Domain separation inside the existing seller instance during a TSA period, where Newco data is logically segregated by domain. New Newco instance after TSA, where Newco operates its own ServiceNow with migrated configuration and data.

Domain separation is a useful pattern for the TSA bridge. It restricts visibility, separates reporting, and supports a TSA service catalog with explicit access scopes. It is not a long term operating answer because Newco depends on the seller for platform governance, upgrades, and admin access. The target end state is a Newco instance under Newco contract and Newco governance.

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

Licensing and the ServiceNow commercial.

ServiceNow licensing is structured around fulfiller users, requesters, and platform packages. The seller agreement does not transfer. Newco signs a direct subscription covering the modules in scope, the fulfiller user count, and the sub production instance count. The negotiation is a one shot opportunity. ServiceNow reads the situation as a captive buyer with carve out timing pressure.

The preparation covers fulfiller user counts by role, module selection, custom table count, and the BATNA. Where Newco can credibly select a different ITSM platform, the negotiation has leverage. Where Newco has chosen to stay on ServiceNow to compress the carve out timeline, leverage comes from the commercial structure including term length, price holds, ramp schedules, and pre committed implementation credits.

Implementation services are the second commercial. Newco selects a ServiceNow Elite or Premier 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 provides ServiceNow services through a TSA bridge, 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 vendor cost pass-through audit framework.

Instance build and configuration migration.

Instance build is the central engineering activity. The implementation partner stands up the new Newco instance and configures it from a baseline ServiceNow template. The ITSM process configuration covering incident, problem, change, request, and knowledge is rebuilt to match the Newco operating model. The service catalog, the SLA definitions, the priority matrix, and the assignment rules are configured. The configuration mirrors the seller where appropriate and adjusts where Newco operating decisions diverge.

Customization migration covers business rules, client scripts, UI policies, ACL rules, scoped applications, workflows, and Flow Designer flows. The customizations are packaged using update sets or scoped application exports and deployed to the Newco instance. Where customizations were authored without good versioning discipline, the migration becomes a code review exercise that has to be planned and budgeted explicitly. The pattern is consistent across ServiceNow separation programs.

Role configuration and ACL rules are the most consequential pieces from a security perspective. The Newco roles are rebuilt with explicit permissions, record level access, and approval routings. Audit 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.

Reporting and dashboards migrate through Performance Analytics indicators, dashboards, and reports. Where the seller used external reporting tools that connect to ServiceNow via REST APIs, those connections are rebuilt in the Newco instance with new credentials and refreshed data models.

CMDB rebuild and integration redesign.

The CMDB is the single most underestimated piece of a ServiceNow separation. The Newco CMDB needs to reflect Newco infrastructure, applications, and business services with accurate ownership, relationships, and lifecycle states. The data does not transfer cleanly from the seller because the seller CMDB describes seller infrastructure. The Newco CMDB is rebuilt through discovery, service mapping, and curated import.

The rebuild sequence starts with the CMDB classes that matter most for ITSM operations. Servers, databases, applications, business services, and locations. ServiceNow Discovery scans the Newco infrastructure and populates the configuration items. Service Mapping correlates the items into business services. The result is a CMDB that supports change risk assessment, incident routing, and impact analysis from day one.

Integrations are the workstream that most carve outs underestimate. ServiceNow connects to dozens of systems. Monitoring tools, security tools, the identity provider, HR for onboarding, procurement for asset acquisition, the project portfolio management tool, the directory for assignment groups, and the email gateway for notification handling. Each integration is inventoried, tested, and rebuilt in the Newco environment using IntegrationHub spokes, REST messages, or middleware.

Identity integration is the final piece. The Newco instance authenticates against Newco identity provider through SAML or OIDC. Assignment groups are mapped from Newco directory groups. The identity boundary is locked before incident migration begins so that the right people own the right tickets at cutover.

Data migration, cutover, and stabilization.

Data migration covers open records and historical records. Open incidents, open changes, open problems, open requests, and open knowledge articles migrate using ETL into the new instance. Historical records typically migrate as an archive that Newco can query but does not actively process. The archive approach reduces migration scope while preserving the data for audit and trend analysis. The migration is sequenced to minimize disruption to the IT operations team.

User accounts, groups, and assignment rules migrate with the role configuration. Knowledge base articles migrate after review for content relevance. Where seller knowledge contains references to seller specific systems or processes that no longer apply to Newco, the articles are filtered or rewritten before import.

Cutover is the window where IT operations move from the seller instance to the Newco instance. The window is typically planned for a weekend with a defined freeze on new tickets in the seller instance Friday afternoon and Monday morning go live in Newco. The runbook covers user notification, ticket migration, integration cutover, and assignment group activation. The runbook is rehearsed twice before the actual cutover.

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

Cost discipline and where carve outs go wrong.

ServiceNow separation programs run between $800K and $5M depending on module scope, customization volume, and CMDB complexity. The cost dispersion reflects the platform breadth. The economic discipline is to scope tightly to required modules, hold the implementation partner to fixed fee, and avoid configuration migration that does not serve the Newco operating model.

The most common cost overruns trace to CMDB rebuild scope expansion, undocumented business rules, and ITOM integration discovery. The fix is the disciplined inventory before contract signing, the early CMDB scope decision that defines which classes are in scope for day one, 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 identity integration, late confirmation of CMDB ownership decisions, and integration backlog with monitoring tools. 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. ServiceNow operates the IT operating model. Delays propagate.

A clean ServiceNow separation produces a Newco that runs its own instance with licensed entitlements, supported configuration, and the optionality to evolve the IT 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.