The IT Manager's Office Move Survival Guide

An office move is one of the most complex projects any business will undertake, and for IT managers, it represents a uniquely intense challenge. You are responsible for ensuring that every piece of technology — from servers and switches to desk phones and printers — is safely decommissioned at the old site, transported without damage, and fully operational at the new location before staff arrive on the first morning. The margin for error is essentially zero. If employees cannot log in, access their files, make phone calls, or use their applications on day one, the entire move is considered a failure regardless of how beautifully the new office has been decorated.

Having supported hundreds of office relocations for businesses across the United Kingdom, from small firms moving within the same building to large organisations relocating across cities, we have distilled the essential knowledge into this comprehensive survival guide. Whether you are moving a 20-person team in Birmingham or a 200-person operation in London, these principles will help you deliver a smooth, successful technology transition.

This guide covers everything from initial planning and infrastructure assessment through to the move weekend itself and the critical first week in your new office. Follow it methodically, and you will transform what could be a chaotic, stressful experience into a controlled, well-executed project.

Every office move is unique, shaped by the size and complexity of the organisation, the distance between sites, the condition of the new building, and the specific technologies in use. A 30-person accountancy firm in Manchester will face very different challenges from a 150-person engineering consultancy in Bristol. Yet the underlying methodology remains the same: meticulous planning, thorough preparation, disciplined execution, and attentive post-move support. This guide provides that methodology in a form you can adapt to your specific circumstances.

Phase 1: Early Planning (12-16 Weeks Before Move)

The success of any office move is determined long before the removal vans arrive. The early planning phase is where you lay the groundwork for everything that follows. Start too late, and you will find yourself making rushed decisions that create problems on move day.

Audit Your Current Technology Estate

Before you can plan the move, you need a complete and accurate picture of what you are moving. Conduct a thorough audit of every piece of technology in your current office. This includes servers, network switches, routers, firewalls, wireless access points, desktop computers, laptops, monitors, printers, scanners, desk phones, video conferencing equipment, CCTV systems, and any specialist hardware specific to your business.

For each item, record the make, model, serial number, age, condition, and whether it will be moved to the new office, replaced, or decommissioned. This audit serves multiple purposes: it gives you an accurate inventory for insurance purposes, identifies equipment that should be upgraded rather than moved, and provides the basis for your new office technology plan.

Assess the New Office Infrastructure

Visit the new office as early as possible and conduct a detailed infrastructure assessment. You need to evaluate the existing network cabling, the location and capacity of network cabinets, the power supply arrangements, the cooling systems for server rooms, the number and placement of power sockets, and the building's internet connectivity options.

Many new offices — particularly those in older buildings being repurposed — will require significant infrastructure work before they can support modern business technology. Cat5 cabling may need upgrading to Cat6 or Cat6a. Additional power circuits may be needed for server rooms. Wireless access point locations will need to be planned based on the floor layout, wall materials, and expected user density.

Order Connectivity Early

Internet connectivity is the single most critical infrastructure element, and it is also the one with the longest lead time. In the United Kingdom, business-grade internet circuits — whether leased lines, FTTP, or dedicated fibre — typically require 60 to 90 working days for installation. Some providers in certain areas may take even longer. Order your new connectivity on the very first day of planning, and order a secondary backup connection from a different provider using a different physical route into the building.

Plan Your DNS and Domain Changes

An often-overlooked aspect of office moves is the cascade of changes required to your domain name system records, mail exchange records, and public-facing services. If your new office uses different public IP addresses — which is almost always the case — you will need to update DNS A records for any services hosted on-premises, MX records if your mail routing changes, SPF and DKIM records if your outbound email infrastructure is affected, and any firewall rules or VPN tunnel configurations that reference your old IP addresses. These changes require careful sequencing because DNS propagation takes time, and premature changes can cause service disruptions. Create a comprehensive list of every external service, partner connection, and remote access configuration that references your current IP addresses, and plan the switchover timing so that changes propagate during the move window rather than before or after it.

Phase 2: Detailed Planning (8-12 Weeks Before Move)

With the foundational assessments complete, you can now develop your detailed move plan. This is where the logistics become granular and the timeline becomes specific.

Create a Network Design for the New Office

