Lessons Learned from 100 Office IT Moves

Over the past decade, Cloudswitched has delivered more than one hundred office IT relocations across the United Kingdom — from single-floor shuffles within the same building to full-scale multi-site migrations spanning London, Manchester, Birmingham, Edinburgh, and beyond. Every move has been shaped by the unique circumstances of the organisation, the constraints of the new premises, and the particular technology stack in play. Yet clear patterns emerge. The same mistakes recur across industries, and the same principles separate smooth transitions from costly disasters.

This article distils the most important lessons from those hundred-plus projects into a practical guide. Whether you are planning a move for ten people or ten thousand, these insights will help you protect uptime, control costs, and keep your team productive throughout the transition.

The True Cost of Getting It Wrong

Before we explore the lessons themselves, it is worth understanding what is at stake. A poorly managed office IT move does not simply cause inconvenience — it inflicts measurable financial damage. Staff sitting idle because their phones and computers are not working, customers unable to reach you, data lost during the transition, and emergency call-out fees from engineers scrambling to fix problems that should have been prevented.

These figures are not abstract. They come from real projects we have managed and real problems we have been called in to fix when things have gone wrong. The difference between a well-planned IT move and a chaotic one is not subtle — it is the difference between a business that opens on Monday morning as normal and one that spends the first week of its new lease apologising to clients.

Lesson One: Start Planning the IT Move Before You Sign the Lease

The single most common mistake we see is treating the IT move as an afterthought. The lease is signed, the interior designers are booked, the removals company is scheduled, and only then does someone ask, “What about the IT?” By that point, critical decisions have already been locked in — decisions about floor layouts, cable routes, riser access, and power distribution that directly affect your technology infrastructure.

In an ideal scenario, your IT partner should survey the new premises before you commit to the lease. They need to assess broadband availability, check whether the building has adequate power and cooling for your server room or comms cabinet, verify that there are sufficient network points or that cabling can be installed, and confirm that mobile signal strength is adequate for your needs.

We have seen organisations sign leases on buildings where the only available internet connection was a basic ADSL line with 8 Mbps download speed. For a team of fifty people relying on cloud applications, that is a non-starter. Discovering this after signing a five-year lease is an expensive lesson.

Lesson Two: Audit Everything Before You Move Anything

You cannot move what you do not know you have. A comprehensive IT asset audit is the foundation of every successful move. This means documenting every piece of hardware — servers, switches, routers, firewalls, access points, desktop PCs, monitors, printers, scanners, phones, and peripherals — along with their current locations, configurations, network addresses, and dependencies.

It also means documenting your software landscape. Which applications run on which servers? Which services depend on which network connections? What are the IP address ranges, VLAN configurations, and firewall rules that keep everything working? This information may exist in documentation, but in our experience, that documentation is almost always incomplete or out of date.

We always conduct a physical walk-through of the existing premises, opening every cabinet, tracing every cable, and photographing every rack. On more than one occasion, we have discovered critical infrastructure that nobody in the organisation knew existed — a backup server tucked under a desk, a network switch balanced on top of a filing cabinet, or a legacy phone system hidden in a cupboard that still handled inbound calls for a major client.

Lesson Three: Connectivity Is the Foundation

If there is one lesson that dominates all others, it is this: get your internet and voice connectivity sorted first. Everything else depends on it. Cloud applications, VoIP phone systems, email, remote access, video conferencing, cloud backup — all of these require reliable, high-bandwidth internet connectivity. If the connection is not ready on move day, nothing else matters.

We always recommend ordering connectivity as early as possible — ideally the moment the lease is agreed in principle. We also strongly recommend installing a 4G or 5G backup connection as a failover. On numerous occasions, this backup has saved the day when the primary connection was delayed or experienced faults during the critical first week.

Lesson Four: Phase the Move Wherever Possible

The big-bang approach — moving everything and everyone in a single weekend — is tempting because it appears simpler and cheaper. In reality, it concentrates all your risk into a single window and leaves no room for error. If something goes wrong at 2 AM on Sunday morning, there is no fallback. Everyone arrives on Monday to a building that does not work.

Wherever possible, we advocate phasing the move. A typical three-phase approach might look like this:

Phase One (two to four weeks before main move): Install and configure core infrastructure at the new site. This includes the comms rack, core switching, firewall, wireless access points, and server infrastructure. Get the internet connection active and tested. Set up the phone system. Run cabling if required. This phase should be invisible to end users — they continue working at the old site while the new site is being prepared.

Phase Two (the main move weekend): Relocate user equipment — desktops, monitors, peripherals, and personal items. Reconnect and test each workstation. Move any remaining server or network hardware. This is the critical window, and because the core infrastructure is already in place and tested, the risk is dramatically reduced.

Phase Three (first week in new premises): Floor-walk support. Engineers on site to resolve teething problems, help users with printers and scanners, fine-tune wireless coverage, and address any issues that only emerge once the full team is working in the new environment.

Lesson Five: Label Everything Obsessively

This sounds trivial. It is not. In the chaos of a move, unlabelled cables, unlabelled boxes, and unlabelled devices create hours of unnecessary work. We label every cable at both ends with a unique identifier that maps to our documentation. We label every box of equipment with the user's name, their new desk location, and a contents list. We label every port on every patch panel and every switch.

