Carve-out of two listed multinationals

What we walked into.

Years of shared infrastructure, shared addressing, shared identity and shared operations, with a legal deadline that does not move.

Everything that was convenient while the companies were one becomes a liability the moment they are two. Separation had to be complete, auditable and invisible to end users.

The approach.

1. Step 1

   Mapped every dependency between the two estates: routing, DNS, identity, datacenter services, security policy and third-party links.

2. Step 2

   Rebuilt the network layer rather than splitting the old one, so each company ended up with a clean, modern foundation instead of half a legacy design.

3. Step 3

   Ran the cutovers in coordinated waves, with both sides operating in parallel until each dependency was proven cut.

Stack and disciplines.

What it delivered.

Two fully independent estates, each with its own network, security perimeter and operating model.

A refreshed network layer on both sides, which turned a compliance exercise into a genuine upgrade.

Lessons that travel.

• Rebuilding beats splitting. Cutting a legacy design in half leaves both sides with half a legacy design.

• Dependencies hide in third-party links and forgotten DNS entries, so you map before you promise a date.

• Parallel running is the only safe way to prove a dependency is truly cut.