Hands-on tutorial

Tutorials · IT Leadership

How to Plan a Network Cut-Over Without Surprises

Replace a core switch, gateway or a whole site's network in one maintenance window: preparation, a minute-by-minute run sheet, test lists, go/no-go points and a tested rollback.

Intermediate10 min8 steps

Before you start

  • Current configurations and documentation
  • The new equipment configured and tested in advance
  • A maintenance window agreed with the business

Step by step

  1. Freeze and document the current state

    Back up every configuration, photograph the racks, record which device is in which port (LLDP and MAC tables help), and stop other changes before the cut-over.

  2. Pre-stage everything

    Configure and test the new devices on the bench with the real configuration. Label every cable you will move with its new port.

  3. Write a run sheet

    List each step with its owner, expected duration and check, in order. Include phone numbers for the ISP, vendors and site contacts.

  4. Define tests

    Write a test list per service: internet, Wi-Fi, phones, cameras, payments, VPNs, critical applications. Test from real user devices.

  5. Set go/no-go points

    Decide in advance when you will stop and roll back, for example if the core is not stable after 60 minutes.

  6. Prepare the rollback

    Keep the old equipment racked or at hand and cables labelled so you can return to the old state quickly. Rehearse it if the change is large.

  7. Execute and verify

    Follow the run sheet, tick tests as they pass, and keep a log of times and issues.

  8. Hand over and watch

    Monitor closely for the first business day, keep an engineer on call, and update documentation.

Pro tips

  • Two people: one executes, one checks and logs.
  • Communicate the window and expected impact to users in advance.
  • Never combine a firmware upgrade with a topology change unless you must.