Office move IT checklist work is the part of a relocation that gets scoped last and bites first. The lease is signed, the removal firm is booked, the furniture is chosen — and then somebody finally asks when the internet will be live in the new building. The answer, far too often, is a date well after the day the first staff are supposed to sit down and work there.
That single gap causes most relocation pain. Everything else in a move is a logistics problem with a van-shaped solution. Technology is a lead-time problem, and lead times cannot be compressed by hiring more people or working a longer weekend. A circuit ordered in week one behaves very differently from the same circuit ordered in week nine, and no amount of goodwill from a provider changes that.
This guide is a practical office move IT checklist for UK businesses relocating anywhere between ten and two hundred staff. It runs from the survey you should do before signing, through connectivity, cabling, devices, telephony, cloud systems and security controls, to the move weekend runbook and the snagging week that follows. Firms already working with a managed IT services partner will recognise the sequencing; firms handling it in-house will find the office move IT checklist most useful read as a set of deadlines counted backwards from move day.
One framing point before the detail. Treat this as a change programme with a fixed, immovable deadline rather than as a house move. The discipline that comes with that framing — a named owner, a written cutover plan, an agreed rollback and a freeze on unrelated changes — is what separates a relocation nobody remembers from one that costs a fortnight of productivity. Every item on the office move IT checklist below assumes it.
Table of contents
- Why an office move IT checklist starts three months out
- Connectivity: the longest lead time in the whole move
- The building survey your office move IT checklist must include
- Devices, endpoints and the asset register
- Phones, meeting rooms and everything that is not a laptop
- Cloud systems and the servers you still own
- Security controls your office move IT checklist cannot skip
- Move weekend: the runbook, hour by hour
- Office move IT checklist tasks for the first week in the new building
- Costs, suppliers and what to hand your provider
- Final thoughts: treat the move as a deadline, not an event
Why an office move IT checklist starts three months out
Three months is not a comfort margin. It is the shortest window in which the long-lead items can be ordered, surveyed, delivered and tested without paying to expedite everything. Six months is better where the building needs new fibre. Under eight weeks you are no longer planning a move; you are choosing which compromises to accept.
The lead-time items that decide your move date
Four things drive the critical path: the internet circuit, physical works in the comms room, structured cabling and floor boxes, and number porting for the phone system. A leased line into a building with no existing fibre can take sixty to ninety working days, sometimes longer where a road crossing or a landlord wayleave is involved. Every other task on your office move IT checklist can be resequenced. Those four cannot.
What actually causes move-day downtime
Downtime is rarely caused by the thing everybody worried about. It is caused by the small dependency nobody wrote down: the card machine that authorises against a fixed IP address, the label printer with a hard-coded destination, the finance package licensed to a server name, the intruder alarm dialling out over a copper line being ceased on the Friday. A written inventory, cross-checked against the office move IT checklist, is the only real defence.
Who owns the office move IT checklist
One named person owns it, and that person is not the office manager and not the removal firm. They need enough authority to freeze changes and enough diary time to chase suppliers weekly. Where there is no internal IT lead, the role is worth buying in explicitly rather than assuming a provider will absorb it. An office move IT checklist without a single accountable owner quietly becomes four partial checklists held by four people.
Build the plan backwards from move day
Set the date first, then count the office move IT checklist backwards from it. Circuit ordered at minus twelve weeks. Building survey at minus ten. Cabling booked at minus eight. Devices audited at minus six. Porting notice served at minus four. Runbook written and reviewed at minus two. Change freeze at minus one. Working forwards from today produces a plan that finishes whenever the tasks happen to finish, which is always later than the lease allows.
Connectivity: the longest lead time in the whole move
If one item on the office move IT checklist deserves obsessive attention, it is the circuit. Almost everything else can be improvised for a few days. A building with no working internet cannot run a modern business for an hour, and there is no rental equivalent that fills the gap at full speed.
Order the circuit before you sign the lease
Ask providers for a formal quote against the new address during due diligence, not after completion. The quote reveals whether fibre already terminates in the building, whether the landlord’s riser is usable, and whether an excess construction charge is coming — occasionally five figures where new duct or a road crossing is needed. That number belongs in the property decision, not in a surprise email six weeks later.
Choose the right access type for the building
A dedicated leased line gives you a symmetric, uncontended service with a hard service level and a fix time measured in hours. FTTP is cheaper, faster to deliver and usually asymmetric with a best-efforts fix. For most offices under fifty staff, FTTP plus a second connection on a different technology is the pragmatic answer. Above that, or wherever voice and remote access carry the business, a leased line earns its cost. Record the choice and its published fix time on the office move IT checklist, because everything else is planned against it.
Keep the old line running in parallel
Do not cease the outgoing circuit on move day. Overlap it by at least two weeks and preferably a month. The overlap costs one month of line rental and buys a working fallback, a clean window to move mail flow and DNS, and somewhere to run the old site’s alarm and card machines until they are re-provisioned. It is the cheapest insurance on the entire office move IT checklist.
Backup connectivity and tested failover
The office move IT checklist should provision a second path before move day, not after the first outage. A 5G router with automatic failover costs little and covers the fortnight when everything is unfamiliar and every fault looks catastrophic. Configure and test the failover in the old office, where you can watch it fail safely. A backup circuit first tested during a live incident is not a backup.
Fast internet is not the same as a fast network
A quick circuit arriving at a poor internal network produces complaints identical to a slow circuit. Budget enough access points, place them from a survey rather than from the ceiling grid, and put wired connections into meeting rooms and any desk running voice or video all day. This is the most common false economy in an office relocation.
The building survey your office move IT checklist must include
Walk the new building with somebody technical before the lease is signed, and again once you have keys. Photograph everything. This part of the office move IT checklist answers questions that otherwise become expensive assumptions, and it costs an afternoon.
Comms room, power and cooling
Find where incoming services terminate and whether there is a room you can secure. Check the power: a dedicated circuit rather than a spur shared with the kitchen, and enough sockets for the rack plus a UPS. Check cooling, because a cupboard holding a switch stack and a small server will reach thirty-five degrees by August. Check the lock. A comms room anybody can walk into is a security finding, and it belongs on the office move IT checklist before it becomes an incident.
Structured cabling and floor boxes
Count the desks, then count the outlets. Most buildings arrive with fewer than you need, in the wrong places. Plan two data outlets per desk plus spares for printers, access points and meeting rooms, and have structured cabling installed and certified rather than run loose under desks. Testing matters: an untested run failing at ten per cent packet loss gets blamed on the internet for a month.
Wireless survey before, not after
A predictive survey against the floor plan costs a few hundred pounds and prevents the most tedious class of post-move complaint. Solid walls, foil-backed plasterboard, glass meeting pods and metal shelving all change coverage in ways nobody guesses correctly. Run the survey before cabling is installed, so access point positions have outlets waiting for them.
Access control, door entry and CCTV
These sit awkwardly between facilities and IT, which is how they end up unowned. Establish early whether the systems are inherited from the previous tenant, whether the landlord retains control, and what they connect to. Door entry panels and CCTV recorders frequently need network ports, static addresses and a route out — decisions worth making deliberately rather than at eight on the Friday evening.
Landlord permissions and lift bookings
Nothing on an office move IT checklist is slower than a permission you discover late. Riser access, core drilling, out-of-hours working, goods lift bookings and parking suspensions all sit with the landlord or building management, and every one of them carries a notice period. Ask for the full list in writing during fit-out planning and give each approval its own date on the plan.
Devices, endpoints and the asset register
Devices are the visible part of a move and the part staff judge it by. They are also where the unglamorous half of an office move IT checklist — knowing precisely what you own — pays for itself several times over.
Audit every device before anything is packed
Produce a register covering every laptop, desktop, monitor, dock, handset, printer, scanner and screen: model, serial, age, warranty status, assigned user and whether it moves. Businesses running proper IT asset management can export most of this in an afternoon; everyone else walks the floor with a spreadsheet. Expect fifteen per cent more equipment than anybody believed existed.
Decide what moves, what gets replaced, what gets retired
A move is the cheapest moment to retire hardware, because you are already handling every item and paying to transport it. Anything out of warranty and past four years is usually cheaper to replace than to move, insure and support for another year. Set that rule numerically in the office move IT checklist before you start, so the conversation is about policy rather than about individual attachments to particular machines.
Packing, labelling and insurance
Label at item level and destination level: what it is, who it belongs to, and which desk it lands on. Photograph the back of anything with more than two cables. Check whether goods in transit are genuinely covered — office policies frequently exclude IT equipment in a third-party van, and removal firm liability is often set per kilogram, which is close to worthless for a rack of switches. Confirm the cover in writing as you work through the office move IT checklist.
Printers, scanners and the forgotten peripherals
Multifunction devices carry service contracts tied to an address, static addresses on the network, scan-to-folder settings that break on any address change, and a footprint needing power and data exactly where they land. Tell the supplier the move date early. A device relocated without notice can void its maintenance agreement and will certainly not be reconfigured for free.
Endpoint enrolment and the state you carry over
Devices managed through a modern endpoint platform care very little where they physically sit, which is the argument for enrolling them before the move rather than after. Where device management is already in place, a laptop plugged in at the new office receives policy, wireless profile and printer mappings untouched. Where it is not, somebody visits every desk twice.
Phones, meeting rooms and everything that is not a laptop
Telephony has its own notice periods and its own way of failing quietly, so the office move IT checklist has to treat it as seriously as the internet circuit. Meeting room technology has no notice period at all and fails loudly, in front of clients.
Number porting and the notice window
Porting numbers between providers takes ten to twenty working days once the paperwork is right, and the paperwork is frequently not right first time — a mismatched billing address or trading name restarts the clock. Start at minus six weeks; on the office move IT checklist this sits alongside the circuit order, not behind it. If you still run ISDN or analogue lines, the UK PSTN switch-off makes a relocation the natural moment to go fully cloud-based rather than reinstate copper somewhere new.
Meeting room audio and video
Every room needs a screen, a camera, a microphone covering the whole table, a way to join a call in under a minute and enough network to carry it. Decide the room standard once and repeat it, because rooms that each behave slightly differently generate a support call for every unfamiliar user. Test each room with a real call before anybody is allowed to book it.
Door phones, alarms and card machines
These are the items that reach the office move IT checklist late, if at all. Intruder alarms and lift phones may still dial out over a line you are ceasing. Card machines may authorise over a fixed address. Access control panels may expect a route to a cloud service. Each has a supplier, a lead time and a configuration change — and each is discovered on move weekend if it was not written down in week two.
Reception, signage and the small visible things
Digital signage, visitor sign-in tablets, the doorbell nobody claims and the screen behind reception all need power, network and an owner. Individually trivial, they cumulatively account for a surprising share of the snagging list. Assign them in advance to whoever owns the meeting rooms.
Cloud systems and the servers you still own
How much a move hurts is largely decided by how much still runs on hardware inside your building. A business whose systems are already hosted moves people. A business with an on-premises server moves people and a dependency, and the office move IT checklist splits neatly along that line.
What is worth moving to cloud before you move offices
A relocation is a natural forcing function for cloud adoption, because you are already paying to relocate the alternative. File shares, mail and line-of-business applications with a hosted option are the obvious candidates. The caution is scope: complete one significant platform migration before the move, then move offices. Two simultaneous cutovers double the surface area and halve your ability to diagnose anything, which is why the office move IT checklist keeps them apart.
Physically relocating a server
If a server has to travel, treat it as a planned outage rather than a transport job. Take a full backup and verify it restores somewhere else. Power down cleanly. Move it in a car, not stacked in the van behind the desks. Have destination rack, power and network ready before it arrives, and rehearse the boot sequence — a machine that has run four years without a restart occasionally declines to come back.
DNS, licensing and address records
Lower DNS time-to-live values a week ahead so changes propagate in minutes rather than a day. Then list everything tied to your old public address: mail records, VPN endpoints, remote access rules, supplier allow-lists, software licensed to an IP or hostname, and any partner firewall that trusts you by address. Cloud computing removes most of these dependencies, but rarely every one.
Backups you have actually tested
A move is the worst possible week to discover a backup job has been failing since March. Verify the jobs run, that copies are stored somewhere other than the building you are leaving, and that a restore has been tested end to end within the last quarter. This is the one office move IT checklist item with no acceptable workaround.
Licences, subscriptions and the address change nobody does
Software licences, domain registrations, certificates, hosting accounts and support contracts all carry a registered address, and several of them send renewal notices to it. Put the update on the plan rather than leaving it to whoever notices, and record where each contract actually lives while you are in there.
Security controls your office move IT checklist cannot skip
Moves create a temporary state where the normal controls do not apply: doors propped open, equipment in transit, unfamiliar contractors on site and an IT team too busy to read alerts. The security half of an office move IT checklist is the part most often deferred, and the fortnight either side of the move is exactly when it matters.
Physical security at both ends
For a week or two you effectively run two insecure buildings. Equipment sits in unlocked rooms at the old site and unattended at the new one. Keep devices in a lockable room or cage overnight, sign equipment in and out against the asset register, and do not park the rack in reception because the comms room is not finished. Most loss during a move is opportunistic rather than sophisticated.
Data protection and secure disposal
Anything being retired holds data, including printers with internal drives and old backup media in a cupboard. Use a certified disposal supplier and keep the destruction certificates — under UK GDPR you remain the controller for that data until it is verifiably destroyed. Organisations with mature data protection practice treat disposal as part of the move plan, not as a skip on the last day.
Network segmentation on day one
A new network is the rare chance to build the segmentation you have been meaning to introduce. Separate guest wireless from corporate, put printers, cameras, door entry and building systems on their own segment, and keep any legacy device that cannot be patched away from everything else. Retrofitting this into a flat network later is a project; doing it while the cabling is terminated is an afternoon, and it is the highest-value line on the security half of the office move IT checklist.
Insider and contractor risk during the move
Leavers, contractors and temporary help all gain access during a move, and access granted in a hurry is rarely reviewed afterwards. Review accounts before the move rather than after, remove the ones that should have gone months ago, and issue contractors time-limited credentials on the guest segment. Good cybersecurity during a relocation is mostly ordinary discipline applied while everybody is distracted.
Baseline the new environment before staff arrive
Capture what good looks like: firewall rules, wireless configuration, the address plan, admin accounts and the device list. Check what you have actually built against the NCSC device security guidance, not against what you intended to build. Stopping at the moment everything switches on leaves the configuration undocumented exactly when it is easiest to record.
Move weekend: the runbook, hour by hour
By the Friday, planning is finished and the only useful artefact is a runbook: a written, timed sequence with names against each step and a defined point for turning back. This is where a good office move IT checklist stops being a list and becomes a script.
Freeze changes and capture a known-good state
Two weeks out, stop all non-essential change. No new applications, no firmware updates, no supplier-initiated migrations. Take configuration backups of every switch, firewall and access point, and photograph the existing rack and patching. When something behaves oddly in the new building, the first question is what changed — and the answer needs to be nothing except the address.
The cutover sequence that works
Order matters more than speed. Bring up the new site’s circuit and firewall first, and prove it from the internet. Then core switching and wireless. Then servers, if any remain. Then printers and peripherals. Then a pilot group of five real users doing real work, not a ping test. Only then move everybody else. Each stage gets a named verifier on the office move IT checklist who confirms it before the next begins.
Who is on site and who is on call
Name the people, publish the numbers and confirm supplier escalation paths in advance. A circuit provider’s out-of-hours process is not the same as their business-hours one, and you want the reference number for the working order in hand before Saturday morning, not in a queue at nine on Monday. One person coordinates the office move IT checklist on the day and does not also carry a screwdriver.
The rollback decision
Agree in advance what triggers a rollback, who calls it, and by what time on the clock. If the circuit is not live by Saturday noon, the plan becomes the fallback: staff work from home on Monday, the old site stays live, the failover router carries the office. That decision is far easier made in a planning meeting than at midnight with a van waiting outside.
Office move IT checklist tasks for the first week in the new building
The move is not finished when the last box arrives. The first week decides whether staff remember the relocation as smooth or as the fortnight nothing worked, so the office move IT checklist should carry week-one tasks explicitly rather than trailing off at the door.
Run a visible triage desk on day one
Put somebody physically visible in the office on Monday with a laptop and a list. Most day-one problems are small — a monitor cable, a printer queue, a wireless password, a scan destination — and they take minutes in person against hours through a ticket queue. Visible support also stops the mood turning, which matters more than any individual fix, and it is the cheapest line on the entire office move IT checklist.
Keep a snagging list and actually close it
Log every issue in one place with an owner and a target date, including the trivial ones. Review it daily for the first week and weekly for the next month. Items that never reach a list never get fixed; they become the things people work around permanently, and eighteen months later nobody remembers a proper solution existed.
Update everything that carries your address
Website, Google Business Profile, email signatures, invoices, letterheads, courier accounts, insurers, banks, domain registrar, certificate contacts and every supplier portal. This is the most tedious item on any office move IT checklist and the one most visible to customers when it is missed. Assign it to one person with a written list and a completion date.
Review what the move revealed
A relocation surfaces every undocumented dependency, every unlicensed application and every system nobody owns. Capture those findings in the fortnight afterwards while the detail is fresh, and feed them into next year’s plan. Firms that treat a move as an input to strategic IT planning get a second return from money already spent.
Costs, suppliers and what to hand your provider
Budget technology separately from the fit-out. The cost side of an office move IT checklist is routinely underestimated, because the visible items — desks, paint, the kitchen — are quoted early and neatly, while the technology arrives as a series of separate invoices from four suppliers over three months.
Indicative UK costs to plan around
For a fifty-person office, expect roughly £3,000 to £8,000 for structured cabling depending on outlet count and building difficulty, £150 to £600 a month for connectivity depending on access type, £2,000 to £6,000 for network hardware, £1,000 to £3,000 per meeting room, and a project fee covering planning and the weekend itself. Excess construction charges for fibre are the wildcard and can exceed everything else combined. Price each line of the office move IT checklist separately, so nothing hides inside a single project figure.
What to ask a provider before you appoint them
Ask who writes the runbook, who is on site over the weekend, what the escalation path is at two in the morning, and what happens if the circuit is late. Ask for a reference from a move of similar size. Ask them to read your office move IT checklist and say what is missing. A provider quoting a relocation as a day rate without asking about circuits, cabling or porting has not understood the job.
Cover the weeks either side, not just the weekend
Support demand spikes for a fortnight after a move and stays elevated for a month. Agree in advance whether that is absorbed, billed or capped, because an unexpected invoice in week three sours an otherwise successful relocation. Check what your support plans actually include for project work, which is frequently excluded from standard cover.
Chester and North West specifics
Local building stock matters more than people expect. Converted period buildings, listed frontages and shared serviced floors all constrain cabling routes, riser access and where a comms room can sit. Businesses arranging IT support in Chester and across the North West should confirm fibre availability at postcode level early, because two units on the same street can carry very different lead times.
The office move IT checklist in one page
Twelve weeks out: order the circuit, survey the building. Ten: agree cabling and comms room works. Eight: audit devices, confirm supplier notice periods. Six: start number porting, book the weekend. Four: write the runbook, name the owners. Two: freeze changes, take configuration backups. One: pilot the new site with real users. Move weekend: cut over in sequence against an agreed rollback time. Week one: triage desk, snagging list, address updates.
Final thoughts: treat the move as a deadline, not an event
The businesses that relocate well are rarely the ones with the biggest budget. They are the ones that started twelve weeks out, named an owner, wrote things down and refused to compress the items that genuinely cannot be compressed. An office move IT checklist is only useful if it exists early enough to change decisions — about the building, the circuit, the contract dates and the sequence.
If you take three things from this guide, take these: order the circuit before you sign the lease, overlap the old line by a month, and write a runbook with a rollback time on it. Everything else on the office move IT checklist is recoverable in the following week. Those three are not, and they are the ones that decide whether Monday morning in the new building feels like progress or like a very expensive mistake.