After the Move: The First Two Weeks

Moving Your Office Without Losing Your Mind (or Your Phones): Part 6 of 8

The furniture is in place. The phones are working. People are at their desks. Move day went smoothly. And then, slowly, the issues start surfacing. Not the dramatic "nothing works" kind of issues that you'd catch on day one, but the smaller, subtler problems that only appear when a full team is using the new setup under real conditions for real work.

The first two weeks in a new office are a shakedown period. Expect things to come up. The goal isn't a flawless first day. It's identifying and resolving issues quickly before they become entrenched frustrations.

Call quality issues that weren't there during testing

You tested calls during the overlap period and they sounded fine. Now that the whole team is in the office, calls are occasionally choppy during the busiest parts of the day. This is the bandwidth saturation pattern covered in the afternoon call quality post from the troubleshooting series.

During testing, you had a handful of people using the connection. Now you have everyone: phones, computers, video conferencing, cloud applications, all competing for the same bandwidth simultaneously. The connection that seemed perfectly adequate during light testing may show strain under full production load.

Monitor the internet connection's utilization during the first week, and run a VoIP quality test during peak hours to quantify any degradation. If upload utilization approaches the connection's maximum during peak hours, implement QoS on the router to prioritize voice traffic. If QoS isn't sufficient, you may need to revisit the connection plan. The overlap period (if the old location's internet is still active) gives you a window to upgrade or add a second connection at the new location before the situation becomes urgent.

WiFi coverage gaps

The WiFi worked great in the conference room during setup. Now that there are 20 devices in the main office, the access point near the front desk is overwhelmed and people in the back corner have weak signal. WiFi under load behaves differently than WiFi with a few devices, and the physical layout of an occupied office (with people, monitors, filing cabinets, and other obstructions) affects signal propagation differently than an empty space.

Walk the office with a phone or laptop and check signal strength in every area where people work or make calls. If there are dead spots or weak areas, the access point placement may need adjustment. Adding an additional access point, moving an existing one, or adjusting channel and power settings can resolve coverage issues.

If anyone is using WiFi for VoIP phones (softphones on laptops, WiFi desk phones), prioritize wired connections for those users. WiFi voice quality will always be less consistent than wired, and the extra devices competing for airtime in a fully occupied office make it worse.

Network discovery and device conflicts

When everything is plugged in at the new location, devices that were on different subnets or VLANs at the old office might end up on the same network. Printers that used static IP addresses at the old location might conflict with DHCP ranges at the new location. A device with a hardcoded IP from the old network (10.0.0.200) might not work if the new network uses a different subnet (192.168.1.x).

Inventory any devices with static IP configurations: printers, network attached storage, security cameras, door access systems, the PBX if it's on premises, and any servers. Verify that their static addresses are within the correct subnet for the new network and don't conflict with the DHCP range.

SIP trunk adjustments

If your SIP trunk uses IP based authentication and the new location has a different public IP address (which it almost certainly does), the trunk provider's configuration needs to be updated with the new IP. If this wasn't done before the move, outbound calls through the trunk will be rejected because the provider doesn't recognize the new source IP.

Contact your trunk provider (or log into their portal if they have self-service IP management) and update the authorized IP address. If you're on registration based authentication rather than IP authentication, this isn't an issue since the trunk authenticates with credentials regardless of the source IP.

Also check whether the new ISP's firewall or NAT is behaving differently than the old one. Even with the same PBX configuration, a different router's NAT handling can cause one way audio, registration failures, or other SIP issues that didn't exist at the old location. If you're experiencing new SIP problems that weren't present before the move, the router's SIP ALG setting, NAT type, and firewall rules are the first things to investigate.

Conference room and shared space issues

Conference rooms have their own set of technology needs that might not have been fully addressed during the move. The conference phone might be on a different VLAN than expected. The display might need network access for wireless presentation. The room's Ethernet ports might not be patched to active switch ports.

Walk through every conference room and shared space in the first week. Test the conference phone, the display connectivity, the wireless presentation system, and the WiFi coverage. These spaces are where problems are most visible (a choppy conference call with a client is noticed immediately) and where they cause the most frustration.

Remote workers reconnecting

If your team includes remote workers who connect to office resources (VPN, remote desktop, shared drives), the change in public IP address and potentially the change in VPN configuration affects them. Remote workers who connected fine to the old office might not be able to connect to the new one until the VPN or remote access configuration is updated with the new addressing.

Send clear instructions to remote workers before the move about any changes they need to make: new VPN server addresses, updated connection profiles, or new credentials if the access system has changed. Have someone available on move day and the days following to help remote workers troubleshoot connection issues.

Updating external records

Your office phone numbers are the same (assuming the port went through), but other things have changed that need to be updated:

Business address in online directories. Google Business Profile, Yelp, industry directories, and anywhere else your business address appears online. Search engines use this information, and an outdated address can misdirect customers.

SIP trunk provider records. Your 911 service address needs to be updated with your VoIP provider. When someone dials 911 from your office phones, the system sends your registered address to emergency services. If this still shows the old address, emergency responders will be sent to the wrong location. This is critically important and should be updated on move day.

Alarm and security systems. If your alarm system communicates over the phone line or internet, it needs to work at the new location. Test the alarm system and update the monitoring company with the new address.

Fax header. If you use a fax machine, the fax header (the line of text printed at the top of each fax you send) typically includes your business name and phone number, and sometimes your address. Update it.

Documenting the new setup

The first two weeks are also the right time to document the new network and phone setup while everything is fresh. Record:

The ISP account number, circuit ID, support phone number, and the IP addressing assigned to the connection. The router and firewall configuration (export a backup). The switch port assignments (which port connects to which desk or device). The phone system configuration (extensions, ring groups, auto attendant settings, trunk configuration). The WiFi network names, passwords, and access point locations. The VLAN assignments and IP ranges. Any static IP addresses assigned to specific devices.

This documentation is invaluable for future troubleshooting, for onboarding new IT support, and for the next time you move. The businesses that document their setup during the move avoid the common problem of nobody knowing how anything is configured six months later when something needs to change.

Setting a review point

Schedule a review two weeks after the move to assess how things are working. Gather feedback from the team: are calls clear? Is the internet fast enough? Are there any recurring issues? Is anything not working that used to work at the old office?

This review is the point where you decide whether the current setup is meeting your needs or whether adjustments are needed. Minor issues can be addressed immediately. Larger issues (like discovering the internet connection isn't adequate for your full team's usage) are easier to solve now than six months from now when the urgency has faded but the frustration hasn't.

Next up: When to Upgrade Everything Versus Carrying Your Existing Setup Forward, which looks at whether to use the move as an opportunity to modernize.