Moving offices is a data-center migration wearing a cardboard costume

Every office move goes the same way: the lease is signed six weeks out, everyone thinks about desks and boxes and the wifi, and the internet circuit at the new building is ordered two weeks out — which is when the provider says the install takes six to eight weeks. Then the team works from a coffee shop for a fortnight while the "simple move" becomes the most expensive outage of the year. An office move is a migration project with a deadline, movers who drop things, and a landlord who controls your physical security — and it deserves the same runbook discipline as any other migration. The first-30-minutes instinct applies: the failures are predictable, so they get a checklist, not a memory.

1. The survey happens before the move, not during it

• Order the connectivity first; everything else is negotiable. Business fiber installs take six to eight weeks in most buildings, sometimes longer if the suite has never been wired. Order the circuit the week the lease is signed, confirm the install date in writing, and plan the move date around the confirmed live date — not the other way around. If the new building's only option is a consumer-grade circuit, that is a finding now, not on moving day.
• Walk the new space with the network map. Where does the rack go, where do the drops go, is there a locked closet or rack (the server hardening checklist applies to the closet, not just the servers), where are the power circuits, and is the ceiling accessible for cable runs. Photograph everything on the walk; the photos are the as-built documentation you will not have time to write later.
• Count power, heat, and noise like a data-center would. A closet with a NAS, a switch, and a UPS needs airflow and its own circuit; a closet that shares a wall with the kitchen fridge trips breakers at lunch. The server monitoring checklist should gain a temperature row the week you move — the new room's thermal profile is unknown and summer is real.
• Verify what the building provides and what it blocks. Shared buildings often have their own management network on "your" wiring, security cameras on your VLAN, and a property manager with opinions about antennas and satellite dishes. Ask in writing what is included; the answers belong in the move runbook next to the circuit install date.

2. The pre-move backup is the actual insurance

• Everything gets a fresh backup the week before, and the backup is tested, not assumed. The move puts every disk, NAS, and cable through vibration, cold cars, and unfamiliar hands. A restore test of the backup that will matter if a drive does not wake up is the entire insurance policy — the backup restore test checklist is the procedure, and "we backed up last month" is not a backup.
• Two copies leave the building separately. One backup travels with a person, one goes to cloud or a second site. The single bag with all the drives in it that rides in the same van as the NAS is the classic move-day failure — the recovery mindset is the same: no single failure may reach both copies.
• Photograph and label the old wiring before unplugging anything. Every rack, every cable run, every wall port, phone-first. Labels go on both ends of every cable. The three hours this costs saves three days of "which port did the printer use?" at the new site — and the photo set doubles as evidence for the security deposit conversation.
• Inventory what moves and what does not. The move is the best moment for a device register: serial numbers, what is being decommissioned instead of moved (the old printer nobody loves), and what gets replaced rather than re-racked. Anything not moving gets wiped or destroyed per the data deletion checklist before it is left behind — decommissioned hardware in a dumpster is a data breach with a lid on it.

3. Packing and moving the gear

• Servers and NASes travel in their original boxes or padded cases, carried, not stacked. Spinning drives in a moving van are the single most at-risk asset of the whole project. The backup from section 2 is what makes a dropped NAS an inconvenience instead of an extinction event; belt-and-suspenders is fine here.
• Nothing with a screen or a disk rides loose. Monitors in crates, drives in antistatic bags, security keys and spare laptops in one numbered box that a named person personally carries. The device-loss runbook is written for exactly the environment of a moving day: unfamiliar hands, no chain of custody, no badge cameras.
• Label by destination, not origin. Every box gets the name of the room and desk it lands at in the NEW office. Boxes labeled "misc cables" are boxes that stay sealed for a year; boxes labeled "marketing desk 3 — dock + keyboard" are unpacked in the first hour.
• The critical kit rides in a car, not the van. Firewall, core switch, the NAS or its backup, security keys, spare laptops, the modem for the new circuit, and a printed copy of the network map and credentials vault access. If the van is a day late, the office still comes online.