Based on your infrastructure assessment and floor plan, create a detailed network design for the new office. This should specify the location of every network switch, wireless access point, server, firewall, and patch panel. It should include VLAN configurations, IP addressing schemes, and wireless channel planning. If you are implementing any new technologies as part of the move — such as VoIP telephony or a new Wi-Fi 6E system — factor these into the design now.

Pay particular attention to the wireless design. The physical characteristics of the new office — wall materials, ceiling heights, floor layout, glass partitions — will all affect wireless signal propagation differently from your current site. If budget permits, commission a wireless site survey before the move to ensure access point placement is optimised from day one. A survey-based wireless design eliminates the trial-and-error approach that leads to dead zones, interference, and frustrated users during those critical first weeks.

Coordinate with Third-Party Vendors

Most businesses rely on a web of third-party technology vendors and service providers whose involvement is essential for a smooth move. Your managed print provider will need to relocate or replace devices. Your telephony provider will need to port numbers or reconfigure SIP trunks. Your managed security provider will need to update monitoring configurations for the new network topology. Your ISP may need to perform work at both the old and new sites. Contact every vendor early, provide them with your move timeline, and confirm their availability on move weekend. A single vendor who is unavailable when needed can delay the entire project. Maintain a vendor contact sheet with escalation paths and out-of-hours numbers for every critical supplier, and ensure your move-day team has immediate access to it.

Develop the Move-Day Run Sheet

Create a minute-by-minute run sheet for move day. This document should specify exactly when each system will be shut down at the old site, who is responsible for disconnecting and labelling each piece of equipment, the order in which items will be loaded onto transport, the expected arrival time at the new site, the order of installation, and the testing procedures for each system. Leave nothing to chance or improvisation.

Coordination between the IT team, the facilities management team, and the removal company is essential during this phase. Ensure that the removal company understands which items are IT equipment requiring special handling and which are general office contents. Ideally, IT equipment should be transported separately from furniture and general items, using vehicles with appropriate suspension and climate control. Establish clear communication channels for move day — a dedicated group chat or radio channel that connects all team leads — so that everyone can relay status updates and flag issues in real time.

Time	Task	Responsible	Duration
18:00 Friday	Begin controlled shutdown of non-critical systems	IT Team Lead	1 hour
19:00 Friday	Final backup verification and server shutdown	Senior Engineer	2 hours
21:00 Friday	Disconnect and label all network equipment	Network Engineer	2 hours
23:00 Friday	Equipment loaded for transport	IT Team + Movers	2 hours
07:00 Saturday	Equipment arrives at new site	IT Team Lead	1 hour
08:00 Saturday	Core network and server installation begins	Full IT Team	6 hours
14:00 Saturday	Network testing and validation	Network Engineer	3 hours
08:00 Sunday	Workstation deployment and testing	Full IT Team	8 hours
07:00 Monday	IT floor-walking support as staff arrive	Full IT Team	All day

Phase 3: Pre-Move Preparation (4-8 Weeks Before Move)

The pre-move preparation phase is about eliminating risks and creating fallback options. This is when you ensure that if anything goes wrong on move day, you have the means to recover quickly.

Verify and Test Backups

Your backup systems should already be running reliably, but now is the time to verify them with additional rigour. Perform full test restores of critical data and applications. Confirm that your backup copies are complete, current, and stored in a location that is independent of both the old and new offices. If you use cloud backup, verify that restoration speeds are acceptable over your new internet connection. If you use physical backup media, ensure copies are stored securely off-site.

Communicate with Staff

Keep your colleagues informed about the technology aspects of the move. Tell them what to expect in terms of downtime, what they need to do with their equipment before the move (such as logging off and disconnecting peripherals), and what the first day in the new office will look like. Provide clear instructions about any changes to technology — new phone numbers, different Wi-Fi networks, updated printer locations, or changed login procedures.

Phase 4: Move Weekend Execution

Move weekend is where months of planning come together. If you have followed the preparation phases diligently, this should be an exercise in execution rather than problem-solving. Your run sheet guides every action, and your team knows exactly what to do and when.

The Friday Evening Shutdown

Begin the controlled shutdown of systems in the order specified by your run sheet. Start with non-critical systems — printers, secondary servers, development environments — and work towards the most critical systems last. Before shutting down each server, verify that the latest backup is complete and successful. Document the state of every system as you shut it down, noting any errors or unusual conditions that might affect the restart.

Transport and Handling

