Office relocations rarely fail because of the furniture. They fail when a server is unplugged before its data is verified, a licence key is left in a desk drawer, or a cloud configuration is lost because nobody treated it as part of the move. In London, tight loading bays and booked lifts can push IT teams into shortcuts, so the safest approach is to treat every piece of hardware as disposable and every piece of data as essential.
The Data You Cannot Afford to Lose Before the Servers Move
When a server leaves the old office, it stops being a working machine and becomes a heavy box. The business value is in the state it carries: databases, application data, virtual machines, configuration files, network settings, certificates, and the glue that holds user access together. A common mistake is to assume that a cloud subscription or a mirrored drive removes the need for a local backup. In practice, cloud services still need their own export and configuration backup, and a mirrored drive can replicate a deletion or corruption just as faithfully as it replicates good data. Before any server is powered down, IT teams should identify every service that will be interrupted: file servers, domain controllers, email relays, print servers, backup catalogues, licence servers, and any legacy application that only runs on one ageing machine.
For each, take a full backup and, where possible, an application-consistent snapshot. Record the hypervisor configuration, the virtual network layout, firewall rules, DNS and DHCP settings, and any encryption keys or recovery codes. Back up the backup system itself; a catalogue of previous backups is useless if the catalogue is lost. Store at least one copy on encrypted removable media and one copy offsite or in a verified cloud repository. Do not rely on a single hard drive travelling in the same van as the server. In London office moves, removal slots may be governed by building access hours, lift bookings, and controlled parking bays. That makes it even more important to finish the backup and verification before the removal crew arrives, rather than hoping to copy data while desks are being carried out.
Label every backup with the date, hostname, application, and restore instructions. Keep a printed and encrypted digital copy of the restore procedure. If a server must be shut down in a specific order, write that order down and assign one person to confirm each step. The goal is simple: when the server reaches the new office, the team should be able to rebuild it from documented backups without guessing which drive holds which month’s data.
Devices, Credentials and Operational Records: The Overlooked Backups
Desks and servers are obvious. Laptops, desktops, mobile phones, and the documents stored in user profiles are less obvious until someone cannot find a client contract or a design file. Before desks leave, IT teams should back up local user data, browser profiles, email archives, and any shared drives that live on individual machines rather than on a server. If the organisation uses Microsoft 365, Google Workspace, or another SaaS platform, check what is actually covered by the provider and what is not. Provider backup is not the same as a business backup: accidental deletion, retention gaps, and configuration errors can still remove data that the business needs. Export mailboxes, calendars, shared drives, and collaboration spaces where the platform allows it, and record the permissions and group memberships that control access.
Credentials are another category that often gets left behind. Administrative passwords, service account details, API keys, SSH keys, Wi-Fi credentials, VPN profiles, and multi-factor authentication recovery codes should be collected into a secure password manager or sealed emergency envelope. Do not write them on a sticky note attached to a monitor. The same applies to software licences, warranty documents, supplier contacts, and support contract numbers. These records are operational data, and losing them can delay the rebuild for days. A simple asset register with serial numbers, hostnames, and assigned users will help the team reconcile what has arrived at the new office against what was backed up and packed.
Do not forget the phone system, access control, and any building systems that IT supports. VoIP configuration, call routing rules, voicemail greetings, and extension lists should be exported or documented. If the old office has a server room with rack elevations, cable schedules, and network diagrams, photograph them and store the images with the backup register. These records are especially useful in London buildings where comms rooms may be small, shared, or accessed through a loading bay with limited hours. When the final sweep includes obsolete furniture, cabinets, and old hardware, it is worth a look at how professional clearance teams plan the sequence so that nothing essential is accidentally removed. Label backup media clearly and keep it separate from general office waste.
Testing, Labelling and Sequencing: How to Back Up Safely Before the Desks Leave
A backup that has never been restored is a hope, not a plan. Before the removal date, IT teams should test at least one critical restore to a spare machine or a virtual environment. Verify file counts, database consistency, and application logins. Use checksums where possible, and record the results in a simple backup log. The log should state what was backed up, where the copies are stored, who verified them, and when the verification took place. Two copies are better than one, and three copies in two locations are better than two. For smaller teams, that might mean an encrypted external drive, a cloud repository, and a copy kept by a responsible person who is not travelling with the removal van.
Sequence matters. Back up first, verify second, shut down third, label fourth, pack fifth, and transport sixth. If a server must remain live until the last moment, agree a cut-off time with the business and stick to it. In London, removal crews may need to use lifts, loading bays, and controlled parking zones, so a delay in shutting down a server can ripple through the whole schedule. Assign one IT contact to stay with the backup media and one to supervise the server removal. Keep backup media in a padded, water-resistant case, and do not stack it under heavy furniture. If the new office will not be ready immediately, consider a secure storage arrangement rather than leaving drives in a car or a corridor.
Finally, document the rebuild plan before the old office is empty. The plan should cover power-on order, network reconnection, DNS and DHCP restoration, application start-up, user account checks, and a post-move test of email, file access, printing, and remote access. Photograph the old server room and the new one so that cabling and rack positions can be compared. Label every cable and every drive with the same naming convention used in the backup log. This may feel slow while desks are being carried out, but it is faster than trying to reconstruct a domain controller from memory. The most successful office moves treat IT backups as part of the removal checklist, not as an afterthought once the desks have gone.
