Moving Your Office Without Losing Your Mind (or Your Phones): Part 7 of 8
An office move is a natural inflection point. You're already disrupting your routine, already reconfiguring equipment, already dealing with change. Some businesses see this as an opportunity to upgrade their entire technology stack: new phones, new PBX, new ISP, new network equipment. Others carry their existing setup to the new location as-is, minimizing variables during an already complex transition.
Both approaches have merit, and the right answer depends on your specific situation. The worst approach is to try to do both at the same time without understanding the tradeoffs.
The case for carrying forward
Moving an existing, working setup to a new location has one enormous advantage: you know it works. The phones, the PBX, the router configuration, the trunk, the auto attendant, the ring groups, everything has been tested and refined over months or years of daily use. Moving it to a new location introduces one major variable (the new internet connection and physical environment) rather than a dozen.
When you carry forward, problems are easier to isolate. If something doesn't work at the new location, you know it worked at the old one, so the issue is almost certainly related to the new environment rather than to the equipment itself. This dramatically narrows the troubleshooting scope.
Carrying forward also costs less in the immediate term. You're not buying new equipment, not paying for new configuration, and not retraining anyone on new systems.
Carry forward when:
- Your current setup is working well and meeting your needs
- The move is already complex enough without adding technology changes
- Your budget is stretched by the move itself
- Your team is resistant to change and can't absorb both a move and a new system at the same time
- The equipment is relatively modern and will serve you for at least another few years
The case for upgrading
A move is one of the rare moments when changing everything is actually easier than normal. You're already disconnecting and reconnecting equipment. You're already reconfiguring network settings. You're already disrupting workflows. Adding new equipment to an already disrupted process is less impactful than introducing new equipment during normal operations when everyone expects things to work seamlessly.
There's also a practical consideration. If your phones are seven years old and showing their age, your PBX is running on hardware that's out of warranty, and your network switches are consumer grade, you're going to need to replace them eventually. Doing it during a move means you do it once. Carrying forward and then upgrading six months later means two disruptions instead of one.
Moving is also the cleanest time to switch from an on premises PBX to a cloud hosted system. At the old location, you'd have to migrate extensions one at a time, manage a hybrid setup during the transition, and coordinate the cutover while people are working. During a move, there's a natural cutover point. The old PBX stays at the old location. The new phones register to the cloud provider at the new location. The transition is clean.
Upgrade when:
- Your current equipment is old, out of warranty, or not meeting your needs
- You've been wanting to switch phone systems (especially from on premises to cloud) and the move provides a natural transition point
- The new office has different infrastructure requirements that your current equipment can't meet (more ports, more PoE capacity, different cabling)
- Your current system has reached its capacity and the new office will have more employees or more phones
- The cost of new equipment is within budget and the long term savings (lower maintenance, better features, reduced support costs) justify the investment
What to upgrade and what to keep
If you decide to upgrade, you don't have to replace everything. Some components are more worth upgrading than others.
Network switches: often worth upgrading. If you're running unmanaged consumer switches, the move is a great time to upgrade to managed switches with VLAN support and PoE. This is one of the highest impact improvements you can make for VoIP quality. Managed switches let you separate voice and data traffic, prioritize voice packets, and monitor port health. The price difference between a consumer switch and a business managed switch has narrowed significantly in recent years.
Router/firewall: upgrade if your current one is limiting you. If your current router doesn't support QoS, doesn't handle SIP well (poor SIP ALG behavior, NAT issues), or doesn't have enough throughput for your connection speed, upgrading during the move makes sense. If your current router works well, carry it forward.
Phones: upgrade if they're old or if you're changing PBX platforms. If you're staying on the same PBX, your existing phones will work at the new location with no changes. If you're switching PBX platforms (especially to a cloud provider), you may need new phones that are compatible with the new system, or your existing phones may need to be reprovisioned, which varies in difficulty by phone model.
Modern IP phones from the last five or six years generally support standard SIP and will work with most providers. Phones older than that may lack features like Gigabit Ethernet, HD audio codecs, or adequate processing power for modern firmware. If you're replacing phones, this is a good time to standardize on a single manufacturer and model across the office, which simplifies management.
Cabling: upgrade if the building requires it. As discussed in the building infrastructure post, the new building's cabling situation may force your hand. If the existing cabling is inadequate, new cable needs to be run regardless of your other upgrade decisions.
PBX: the biggest decision. Changing PBX platforms during a move is the most impactful upgrade and the one with the highest risk. It introduces the most variables: new interface, new features, new configuration, new provider relationship, potential number porting, and a learning curve for everyone. If you're going to do it, plan it as a separate project that happens to coincide with the move, with its own timeline, testing plan, and rollback strategy. Don't treat it as a line item on the moving checklist.
The hybrid approach
Many businesses take a pragmatic middle path: carry the core system forward and upgrade the components that need it most.
Keep the PBX and phones. Upgrade the switches and router. Run new cabling in the new building. The phone system that everyone knows continues working exactly as before, but the underlying network infrastructure is modernized.
Or: keep the network equipment (it's only two years old and works fine) but switch from an on premises PBX to a cloud provider, using the move as the cutover point.
The hybrid approach lets you pick your battles. Focus the upgrade budget and the disruption tolerance on the components that will make the biggest difference, and leave the rest alone.
Timing the upgrade relative to the move
If you're upgrading any component, the upgrade should be tested before move day, not on move day.
For new network equipment (switches, router, firewall): configure it at the new location during the overlap period and test with a few devices before the full move.
For a new PBX or cloud phone system: set it up, configure all extensions and features, test thoroughly with temporary numbers, and only cut over to it on or after move day once you're confident it works.
For new phones: provision them and test them on the new system before deploying them to desks. A phone that's been provisioned, tested, and labeled with the user's extension is a phone that can be plugged in on move day and work immediately.
The principle is the same as the rest of this series: reduce the number of variables on move day. Test everything you can in advance. Use the overlap period to validate. Make move day about connecting proven equipment, not debugging new equipment.
Next up: The Complete Office Move Telecom Checklist, a consolidated reference of everything covered in this series.
Share
Want to know when we publish new articles? Sign up for updates