IT equipment requires careful handling during transport. Servers and switches should be transported in their original packaging where possible, or in purpose-built flight cases with adequate padding. Hard drives are particularly vulnerable to shock damage — if you are moving servers with mechanical hard drives, ensure they are well-cushioned and transported upright. Label every cable, every device, and every component. The time you spend labelling during disconnection will save you hours of confusion during reinstallation.

Installation and Testing at the New Site

Follow your network design to install equipment in the correct locations. Begin with core infrastructure — the firewall, core switches, and servers — and work outward to access switches, wireless access points, and workstations. Test each layer before proceeding to the next. Verify that the internet connection is active and performing to specification. Test internal network connectivity between all VLANs. Verify that servers are accessible and applications are responding correctly. Test printing, telephony, and video conferencing systems. Only when every system has been validated should you consider the technical move complete.

Phase 5: The First Week in the New Office

The move is not over when the last cable is plugged in. The first week in the new office is a critical period that requires dedicated IT support and vigilant monitoring.

Floor-Walking Support

Have IT staff physically present on every floor from the moment the first employees arrive. People will have questions, encounter minor issues, and need help adjusting to the new environment. A visible, proactive IT presence during this period builds confidence and prevents small problems from escalating into major disruptions.

Monitor and Optimise

Watch your monitoring systems closely during the first week. Network traffic patterns in the new office will differ from the old one, and you may need to adjust wireless channel configurations, switch port allocations, or bandwidth allocations. Pay particular attention to Wi-Fi performance — the physical environment of the new office (wall materials, ceiling height, furniture density) will affect wireless propagation differently from the old site.

The first week is also when you will discover the things you forgot. Perhaps a particular printer needs a different driver in the new location. Perhaps a conference room's display does not work with the new network configuration. Perhaps the kitchen's smart appliances need reconnecting to Wi-Fi. Handle these issues promptly and document them for future reference.

Conduct a Post-Move Review

Within two to four weeks of the move, hold a formal post-move review with your IT team and key stakeholders. Document what went well, what could have been improved, and any issues that were encountered along with their resolutions. This review serves several purposes: it identifies any lingering issues that still need attention, it provides valuable lessons for any future relocations, and it gives the team an opportunity to recognise the considerable effort that went into the project. The post-move review should also include a formal comparison of the technology environment before and after the move — confirming that all systems are performing to specification and that no degradation has occurred during the transition.

Update your disaster recovery and business continuity documentation to reflect the new office environment. Your recovery plans, which were written for the old site, will contain references to physical locations, network configurations, and local resources that no longer apply. Similarly, update your asset register, network diagrams, and any documentation that references the old office address, IP addresses, or circuit references. It is easy to defer this administrative work in the post-move period, but out-of-date documentation will cause confusion and delays if you ever need to invoke your recovery procedures.

Contingency Planning: What If Things Go Wrong

No matter how thoroughly you plan, you must prepare for the possibility that something will go wrong. The most common failure scenarios during office moves include internet connectivity not being ready, equipment damaged during transport, configuration errors that prevent systems from communicating, and power supply issues at the new site.

For each of these scenarios, prepare a documented contingency plan. If the internet is not ready, can you use 4G/5G backup connections to maintain basic operations? If a server is damaged, can you restore from cloud backup to temporary hardware? If the new office has power problems, do you have UPS systems to protect critical equipment? The goal is not to prevent every possible problem — that is impossible — but to ensure that when problems occur, you can respond quickly and effectively rather than descending into panic.

The Rollback Plan

One of the most important contingency measures — and one that is frequently overlooked — is the rollback plan. This is the documented procedure for returning operations to the old office if the new site proves fundamentally unusable on Monday morning. For the rollback plan to be viable, you need to retain access to the old office for at least one week after the move and keep the old internet connections active until you are confident the new site is fully operational. The cost of maintaining these overlapping services for a few extra days is trivial compared to the cost of having no fallback if a critical system fails at the new site.

Communication is also a vital part of contingency planning. Prepare template communications for different failure scenarios — a brief email to all staff if the morning start is delayed by an hour, a more detailed communication if a specific system is unavailable, and an escalation message to senior management if the situation is more serious. Having these templates ready means you can communicate clearly and quickly under pressure, rather than trying to compose thoughtful messages whilst simultaneously troubleshooting a technical crisis. Include your mobile phone number and those of key team members in these templates so that staff have a direct line to IT support if email itself is affected.