Enterprise Network Refresh
the switches are six years old. The next outage isn't a question of if.
Refresh design and execution across SoCal — corporate, healthcare, higher ed, K-12, government, manufacturing. Cisco Catalyst / Meraki. Aruba CX. Fortinet FortiSwitch. Juniper EX / Mist. Extreme. Phased migration. Weekend cutover. Zero-downtime where topology permits.
Enterprise network refresh — the switches outlive the warranty, not the business case
Enterprise network refresh is the project most IT leaders push two or three years past the right window because the network is still working. It works until it doesn't. Vendor end-of-support dates, ASIC-level performance ceilings, missing modern features (PoE budget, multi-gig, AV-over-IP, NAC support), and cyber-insurance underwriting pressure set the real timeline. NIST Cybersecurity Framework aligns the security posture inputs.
The scope: existing-state audit (Layer 1 through Layer 3, plus wireless, plus firewall), refresh target architecture, vendor and platform selection, phased migration plan with rollback at each phase, change-management windows, weekend cutover execution, post-cutover monitoring, and decommissioning of legacy hardware with documented chain-of-custody for data-bearing devices.
Pairs with networking for the broader architecture, wireless for the AP refresh, structured cabling for any Cat 5e-to-Cat 6A upgrades, and managed services for ongoing operations post-cutover. Start with a free assessment.
Three patterns that derail refresh projects
Refresh projects get planned, scoped, budgeted, and then sit. The reasons are predictable.
No documented topology
The as-built drawings are five years stale. The MDF rack diagram exists in someone's head. The VLAN assignments live in tribal knowledge. Refresh planning stalls at week two when the team realizes they're refreshing a network nobody fully documented. The audit phase fixes this; skipping it kills the project.
Big-bang cutover gets attempted
The forklift weekend gets scheduled. Everything switches at once. Something breaks. Nobody knows which change caused it because everything changed. Phased migration with documented rollback at each phase is the answer; big-bang is the cause of every nightmare-cutover story you've heard.
Legacy gear stays in production
The new switches go in. The old switches stay in "for now." Six months later the closet has both. Patching is unclear. Operations support both. Decommissioning has to be part of the project plan, not a follow-up phase that never happens.
Why choose WCC for enterprise network refresh
Network refresh is audit + design + phased migration + cutover execution + decommissioning. WCC handles all five under one license.
CSLB C-7 · C-10 · C-28
Active California contractor license. Structured cabling, electrical, low-voltage, and electronic systems under one license stack. Permits handled where required.
Cisco · Aruba · Fortinet · Juniper
Cisco Catalyst / Meraki, Aruba CX, Fortinet FortiSwitch / FortiAP, Juniper EX / Mist, Extreme Fabric. Vendor-neutral refresh recommendations.
Documented Rollback
Phased migration plan with documented rollback at each phase. No big-bang cutovers. No "we'll figure it out Sunday morning." Every change has a back-out.
Decommissioning + Chain-of-Custody
Legacy hardware decommissioning with documented chain-of-custody for data-bearing devices. Disposal certificates. ITAD partner integration. Asset removal from CMDB.
The six refresh capability areas
Each capability scopes to existing topology, target architecture, and operational risk tolerance.
Existing-State Documentation
Layer 1 cable plant audit, Layer 2 / 3 topology, VLAN inventory, routing posture, wireless coverage map, firewall rule audit, dependency mapping. Documented baseline against which the refresh design is built.
Target Architecture
Refresh target design including switch / wireless / firewall vendor selection, topology rationalization (collapsed-core, spine-leaf, or two-tier), VLAN restructure where warranted, PoE budget sizing, multi-gig where applicable, AV-over-IP readiness.
Cable Plant Assessment
Cat 5e to Cat 6A upgrade scoping where new gear demands it. Fiber backbone capacity review. Single-mode vs. multi-mode rationalization. Patch panel and MDF / IDF rack refresh where warranted.
Phased Migration Plan
Phased migration with documented rollback per phase. Pilot closet, lab validation, then production phases. Change-management window scheduling. Communication plan for end users. Documented success criteria per phase.
Weekend Window Execution
Weekend or after-hours cutover windows with documented runbooks, rollback procedures, and verification checklists. On-site execution team. Network engineer plus cabling tech plus project manager. Hour-by-hour status during the window.
Legacy Decommissioning
Legacy switch / AP / firewall removal. Data-bearing device chain-of-custody. ITAD partner shipping. Disposal certificates. CMDB asset retirement. MDF / IDF cleanup. Documentation refresh.
Enterprise network refresh — common questions
Considering NaaS for the refresh instead of owning the new stack? Read the Meter alternative comparison first — subscription convenience vs. multi-vendor hardware you own.
Five drivers force the timeline: vendor end-of-support (the hard one — no security patches, no warranty), ASIC-level performance ceilings (the closet can't do what new traffic demands), feature gaps (no NAC support, insufficient PoE budget, no multi-gig), cyber-insurance underwriting requirements, and accumulated technical debt. Most environments are due 12-18 months before they refresh.
Driven by existing operational expertise, identity / NAC stack, and broader security posture. Cisco for Cisco-trained operators and ISE-heavy NAC. Aruba for ClearPass-heavy NAC, AOS-CX simplicity, mid-market sweet spot. Fortinet for security-stack consolidation under FortiGate / FortiManager. Juniper for Mist AI-driven wireless or where Apstra fabric is the target. Extreme for fabric-attached campus. WCC scopes vendor in the design phase.
Phased. Pilot closet or IDF first — lowest-risk segment, weekend window, full verification before moving on. Production phases scheduled by risk and dependency: low-risk closets first, then production VLANs, then critical-path infrastructure. Each phase has a runbook, rollback procedure, and verification checklist. Hour-by-hour status during cutover windows. Post-cutover monitoring for the following business day.
Wireless refresh typically rides with the switch refresh because the APs are PoE-fed by the switches and the controllers depend on the L3 design. Common patterns: refresh switches and APs together for cleanest cutover; refresh switches first with existing APs migrated to new switches, then AP refresh in a follow-up phase; refresh APs first to a cloud-managed model (Meraki, Mist), then switch refresh. Driven by AP-end-of-support and Wi-Fi 6 / 6E / 7 demand.
Sometimes — depending on topology and design discipline. Spine-leaf and dual-homed access designs support per-device hot-swap migration with no end-user impact. Two-tier or single-homed designs require maintenance windows. The realistic answer for most enterprise refresh: zero-downtime for the critical-path infrastructure (firewalls, distribution, core), planned weekend windows for the edge (access switches, APs).
Small office refresh (under 50 users, 1-2 closets, basic switch and wireless): $30K-80K hardware plus $15K-40K services. Mid-market refresh (100-500 users, multi-closet, integrated security and wireless): $100K-400K hardware plus $50K-150K services. Enterprise refresh (1,000+ users, multi-site, fabric or spine-leaf, multi-vendor coordination): $400K-2M+ hardware plus $150K-800K services. E-Rate eligible portions discount the schools refresh substantially.
Network refresh projects across Southern California
WCC delivers enterprise network refresh across all six SoCal counties — corporate, healthcare, higher ed, K-12, government, manufacturing. Chino HQ.
Network refresh is the project that gets pushed two years too long.
WCC delivers enterprise network refresh: existing-state audit, target architecture design, vendor-neutral selection across Cisco, Aruba, Fortinet, Juniper, Extreme. Phased migration with documented rollback. Weekend cutover execution. Legacy decommissioning with chain-of-custody. CSLB C-7 / C-10 / C-28.