Solutions / Separations & Carve-outs
For CIOs, CISOs, and separation management offices
XOPS reconciles fragmented systems into a clean Day-1 operating reality for each new entity.
Months of separation work collapse into days.
The separation reality
Every separation, carve-out, and divestiture runs on the same fragile assumption: that the systems of record agree. They don’t. The legal entity splits on Day 1. The operational state doesn’t. Access persists where it shouldn’t. Customer data ends up where it shouldn’t. And the consulting firm fills the gap with people in spreadsheets.
Workday and SuccessFactors run payroll just fine. They don’t track who actually sits where, which contractors report through which manager, or which interim transfers were never reconciled. Good enough for payroll. Not good enough when a regulator asks who works for whom on the day of close.
Devices in Intune. Software in Flexera. Mobile lines in the telecom-expense system. Seats in IWMS. Vendor contracts in Coupa. Nobody owns the join. The split happens in CSV, one column at a time — and the entitlements, contracts, and assets that get stranded show up later as audit findings on the wrong NewCo’s books.
EY, Deloitte, and Accenture bring strong separation playbooks. The systems beneath them don’t agree — so every engagement begins with weeks of data reconciliation no one keeps. Senior judgment ends up buried under spreadsheet work that won’t survive Day 1.
Workday re-orged by hand. Fieldglass contractor records re-keyed. Okta and Entra ID groups rebuilt. AD security groups split. Every change is a ticket; every ticket is a chance to drift.
Every separation breaks at the seams between systems of record — where no system owns the full operational truth.
What XOPS coordinates
XOPS holds the reconciled state of every employee, contractor, asset, contract, and seat across the enterprise. The separation stops being a six-month data-reconciliation project. Your partner spends their time on judgment — not on spreadsheets that won’t survive Day 1.
1 · Reconcile the enterprise
Every employee, contractor, device, license, mobile line, vendor contract, seat, and conference room — reconciled against a single knowledge graph.
The physical world catches up to the cap table on Day 1.
2 · Execute Day-1 changes
Every operational system updates simultaneously, gated by Configuration-as-Code. NewCo employees onboard the morning of the split — with the right manager, the right cost center, the right access.
3 · Defensible audit trail
Every assignment carries who made it, what evidence supported it, and which approver signed. Defensible to regulators, to the TSA partner, and to the auditor six months after close.
The Day 1 test
Every employee walking into a new entity on Day 1 needs to know — without manual intervention — where they report, what their cost center is, what device is assigned to them, what software they have access to, and how to get support.
The platform makes that true.
In production today
Customer outcome · F500 enterprise mid-separation
Anonymized
A Fortune 500 enterprise preparing to split into two publicly traded entities asked HR for clean employee rosters. Workday came back self-graded at roughly 70% accuracy — fine for payroll, unusable for separation. Within an hour, XOPS reconciled eight systems of record into a defensible separation map for both NewCos — every person, asset, entitlement, and seat with provenance. Weeks of consulting scope collapsed into hours of platform work.
~70%
HR-reported Workday accuracy
< 1 day
Defensible separation map produced
8
Sources of state reconciled
2
Clean NewCos, full provenance
Day 1 and beyond
From Day 1 forward, each NewCo operates as its own clean entity. No shared identity surface. No commingled audit log. No customer or employee data drifting across the cap-table boundary. Both companies inherit a working operating model — not a six-month list of cleanup tickets.
TSA exit
Dependencies on the shared parent retire on a known schedule. Neither NewCo bleeds margin to TSA extensions.
No orphaned identities
Former colleagues at the other NewCo lose access on Day 1, not on memory. No long-tail accounts dangling in directory groups months later.
Audit defensibility
Each NewCo answers to its own regulators with its own audit trail. No reconciliation, no commingling, no inherited exposure.
Clean handoff
Both NewCos walk into Day 1 with a working operating model — not a half-finished migration. No “we’ll fix it after legal close.”
Day 1 becomes activation, not implementation.
For CIOs, IMOs, and separation programs
You still need a partner. You no longer need them to rebuild the data.
Accuracy guaranteed, not estimated. Defensible, not reconstructed.
