Overview: replace or expand?
When a UniFi switch starts to feel tight on ports, power, or throughput, the obvious choices are to add another switch or replace it with a larger unit. Both options are valid—what matters is matching technical needs, budget, physical constraints, and downtime tolerance. This article gives a practical decision checklist and step‑by‑step migration advice based on field experience with small offices, retail sites, and vacation rental properties.
Key factors to evaluate before deciding
Run a short audit before you buy anything. These are the signals we use in the field to choose replacement versus expansion.
1. Port and PoE capacity
- Count active and planned devices: APs, phones, cameras, door controllers, IoT. Include near‑term projects (next 12 months).
- Check PoE draw: some cameras and access points use more power than older models. Use a PoE budget calculator to estimate total wattage. A quick online tool like the PoE budget calculator helps confirm whether a switch can sustain current and planned loads.
- If ports are nearly full and the PoE budget is exhausted, replacement with a higher‑density or higher‑PoE model is often simpler than stacking many small switches.
2. Uplink bandwidth and throughput
- Look at uplink saturation. If the switch’s uplink port (1Gb SFP, 10Gb, etc.) is the choke point, adding edge switches won’t fix the bottleneck—consider replacing the switch with a higher‑capacity core or a model with multi‑gig uplinks.
- Monitor actual throughput during peak periods. If utilization consistently approaches the available uplink, plan for a replacement that increases aggregate capacity.
3. Latency, packet errors, and CPU limitations
- High CPU/forwarding engine usage, increasing collisions, or rising CRC errors are signs a switch is struggling. These are better addressed by replacement.
- Temporary expansion can work around intermittent issues, but hardware showing growing error counts should be replaced rather than band‑aided.
4. Feature needs and future‑proofing
- Do you need SFP+ ports, multi‑gig PoE ports, Layer 3 routing, or higher buffer sizes? If new features are required, replacing the switch is the only option.
- If growth is limited and you only need more basic ports, a simple expansion switch is cheaper and quicker to deploy.
5. Physical constraints, noise, and rack space
- Check available rack units, ventilation, and noise. A replacement can consolidate multiple noisy, power‑hungry units into a single quieter chassis.
- Use a planner to visualize rack space before buying—tools like the network rack planner are useful for this step.
Practical decision checklist
Use this quick flow to decide.
- Are ports full but PoE budget and uplink healthy? If yes → add an edge switch.
- Is the PoE budget exhausted or expected to be within 12 months? If yes → replace with a higher‑PoE switch.
- Is uplink bandwidth saturated or are you adding high‑bandwidth services (video, frequent backups)? If yes → replace with a higher‑capacity core switch.
- Are you running out of rack space, or are noise/heat concerns a factor? If yes → favor replacement to consolidate.
- Do you need new features (multi‑gig, SFP+, L3 routing)? If yes → replace.
Migration and deployment steps for replacement
Replacing a switch can be disruptive if not planned. These steps, honed from on‑site work in small businesses and vacation rentals, keep downtime low.
1. Plan and stage
- Document existing ports and devices. Label cables and record VLAN and PoE settings in the controller. A simple spreadsheet with port→device mapping prevents confusion during cutover.
- Back up the UniFi Network controller configuration and export relevant switch configs.
- Preconfigure the new switch in a lab or off‑hours to minimize time onsite. Adopt it into the controller and set VLANs, PoE profiles, and port profiles the same as the existing switch.
2. Test adoption and firmware
- Adopt the device in the controller in a staged environment if possible. Avoid pushing large firmware upgrades during a live migration—plan them for a maintenance window.
3. Schedule a maintenance window
- Communicate expected downtime and have a rollback plan (keep the original switch powered and connected until testing is complete).
4. Cutover
- Disconnect devices from the old switch and move them to the new one following your port map. If possible, move uplinks and clustered devices first (firewalls, servers) to restore core connectivity quickly.
- Confirm VLANs, PoE, and link status. Verify critical services—phone system, guest Wi‑Fi, cameras—first.
5. Validate and decommission
- Allow a monitoring period (24–72 hours) to verify stability. Keep the old switch available but powered off; don’t permanently decommission until you’re confident the new configuration is stable.
Deployment steps when adding an edge/expansion switch
Expanding with a second switch is often quick and low‑cost, but you still need to avoid common mistakes.
1. Choose the correct uplink and PoE configuration
- Ensure your uplink between switches has enough bandwidth; consider link aggregation if you expect heavy cross‑switch traffic.
- If the expansion switch will power cameras or APs, verify its PoE budget with a calculator such as the PoE budget calculator. Don’t assume two smaller switches equal one large switch’s power handling.
2. Adopt and profile
- Adopt the new switch into the controller and apply the same port profiles and VLANs. If you use different firmware branches, match versions to avoid behavioral differences during the initial hours.
3. Physically mount and tidy cabling
- Document port assignments and label both ends. Clean cable management reduces future troubleshooting time and accidental unplugging.
Common pitfalls and how to avoid them
- Assuming ports alone solve the problem. If uplink or CPU is the bottleneck, adding switches won’t improve performance.
- Not checking PoE headroom. Cameras and newer APs quickly consume PoE budgets.
- Poor labeling and no backup—always export controller settings and keep a physical port map.
- Upgrading firmware during a cutover without a rollback plan—schedule upgrades separately.
Troubleshooting after a swap
If issues appear after replacement or expansion, follow a methodical approach: check physical links, confirm VLAN tags, verify PoE is enabled where required, and look at interface error counters. Many common problems are covered in our technical troubleshooting guide: Unifi troubleshooting.
Example scenarios
Scenario A — Growing office needing more APs and cameras
The office has a single 8‑port switch with all ports used and PoE exhausted. Cameras planned for the next quarter will push PoE demand higher. Decision: replace with a higher‑density switch with a larger PoE budget to avoid power juggling across multiple devices.
Scenario B — Retail site with slow backups at night
Multiple edge switches feed a single 1Gb uplink that saturates during nightly backups. Decision: replace the core switch with a model offering 10Gb uplinks or add a 10Gb uplink between key devices to relieve the bottleneck.
Checklist before you buy
- Inventory: ports in use + forecasted new devices (12 months).
- PoE check: total wattage required (use PoE calculator).
- Uplink check: measure peak and average utilization.
- Space/noise: verify rack units and ventilation (use rack planner if needed).
- Backup: export the controller and document port mappings.
Short FAQ
How much PoE headroom should I leave?
Leave at least 15–25% headroom for future devices and power spikes. Exact needs depend on the types of devices you’ll add—cameras and multi‑radio APs use more power than simple IoT sensors.
Can I mix switch models from different UniFi generations?
Yes—UniFi allows mixed models in the same network. Beware of differences in performance, port behavior, and firmware. Test compatibility and avoid major firmware changes during a live cutover.
Is it worth using link aggregation between switches?
Link aggregation is valuable when you have sustained cross‑switch traffic such as backups, virtualization hosts, or large file transfers. It increases throughput and provides redundancy for the uplink.
What if I need help planning or troubleshooting?
We provide independent Network installation and remote support across the USA, with on‑site service available in Virginia and North Carolina (including the Outer Banks). For complex cutovers, a pre‑staged approach and a checklist greatly reduce risk.
Independent‑service disclaimer
This article is informational and based on hands‑on experience with UniFi equipment. We are an independent Network service provider and not affiliated with the brand. On‑site services are offered in Virginia and North Carolina (including the Outer Banks); remote support is available nationwide. This content is not a substitute for reading vendor documentation or consulting with a qualified network professional for your specific environment.