IT separation for a divestiture
A divested business separated from its former parent's technology: every dependency identified, day-one needs defined, and the exit sequenced.
Project type
Mergers and acquisitions — IT separation
Practice
IT strategy
Where it reached
- People
- Process
- Information
- Technology
Where they started
A divestiture meant a business that had run on its parent’s technology now needed its own.
What we did
- Separation plan. Identified every system, contract and data set the divested business depended on.
- Stand-up. Defined the systems and IT function the new business needed on day one.
- Exit. Sequenced the move off the parent’s systems.
What changed
A clear path to independence: every dependency known, the new business’s day-one needs defined, and the exit from the parent’s systems planned in order.
Want a result like this?
Bring the situation you are in. We will tell you where we would start, and whether it is worth doing now.