The investment in labelling is small. The time saved is enormous. On one project, the removals company mixed up boxes between two floors. Because every box was labelled with the destination desk number, we were able to redirect them in minutes rather than spending hours working out whose monitor was whose.

Lesson Six: Test Before the Team Arrives

Never rely on the assumption that everything will work. Before the main workforce arrives at the new premises, every system must be tested. This means physically sitting at a sample of desks, logging in, checking email, making phone calls, printing documents, accessing shared drives and cloud applications, testing the VPN, and verifying that every critical business application functions correctly.

We also test non-obvious things: Does the video conferencing system in the boardroom connect properly? Can visitors connect to the guest Wi-Fi? Do the door access systems work with existing key cards? Does the kitchen display board still show the company dashboard? These small details matter because they affect the user experience on day one.

Lesson Seven: Communication Prevents Panic

Your staff are not IT professionals. They do not understand the technical complexity of what is happening behind the scenes. What they do understand is whether their computer works, whether they can answer the phone, and whether they can do their job. Clear, proactive communication before, during, and after the move transforms the experience.

We recommend issuing a series of communications: an initial announcement explaining the move timeline and what to expect, a detailed guide explaining what staff need to do (label their equipment, pack personal items, log off computers by a specific time), a day-one welcome guide explaining the new setup, and a clear process for reporting problems.

The organisations that communicate well experience far fewer support tickets and far less anxiety among their teams. The organisations that communicate poorly end up with panicked staff calling mobile phones at 7 AM because they cannot find their desk.

Lesson Eight: Do Not Forget the Phones

Voice communication is often the forgotten element of an office move. Modern VoIP phone systems are relatively portable — handsets can often be unplugged from one location and plugged in at another, inheriting their settings via the network. But this only works if the network infrastructure at the new site is configured correctly, the VoIP VLAN is set up, quality of service rules are in place, and the phone system can reach its host (whether on-premise or cloud-based).

Traditional analogue or ISDN phone systems present a different challenge. Number porting can take weeks, and any delays will leave your business unreachable on its main telephone number. With the PSTN switch-off progressing across the UK, many businesses are using their office move as the trigger to migrate to a cloud-hosted VoIP platform — a sensible decision, but one that requires its own planning and lead time.

Lesson Nine: Security Must Not Be Compromised During Transit

An office move is a period of heightened security risk. Equipment is in transit, doors are propped open for removals staff, temporary access is granted to contractors, and critical infrastructure may be powered down and physically accessible. We have seen hard drives go missing during moves, laptops disappear from unlabelled boxes, and sensitive documents end up in skips alongside old furniture.

Our approach includes maintaining a chain-of-custody log for all IT equipment, ensuring servers and storage devices are transported in secure, locked cases, verifying that all equipment arrives at the destination, and wiping any decommissioned hardware using certified data destruction methods. Physical security during a move is just as important as cyber security during normal operations.

Lesson Ten: Plan for Decommissioning the Old Site

The move is not finished when the last person leaves the old building. Equipment may remain, leased lines need to be cancelled, alarm systems need to be deactivated, and any IT infrastructure left behind needs to be dealt with. Failing to cancel internet circuits or phone lines at the old site will result in ongoing monthly charges that can persist for months before anyone notices.

We maintain a decommission checklist for every project that covers disconnection of all services, retrieval or secure disposal of all hardware, removal of any data from on-site storage, cancellation of all utility and telecom contracts tied to the old address, and a final walkthrough to confirm nothing has been left behind.

Bringing It All Together

The thread running through every one of these lessons is the same: preparation. The organisations that invest time and resource in planning their IT move properly are the ones that experience smooth transitions with minimal downtime. The ones that treat IT as an afterthought are the ones that spend their first month in new premises fighting fires.

An office move is disruptive by nature, but the IT component does not have to be the source of that disruption. With the right partner, the right plan, and the right execution, your technology can be the one thing that works perfectly from the moment you open the doors.

Frequently Asked Questions

How far in advance should we start planning our IT move?
We recommend beginning IT planning at least twelve weeks before your target move date. If you need a new leased-line internet connection, allow sixteen weeks or more. The earlier you start, the more options you have and the lower the risk of delays.

Can we move our IT over a weekend without disruption?
Yes, if the new site is pre-staged with core infrastructure beforehand. The main user equipment move can then happen over a weekend with minimal risk. We typically work Friday evening through Sunday, with engineers on site Monday morning for floor-walk support.

What happens to our phone numbers when we move?
Phone numbers can be ported to your new location, but the process varies depending on your provider and the type of system you use. VoIP numbers are highly portable. Traditional landline numbers may require porting through Openreach, which can take two to three weeks.

Do we need to rewire the new office?
It depends on the condition of the existing cabling infrastructure. We always conduct a cable survey to assess whether existing network points are adequate, whether they are Cat5e or Cat6 standard, and whether additional points are needed for your layout. Many modern offices use Wi-Fi extensively, reducing the need for cabling to every desk, but core infrastructure and access points still require wired connections.

What if our internet is not ready on move day?
This is exactly why we recommend installing a 4G or 5G backup connection at the new site. It provides sufficient bandwidth for essential operations while the primary connection is being resolved. We have used this failover approach on dozens of projects, and it has prevented significant downtime every time.