SD-WAN rollout across 750+ offices

What we walked into.

More than 750 offices on four continents, each with its own carrier contract, its own local quirks and its own idea of what the network should do.

Every site had to keep running while it was being replaced. No maintenance window big enough exists for an estate this size, so the migration had to be designed as a rolling operation rather than a cutover.

The approach.

1. Step 1

   One reference design, templated to the site level, so that a small office in a shopping street and a regional headquarters both come out of the same factory.

2. Step 2

   A repeatable rollout pipeline: site survey, circuit ordering, zero touch provisioning, remote cutover, validation, handover. Every step measurable, every step owned.

3. Step 3

   Central policy and routing control, so security and traffic engineering changes land everywhere at once instead of site by site.

Stack and disciplines.

What it delivered.

A single global fabric under one policy, with new locations joining in days instead of months.

Lower telecom spend as expensive legacy circuits fell away, and application performance that operations teams can actually see.

Lessons that travel.

• Templates beat heroics. The moment a rollout depends on a clever engineer improvising per site, the schedule is gone.

• Local carriers set the pace, so circuit ordering starts long before the first cutover.

• Validation is part of the migration, not a phase afterwards.