Boxes at the Door, No Network Inside: The Office Move Is an IT Project
Photo: Hikaru Iwasaki, Public domain, via Wikimedia Commons
There is a particular kind of optimism that surrounds a small office move. Someone books a removal firm, someone else orders boxes, and everyone agrees that the IT side will 'sort itself out' once the desks are in. It rarely does.
The removal job moves furniture. An office move moves the business. Those are different projects, and the IT part starts weeks before anyone touches a packing tape dispenser.
The removal van is not the milestone
In the UK, broadband and cabling are the long poles. A new business line can take weeks to install, and that is before anyone discovers a missing wayleave, a landlord who needs to approve access, or a comms room that turns out to be a cupboard with no power. If the broadband order goes in after the lease is signed, the firm may be waiting long after the furniture has arrived.
This is not a reason to panic. It is a reason to treat the move as an IT project with a named owner, a simple plan, and a test day.
Weeks before: services and access
Start with connectivity. Check what is available at the new address, order early, and keep a 4G or 5G backup plan in mind. Do not cancel the old broadband until the new line has been tested and the old site is genuinely finished. If the firm runs phones over the internet, make sure the new connection can carry them.
Then look at cabling and the comms room. Cat6 cabling, patch panels, power, cooling, and a lockable door are not glamorous, but they decide whether the network works on day one. Confirm access times with the landlord or building management. Ask about the riser, lift bookings, and any permits needed for contractors. These are the small details that turn a two-hour job into a two-week delay.
Three weeks before: address plan and inventory
Do not clone the old network blindly. A small firm may not need a complicated setup, but it does need a plan for IP addresses, Wi-Fi, printers, and door access. Give printers static addresses or DHCP reservations. Label network ports by desk or room. Decide what moves, what is replaced, and what is retired.
Build an asset inventory: laptops, monitors, docks, printers, switches, access points, phones, and anything else with a plug or a serial number. Label boxes by room and desk, not 'misc cables'. On moving day, 'misc cables' is where morale goes to die.
Moving week: sequence beats speed
Get the comms room working before the desks are populated. Test the network with one laptop before connecting everything. Keep the old site running until the new line is live. If email is in the cloud, that part is easier, but file shares, printers, and door access still need checking.
Book a test day before staff return. Walk the building with a laptop and a phone. Test Wi-Fi in each area, print to each printer, open the shared drive, join a meeting room screen, and check the door access. Write down what fails. A test day is not a luxury; it is the difference between a smooth Monday and a queue at reception.
The test day that saves a week
On test day, have the broadband backup ready, the IT contact on call, and a simple list of what 'working' means. Can people sign in? Can they print? Can they reach the files they need? Can visitors get on the guest Wi-Fi without seeing the office network? Do the phones ring? If something fails, fix it before the staff arrive, not while they are standing in the doorway with a mug and a monitor.
Also plan the first morning. Do not schedule the whole company to return at 9am and expect IT to solve every laptop issue at once. Stagger arrivals if possible. Have a named person at the new office who can answer basic questions and escalate the rest.
Who owns it
Name an IT lead for the move, even if that person is the office manager or an external support provider. Give them one spreadsheet, one weekly 20-minute call, and the authority to make small decisions. The removal firm should not be deciding where the switch goes. The landlord should not be discovering the cabling plan on the morning of the move.
A small UK firm does not need a project management office to move office. It needs to accept that the move is an IT project, not a removal job. Start early, test before people return, and keep the old line alive until the new one works. Boxes at the door are fine. Boxes at the door with no network inside are an avoidable problem.