How to Handle IT During a Company Relocation
A company relocation compresses every IT risk into a single event. Internet circuits, network infrastructure, phone systems, security cameras, server rooms, and employee workstations all have to be decommissioned at one location and operational at another within a window that is almost always shorter than leadership expects. The businesses that survive a move without significant downtime are those that treated IT as a parallel workstream to the physical move rather than something that gets handled during the final week.
The difference between a smooth technology transition and a week of chaos is roughly ninety days of planning. Here is how to approach it.
Build Your IT Inventory Before Anything Else
Before packing a single cable, document every piece of technology in the current office. This inventory becomes the foundation for every decision that follows: what moves, what gets replaced, and what gets retired.
Walk every room and closet with a clipboard or spreadsheet and record every server, switch, router, firewall, access point, UPS, printer, phone, desktop, monitor, and peripheral. Note serial numbers, warranty status, and age. Equipment older than five years is often cheaper to replace than to move because it is approaching end-of-life regardless and the labor cost of disconnecting, transporting, and reconnecting aging hardware adds up quickly.
Map the logical infrastructure as well. Document IP address schemes, VLAN configurations, firewall rules, DNS records, DHCP scopes, VPN configurations, and any site-to-site tunnels connecting the current office to cloud services or other locations. This documentation will be critical when configuring the new environment and will expose any tribal knowledge that exists only in the head of whoever set up the network originally. The National Institute of Standards and Technology maintains frameworks for IT asset management that can guide a thorough inventory process.
Engage Internet Service Providers Ten to Twelve Weeks Early
Internet installation at a commercial building is the longest lead-time item in any office relocation. Fiber provisioning can take eight to twelve weeks depending on whether the new building already has lit fiber in its telecommunications closet. If the building has never had fiber service, the provider may need to trench or bore to bring a new line from the street, which adds permitting and construction time.
Order service at the new location as early as the lease allows. Request two circuits from separate providers if the business depends on connectivity for revenue-generating activities or has more than twenty employees. A single circuit means a single point of failure, and learning that lesson during the first week in a new office is expensive. Keep existing service active at the old location until the new circuits are tested and proven stable. Overlapping service for two to four weeks costs far less than the revenue lost to a connectivity gap.
Contact every provider tied to the current address: internet, phone, cloud services with IP-based access controls, and any colocation or data center services with cross-connects. Each one has its own disconnection and transfer procedures, and missing one can result in unexpected service termination.
Plan the New Office Network Architecture
A relocation is the best opportunity to fix every networking compromise made over the years at the old office. The ad hoc switches tucked behind desks, the consumer access point someone added because the WiFi did not reach the break room, and the unmanaged switch in the conference room all get left behind. The new office should be built properly from day one.
Work with a cabling contractor to install structured cabling during the buildout phase, before walls are finished and furniture arrives. Run Category 6A cable to every workstation location, conference room, and access point mounting position. Pull more drops than the current headcount requires because adding cabling after construction is finished costs five to ten times more per drop.
Design the wireless network based on a professional site survey of the new space rather than guessing access point placement. Wall materials, ceiling height, and the expected device density all affect coverage and throughput. Segment wireless into separate networks for corporate devices, guest access, and IoT equipment like printers and smart displays, each on its own VLAN with firewall rules preventing lateral movement. The Cybersecurity and Infrastructure Security Agency publishes guidance on network segmentation that applies directly to new office deployments.
Create a Detailed Migration Timeline
Working backward from the move date, assign every IT task to a specific week with an owner and a dependency chain. A typical timeline looks like this:
Twelve weeks out: Order internet circuits at the new location. Begin equipment inventory. Engage cabling contractor.
Ten weeks out: Finalize network architecture design. Order new equipment for anything being replaced rather than moved. Begin configuring firewalls, switches, and access points in a staging environment.
Eight weeks out: Structured cabling installation begins at the new site. Coordinate with the general contractor on power requirements for the server closet or network rack, including dedicated circuits and cooling.
Six weeks out: Internet circuits should be installed and testable. Begin configuring VPN tunnels, DHCP scopes, DNS, and firewall rules at the new location. Test site-to-site connectivity.
Four weeks out: Install and test wireless access points. Configure and test the phone system. Begin staging employee workstations with any new configurations needed for the new network.
Two weeks out: Conduct end-to-end testing of all systems at the new location. Test failover scenarios. Verify that every application and cloud service works correctly from the new IP ranges. Update any IP-based allow lists with vendors and partners.
One week out: Final data backup before the move. Communicate the IT timeline to all employees including what to expect, when systems will be down, and how to report issues. Prepare a physical move plan for any server and network equipment being transported.
Move weekend: Execute the physical migration. Bring systems online in dependency order: internet first, then core networking, then servers, then phones, then workstations. Test every critical system before declaring the move complete.
Protect Data Throughout the Move
A relocation creates data risk at every stage. Hard drives in transit can be damaged or lost. Servers powered down for the first time in years sometimes do not come back up. Cloud syncs interrupted by a connectivity gap can create conflicts. Every one of these scenarios requires a backup strategy that is tested before the move begins, not assumed.
Run full backups of every server, NAS, and critical workstation the week before the move and verify that each backup restores successfully. Store backup copies in at least two locations: one in the cloud and one on portable encrypted storage that travels separately from the equipment. If the business uses on-premise servers that are being physically moved, image every drive before the equipment is disconnected so there is a point-in-time recovery option if hardware is damaged during transport.
For businesses running critical applications on local servers, consider whether the relocation is the right time to migrate those workloads to cloud infrastructure. Moving a physical server across town requires careful packing, environmental control during transport, and the risk that a server that has been running continuously for years fails during the power cycle. Migrating to a cloud VM before the move eliminates that risk entirely and means the application is accessible from both the old and new offices during the transition period. The Small Business Administration provides guidance on backup and data protection practices for businesses of all sizes.
Address Phone Systems and Communications
How the phone system migrates depends entirely on what type of system is in use. Cloud-based VoIP platforms like Microsoft Teams Phone, RingCentral, or Zoom Phone travel with the user rather than the building, making the transition straightforward. Ensure that the new office network is configured with Quality of Service policies that prioritize voice traffic, and test call quality from the new location before the move date so any bandwidth or latency issues are resolved in advance.
Traditional on-premise PBX systems are far more complex to relocate. The physical hardware must be moved, reconfigured for the new network, and reconnected to trunk lines at the new location. Porting phone numbers from one carrier to another or from one address to another can take two to four weeks and requires coordination with both the losing and gaining carriers. If the business is still running an on-premise PBX, the relocation is a natural migration point to cloud communications, which eliminates the physical move entirely and modernizes the platform.
Do not forget about fax numbers, toll-free numbers, and any numbers published on marketing materials, business cards, or regulatory filings. Each one has a porting timeline that should be initiated well before the move.
Manage the Physical Equipment Move
IT equipment requires handling that a general moving company is not equipped to provide. Servers, switches, UPS systems, and network racks should be moved by a team that understands anti-static procedures, proper packing for sensitive electronics, and the importance of labeling every cable before disconnecting it.
Photograph every rack, patch panel, and cable run before disconnecting anything. Label both ends of every cable with a numbering system that maps to the network documentation. Pack servers and switches individually in anti-static bags with foam padding. Transport hard drives separately from the chassis when possible and never leave equipment in an unattended vehicle where temperature extremes or theft could cause loss.
At the new location, bring systems online methodically rather than reconnecting everything simultaneously. Start with the core network infrastructure: firewall, core switch, and internet connectivity. Verify connectivity to the outside world and to any cloud services. Then bring up servers in dependency order, starting with domain controllers, DNS servers, and DHCP servers before file servers, application servers, and databases. Only after core infrastructure is verified should employee workstations be connected and tested.
Communicate with Employees Early and Often
Employees need to know what to expect before, during, and after the move. Publish a clear timeline that includes when email will be unavailable, when phone lines will be down, when they should stop working at the old office, and when they can begin working at the new office. Provide instructions for any steps employees need to take themselves, such as backing up local files, undocking laptops, or signing into new WiFi networks.
Designate a help desk presence at the new office for the first two to three days after the move. Even with perfect planning, employees will encounter issues: a monitor that did not make the trip, a printer that is not mapped, a VPN client that needs reconfiguration, or a badge that does not open the new door. Having IT staff physically present and available converts those issues from frustrated help desk tickets into thirty-second fixes at the desk.
Set realistic expectations with leadership about productivity during the transition. A one-day office move typically means two to three days of reduced productivity as employees settle in, discover issues, and adjust to the new environment. Planning for that reality is better than promising a seamless transition and then explaining why half the team could not work on Monday.
Test Everything Before Declaring Victory
The move is not complete when the last box is unpacked. It is complete when every system has been tested under real-world conditions. Run through a checklist that covers every technology service the business depends on:
- Internet connectivity on both primary and failover circuits
- WiFi coverage and speed in every area of the office
- VPN access for remote employees connecting to the new office
- Phone system functionality including inbound, outbound, and transfer
- Printing and scanning from every workstation
- Access to file shares, databases, and line-of-business applications
- Security cameras, door access control, and alarm systems
- Backup jobs completing successfully to both local and cloud targets
- Video conferencing in every conference room
Any item that fails testing goes on a punch list with an owner and a deadline. The punch list should be reviewed daily for the first week and weekly for the first month until every item is resolved.
Use the Move to Modernize
A relocation is a forced infrastructure reset that happens rarely in the life of a business. It is the single best opportunity to retire technical debt, replace aging equipment, and implement changes that would be disruptive during normal operations. Replacing a five-year-old firewall, upgrading from 1-gigabit to 10-gigabit core switching, or migrating from an on-premise file server to SharePoint is dramatically easier when everything is being disconnected and reconnected anyway.
Evaluate every piece of equipment against a simple question: will this serve the business well for the next three to five years at the new location? If the answer is no, the relocation is the cheapest time to make the change because the labor to disconnect and reconnect the old equipment is already being spent. Replacing it at the new site avoids paying that labor cost twice.
An office relocation is too important to improvise. Contact We Solve Problems to plan and manage your IT relocation from inventory through go-live, ensuring zero surprises on move-in day.