Network Upgrade Checklist for WiFi, Switching & Cabling

Step 1: Assess What You Have Before Starting the Network Upgrade

Don’t order hardware until you’ve assessed what you have. Buying new switches before you know your existing cabling can support them is a common and expensive mistake. Assess first. Specify second. Order third.

What Your Network Upgrade Assessment Should Cover

Start with a full inventory of existing hardware. Document every switch model, AP model, and gateway. Note the firmware version and check it against the manufacturer’s current supported release. Hardware more than four years old without an active firmware support path needs replacement — not just upgrade. Hardware that still receives updates gets evaluated on performance first.

Check your current PoE budget against your current device load. Log into your UniFi controller and pull the PoE consumption report for each switch. If any switch runs above 75 percent of its PoE budget, it’s already a bottleneck. Your network upgrade needs a larger switch, not just a newer one.

Cabling Assessment: Run Certification Before You Spec New Hardware

Certify your existing cable plant with a Fluke DSX before finalizing your cabling upgrade scope. Cat5e runs certify at 1 gigabit up to 100 meters. If you’re moving to 2.5G or 10G switching, those runs become your bottleneck. Cat6 runs certify at 10 gigabit up to 55 meters — adequate for most office drops. Cat6A certifies at 10 gigabit up to 100 meters — the right spec for any drop over 55 meters or near PoE++ devices.

The certification test tells you exactly which runs need replacement. Don’t assume all Cat5e needs replacing. Don’t assume all Cat6 stays. Measure it. Replace only what the data says needs replacing. That approach cuts your cabling scope — and your cabling cost — significantly. See our detailed breakdown of Cat6 vs Cat6A vs Cat7 and when each applies for help making that call.

Replace your APs when they’re over four years old, when they no longer receive firmware security patches, or when they run 802.11ac (WiFi 5) in an environment that now runs 50 or more concurrent devices. WiFi 6 and WiFi 7 hardware handles dense client environments significantly better than older 802.11ac gear. The performance gap widens as you add devices.

The UniFi U6 Pro covers most mid-size office environments at 13.5W PoE draw per AP. For dense urban buildings or conference-heavy floors, the U7 Pro adds a 6GHz radio that cuts through 5GHz congestion. If your existing APs are U6 Lites running at capacity in conference rooms, swapping them for U6 Pros resolves most performance complaints without re-cabling anything.

Before the WiFi upgrade:

• Run a passive wireless site survey. Capture existing signal levels, channel assignments, and spectrum congestion from neighboring networks.
• Document every AP’s current position, channel, and TX power setting.
• Pull the client count history from your UniFi controller for each AP. Identify which APs regularly exceed 50 concurrent clients.
• Verify that your PoE switch budget supports the new AP models. U7 Pro APs draw 25W — nearly double the U6 Lite’s 12W. Budget the difference before ordering.

After the WiFi upgrade:

• Run a post-deployment heat map. Confirm every occupied area hits -65 dBm or better.
• Assign channels manually from the site survey spectrum data. Don’t rely on auto-channel in a congested building.
• Enable 802.11r fast roaming on your staff SSID. Verify seamless handoff by walking between AP coverage zones with an active call.
• Check PoE consumption per switch in the controller. Confirm no switch exceeds 80 percent of its rated budget.

For more on how AP selection affects the outcome of a network upgrade, see our guide to choosing the right wireless access points.

Switch Upgrade: PoE Budget, Port Density, and Uplink Speed

A switch upgrade has three variables: PoE budget, port count, and uplink speed. Get any one wrong and the new switch becomes the bottleneck you just replaced the old one to fix.

Calculating Your New PoE Budget

Add up the maximum wattage of every PoE device connecting to the new switch — APs, IP cameras, VoIP phones, access control panels. Multiply the total by 1.25. That’s your minimum PoE budget. A floor with 8 U6 Pro APs (108W), 16 cameras (192W), and 20 VoIP phones (100W) draws 400W at peak. Multiply by 1.25 and you need a switch with at least 500W of PoE budget. The USW-Pro-48-PoE at 600W handles that floor with room for growth.

Don’t spec the USW-24-PoE for a mixed AP and camera deployment. Its 95W total PoE budget averages less than 4W per port. That works for a handful of low-draw devices. It fails the moment you add more than six real-world PoE devices with meaningful draw. The Pro model costs more. The re-spec call six months later costs more than the difference.

Uplink Speed: When 1GbE Is No Longer Enough