4. First day at the new office: connectivity before comfort

• The standing order is: circuit, firewall, wifi, then everything else. Internet live, firewall on, core switch up, test VLANs, then wifi. Desks, chairs, and the coffee machine are somebody else's day-one job; the network being down blocks every one of the team's first-day tasks, so it gets the first hours of the day and the best troubleshooting slot of the week.
• Test the failover story while the installer is still in the building. Power-cycle the circuit, unplug and re-plug the handoff, confirm the UPS holds the closet through a breaker flip, and verify the failover circuit or LTE backup if one exists — the day everything is new is the one day the vendor's engineer is standing next to you when something is wrong.
• Print and post the two things nobody remembers: the wifi password policy (per the wifi security checklist — guest network separate from the office network from day one, not "temporarily" shared) and the new building's alarm and access rules. The door code policy starts its life in the new building on day one, with a fresh vault entry per door.

5. The new building resets your physical security — take the upgrade

• The new building is a rekey you did not have to argue for. Old keys do not open the new doors, which means the copy-count problem from the key inventory register resets to zero — if the register is written before new keys are issued. Named holders, stamped copies, no master keys to the whole floor unless the register says so; the move is the one moment in an office's life when clean key discipline is free.
• Alarm codes, badges, and the visitor desk start fresh too. Set the alarm-code policy on day one — per-user codes where the panel supports it, quarterly rotation on the calendar — and stand up the badge access control before the first visitors arrive. The visitor log starts on day one; retrofitting it later is how the "who was in the office that day?" question becomes unanswerable.
• The closet or rack room gets its access tier on day one. The room with the switches and the NAS is the highest-value target in the office; its key or code goes on the register's highest tier, and it does not share a code with the front door. Landlord and building-staff master keys are recorded in the register's vendor section with the name of whoever accepted them.
• Cabling discipline is a security decision, not tidiness. The new office is the only day the patch panel can be labeled, the switch ports mapped to desks, and the unmanaged switch under someone's desk prevented from ever existing. The annual review will thank the person who took the extra hour.

6. Leaving the old office: the decommission checklist

• Everything left behind is either wiped, destroyed, or deliberately abandoned-and-documented. Hard drives from decommissioned machines leave with the team or get destroyed; cables that stay are cut; the old NAS cabinet is emptied. The offboarding rule applies to rooms: an office nobody fully clears is a warehouse of credentials — keys in drawers, notes on whiteboards, a hub still blinking with a live VPN.
• The old circuit and accounts are cancelled deliberately, not by non-payment. Cancel in writing, keep the confirmation, and strip the old address from every system that uses it for verification — billing accounts, vendor portals, insurance, the mailroom redirects. The old address in a password-reset answer is social engineering bait for the phishing crowd.
• Update the physical-address records everywhere within the week. Legal documents, insurance, the security-questionnaire answers customers ask for (the questionnaire template mentions facilities), the DNS TXT records if the address appears in SPF-adjacent services — an office move has a long tail of paperwork, and the checklist catches what memory does not.
• Close the move the way incidents close: one postmortem page — what took longer than planned, what the checklist missed, what the next move (or the next new site) inherits. The postmortem template fits, and the second office move should cost a third of the first.

An office move is a migration: survey and circuit order first, fresh tested backups with two copies traveling separately, photographed-and-labeled wiring, critical kit in a car rather than the van, connectivity-first on day one, and a full physical-security reset at the new building — rekeyed doors, register-written keys, tiered codes, day-one visitor log — then a deliberate decommission of the old site. The Ops Starter Kit ($14) includes the checklists and runbooks that structure weeks like this one, and the Automation Starter Pack ($19) schedules the follow-ups (backup tests, code rotations, address sweeps) so the move's loose ends actually close.