Enterprise LAN refreshes are one of the most significant infrastructure investments an organisation can make. They touch every user, every system, and every application across the business. Get one right and you have a network that performs reliably for a decade. Get it wrong and you’re looking at downtime, cost overruns, and a refresh that needs redoing within a few years.
Having worked across enterprise LAN refresh projects spanning multiple sites and continents, the same patterns of failure appear repeatedly — and almost none of them are technical. Here’s what goes wrong, and how to avoid it.
1. Treating It as a Hardware Swap Rather Than a Design Exercise
The most common mistake is framing a LAN refresh as a procurement exercise: identify the ageing switches, replace them with newer models, job done. This approach ignores the reason the network exists — to support the business applications and users that depend on it.
A LAN refresh is an opportunity to redesign the network from the ground up. That means understanding current traffic patterns, forecasting growth, identifying where the previous design caused bottlenecks, and making deliberate decisions about topology, redundancy, and segmentation before a single purchase order is raised.
Organisations that skip this step invariably inherit the problems of their old network on new hardware.
What to do instead: Begin every refresh with a network assessment. Document existing VLANs, uplink capacity, spanning tree behaviour, and any known pain points. Use that data to drive the design — not the other way around.
2. Underestimating the Wireless Component
Wired LAN and wireless LAN are rarely managed as a single unified project, and this disconnect causes significant problems. A brand new access layer with Category 6A cabling and high-density switching means very little if the wireless infrastructure feeding into it is five years old and undersized for current device density.
Modern enterprise environments often have more wireless devices than wired ones. Meeting rooms, open-plan offices, warehouses, and public-facing spaces all have their own density and coverage requirements. A LAN refresh that doesn’t include a proper wireless survey and redesign is leaving half the job unfinished.
What to do instead: Commission a professional wireless site survey as part of the LAN refresh scoping process. Predictive modelling and live survey data should inform access point placement, channel planning, and controller configuration — not rough estimates based on floor plans.
3. No Clear Cutover Plan
Enterprise networks run 24 hours a day. Production systems, telephony, security cameras, building management systems, and payment terminals all depend on the LAN being available. Yet many organisations begin a LAN refresh without a detailed cutover plan, assuming the work can be scheduled informally as it progresses.
The result is unplanned outages, missed migration windows, and last-minute decisions made under pressure that introduce configuration errors. In regulated industries, an undocumented outage can also create compliance problems.
What to do instead: Build a site-by-site cutover plan before the project begins. Identify every critical system on each network segment, define maintenance windows, communicate timelines to department heads, and assign clear rollback procedures in case a migration goes wrong. A LAN refresh without a cutover plan is not a plan — it’s a hope.
4. Buying the Wrong Platform for the Environment
Vendor selection is too often driven by existing relationships or procurement framework agreements rather than technical fit. The result is hardware that doesn’t match the operational environment — whether that’s a campus platform deployed in an industrial setting, a cloud-managed solution in a location with unreliable internet connectivity, or an on-premise stack that the internal team lacks the skills to operate.
There is no universal right answer when it comes to switching and routing platforms. The right platform depends on the environment, the team’s expertise, the existing management tooling, and the organisation’s five-year roadmap.
What to do instead: Evaluate platforms against documented requirements rather than commercial preference. Consider total cost of ownership including licensing, support, and operational overhead — not just the upfront hardware cost. If the internal team doesn’t have experience with the chosen platform, factor in training or specialist support from day one.
5. Inadequate Documentation at Handover
A LAN refresh that ends without comprehensive documentation is a project half-done. Yet documentation is consistently the element that gets deprioritised as projects run over time or budget.
Three to five years after a refresh, when a fault occurs at 2am or a new engineer joins the team, the value of accurate network documentation becomes immediately apparent. Without it, every troubleshooting exercise becomes an investigation. Configuration changes get made without a full picture of dependencies. And the next refresh starts from scratch rather than building on solid foundations.
What to do instead: Define documentation deliverables as a contractual requirement before the project begins. As-built diagrams, IP address plans, VLAN registers, switch configuration backups, and wireless heat maps should all be included. Handover is not complete until documentation is complete.
6. Ignoring Power and Physical Infrastructure
New switches frequently have different power and rack requirements compared to the equipment they replace. High-density access switches, PoE+ or PoE++ capable models, and new uplink modules can significantly increase power draw per rack — beyond what existing UPS units and PDUs were sized for.
Similarly, new cabling requirements, rack space constraints, and cooling changes are often discovered mid-project rather than during planning, causing delays and unexpected costs.
What to do instead: Conduct a physical infrastructure audit as part of the pre-project scoping. Verify rack space, power availability, UPS capacity, patch panel labelling, and cable plant condition before finalising the hardware specification. Surprises on this front are expensive and entirely avoidable.
The Common Thread
Every failure mode above shares the same root cause: insufficient planning before the project begins. The organisations that execute LAN refreshes successfully are those that invest time in scoping, assessment, and design before a single purchase order is raised. The organisations that struggle are those that treat planning as a luxury and implementation as the real work.
A LAN refresh is not a commodity exercise. It requires engineering expertise, project discipline, and a clear understanding of the business it serves. Organisations that work with a LAN refresh specialist uk businesses trust are far more likely to deliver on time, within budget, and without disruption. For those evaluating their options, IT Connect — a specialist LAN refresh consultant in the UK — has published a practical guide covering the full process, from initial scoping and site assessment through to cutover planning and handover documentation.