Move to a 10GbE uplink switch if you run four or more APs on the same switch, or if a NAS or server connects on the same segment. A single 1GbE uplink saturates well before your APs reach their client capacity. The USW-Pro-24-PoE and USW-Pro-48-PoE both include 2 × 10GbE SFP+ uplink ports. That’s your standard spec for any commercial deployment that plans to grow.

Run Cat6A to every switch uplink drop if you haven’t already. Cat6A supports 10-gigabit throughput up to 100 meters. Cat6 supports it up to 55 meters. If your IDF-to-MDF fiber uplink already runs SFP+, confirm the transceiver modules match on both ends before the switch upgrade day.

Switch Upgrade Checklist

• Document every existing switch port assignment before the upgrade. Label each port with device name, VLAN, and cable run ID.
• Pre-configure the new switch on the bench. Apply VLANs, trunk ports, PoE profiles, and management settings before racking.
• Confirm the new switch adopts cleanly into your UniFi controller at the correct site.
• Verify PoE budget headroom post-installation. Aim for no more than 75 percent utilization at peak load.

Your Fluke DSX certification results from the assessment phase tell you which runs fail at your target speed. Replace every failing run. Keep every passing run. For runs that pass today but sit right at the margin — less than 1 dB of headroom on insertion loss — replace those too. A marginal run fails after the next re-termination or a temperature change in a warm IDF closet.

Prioritize AP drop replacements first. APs run the highest sustained data rates of any device on your network. A marginal cable under an AP causes intermittent retransmissions that look like WiFi problems. The cable is the actual problem. Replace it and the WiFi performance complaint often disappears without touching the AP at all.

Every new run uses Cat6A terminated to TIA-568 standards. Every run gets a Fluke DSX certification report before the ceiling tile closes. Label both ends of every run with the same ID from your cable schedule. Use a Brady BMP21-PLUS label printer — not handwritten tape. Handwritten labels yellow and peel within 18 months in a warm IDF closet.

Deliver the as-built documentation package at project close. It includes the cable schedule, the Fluke DSX certification report for every run, the rack diagram, and the VLAN assignment table. Without it, every future change starts with a re-tracing exercise that shouldn’t exist. See our full guide on Fluke cable testing for network certification for what the DSX report package looks like.

Network Cutover Plan: How to Upgrade Without Downtime

The network cutover plan is where most upgrades either succeed cleanly or turn into a multi-hour emergency. A good cutover plan has four components: pre-staging, a sequenced cutover window, a validation checklist, and a rollback procedure.

Pre-Staging: Do the Work Before the Window

Pre-stage every device at least one week before cutover. Apply your full VLAN structure, SSID configuration, firewall rules, and QoS settings to the new hardware on the bench. Adopt every switch and AP into the correct site in your UniFi controller before it goes to the rack. Configuration work during a live cutover window creates errors under pressure. Configuration work on the bench takes longer but produces a cleaner result.

Test every VLAN on the bench before the cutover date. Connect a test device to each segment. Confirm correct routing, internet access, and firewall isolation. Document the results. If a VLAN fails on the bench, you fix it before the cutover window — not during it.

The Cutover Window: Sequence Matters

Schedule your cutover window during off-hours. A weeknight from 9 PM to midnight or an early Saturday morning gives you time to work without user pressure. Run this sequence during the window:

• Power on the new gateway. Confirm WAN connectivity and firewall rule operation.
• Bring IDF switches online one floor at a time. Confirm each switch adopts into the controller and shows correct PoE output.
• Connect AP drops. Confirm each AP adopts and broadcasts the correct SSIDs on the correct channels.
• Run per-VLAN validation. Connect a test device to each SSID and wired port. Confirm routing, internet access, and VLAN isolation.
• Run a WiFi heat map spot-check on the most critical floor. Confirm signal meets your -65 dBm threshold in conference rooms.
• Decommission old hardware only after every validation step passes.

The Rollback Procedure

Keep the old hardware powered but disconnected — not decommissioned — until at least the next business day. If a critical issue surfaces at 8 AM Monday, reconnecting the old gear gives you a working network in minutes while you diagnose the new one. A rollback that takes 10 minutes is a safety net worth keeping. A rollback that requires rebuilding from backup takes hours you don’t have during a business day crisis.

Export your current UniFi controller configuration as a backup before the cutover window starts. Store it somewhere outside the controller — a shared drive or email to IT leadership. If the controller itself has a problem during cutover, that backup rebuilds your configuration without starting from scratch.

