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.
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
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.
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.
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.
Define tests
Write a test list per service: internet, Wi-Fi, phones, cameras, payments, VPNs, critical applications. Test from real user devices.
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.
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.
Execute and verify
Follow the run sheet, tick tests as they pass, and keep a log of times and issues.
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.
FAQ
Frequently asked questions
How long should the maintenance window be?
Plan the work plus testing plus the full rollback time, with margin. If rollback takes an hour, the window must allow for it.
What is the most common cut-over failure?
Something undocumented: a forgotten static route, VLAN, port setting or device that nobody knew depended on the old network.
Keep learning
Related guides
Safe network change pipeline
Read more →Document and label a network
Read more →Back up and restore configurations
Read more →How to Plan and Justify an IT Network Budget (With a Free Calculator)
A step-by-step method for CTOs and IT managers to build a network budget: inventory, sizing, one-time and recurring costs, contingency and a business case management will approve. Includes a free budget calculator.
Read more →How to Compare Total Cost of Ownership: Cloud-Managed vs On-Premises Network Management
Price per device is only part of the cost. Compare 5-year total cost of ownership for cloud-managed and on-premises controllers: hardware, licences, staff time, downtime and travel.
Read more →How to Plan a Network Refresh and Hardware Lifecycle
Old switches, access points and firewalls are slower, less secure and eventually unsupported. Build a lifecycle plan that spreads replacements over years instead of emergencies.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.