Mistake 1: Treating the Network Upgrade as a One-Day Event

What happens: New hardware arrives on cutover day. The team unpacks, configures, and migrates on the same day. The cutover runs four hours over schedule. Something gets missed. Users report problems for two weeks.

Why it undermines the upgrade: Configuration work under live-cutover pressure produces mistakes. Missed VLAN rules, wrong SSID mappings, and skipped firewall configs all surface when 40 people connect on Monday morning. Each one requires a separate fix on a live production network.

The fix: Separate the pre-staging from the cutover by at least one week. Configure and test everything on the bench. The cutover window becomes a physical swap and validation exercise — not a configuration sprint. Your team finishes on time. Users notice nothing.

Mistake 2: Skipping the Cabling Assessment Before the Switch Upgrade

What happens: The team installs a new 10GbE switch and discovers that the existing Cat5e runs to the APs cap out at 1 gigabit. The switch bottleneck moved from the hardware to the cable plant. Performance doesn’t improve. The cabling upgrade now needs to happen on top of a switch upgrade that’s already complete.

Why it happens: Cabling assessments add time and cost to the project. Teams skip them to move faster. The assumption is that the existing cabling is “fine.” Fine for what it ran before. Not fine for what the new hardware needs.

The fix: Always run Fluke DSX certification on the existing plant before specifying new switching hardware. The certification results tell you what your cabling supports today. That data determines whether a cabling upgrade runs in parallel with the switch upgrade or not at all. See our guide on PoE cable testing and certification for reliable power delivery for what the test covers.

From the Field: A 70-person law firm in Jersey City brought us in to manage a full network upgrade — 4 new USW-Pro-48-PoE switches, 18 U6 Pro APs, and a Dream Machine Pro replacing a five-year-old consumer router. We pre-staged all hardware two weeks before cutover. Every VLAN, every SSID, every firewall rule configured and tested on the bench. Cutover night took 2 hours and 40 minutes for a 4-floor building. Every AP adopted. Every VLAN validated. Old hardware powered off at 11:45 PM. Staff arrived Monday morning to a network that felt completely normal — because from their perspective, nothing had changed except the speed. That’s what a documented network cutover plan produces.

Quick Wins for a Smoother Network Upgrade

• Name every device before the cutover using a consistent format: [Floor]-[Type]-[Number]. “F03-SW-01” and “F03-AP-02” are instantly identifiable during a 10 PM cutover. “USW-Pro-48-PoE” with a random MAC address is not.
• Document your VLAN assignment table before the upgrade and hand it to every technician on the cutover team. Everyone needs to know what VLAN 10 carries, what VLAN 20 carries, and which switch ports trunk which VLANs. That document prevents configuration disagreements mid-cutover.
• Keep one spare AP and one spare switch in your equipment room after the upgrade. Hardware failures on a newly upgraded network don’t need to become next-day shipping emergencies. A spare device on the shelf means a same-hour swap.
• Review your upgrade results against your original assessment data 30 days after cutover. Compare PoE consumption before and after. Compare per-AP client counts. Compare bandwidth usage per SSID. The comparison tells you whether the upgrade achieved its goals — and flags anything that still needs attention before it becomes a complaint.

Your Network Upgrade Succeeds or Fails in the Planning Stage

Every clean network upgrade we’ve delivered followed the same pattern: assess before ordering, pre-stage before cutting over, validate before decommissioning, and document before closing the project. The hardware rarely causes problems. The process does — or doesn’t.

The Jersey City law firm’s cutover took under three hours for a 4-floor building because two weeks of bench work happened before anyone touched a live network. That’s the ratio that works. More time in pre-staging means less time in the cutover window. Less time in the cutover window means less exposure for your business and less stress for your team.

If you’re planning a network upgrade and want a team that handles the assessment, pre-staging, cutover, and documentation, book a call. We’ll scope the full project — WiFi, switching, cabling, and cutover plan — so every layer of your upgrade lands right on the first try.

Ready to Plan Your Network Upgrade Without the Downtime Risk?

Tell us your current hardware, floor count, and device count. We’ll scope the full upgrade — WiFi, switching, cabling, and cutover plan — so your team has a faster, more reliable network without a Monday morning crisis.

Call: 833-469-6373 or 516-606-3774
Text: 516-606-3774 or 772-200-2600
Email: hello@unifinerds.com | Visit: unifinerds.com

Free consultations • Phased implementation • Budget-friendly • Expert support