A office IT relocation is one of the highest-risk projects a UK business can run — and one of the few where the whole company notices the day it goes wrong. Moving desks and chairs is a logistics job; moving the network, the phones, the internet circuit and the servers that everyone depends on is an engineering job with a hard deadline and no room to slip. Get the sequencing right and staff walk into the new premises on Monday morning, log in, pick up the phone and carry on as if nothing happened. Get it wrong and you lose a week of productivity, a broken phone system greets your customers, and the finance team is still trying to reach the accounting server from the old building.
This guide is built around a single promise: a zero-downtime office move is achievable for almost any small or mid-sized UK business, but only if the IT workstream starts months before the removal van is booked. Below you will find the full IT infrastructure moving checklist — connectivity provisioning lead times, network cutover sequencing, hardware decommissioning and re-racking, telephony continuity and a day-by-day relocation timeline — written so an operations leader, an office manager or an internal IT lead can plan the move without a broken phone system or a fortnight of lost output. Read it once end to end, then use the checklist and timeline as your working plan.
What a zero-downtime office move actually means
“Zero downtime” does not mean nothing ever switches off. Servers get powered down, circuits get ceased, and cables get unplugged — that is unavoidable. What it means is that no business-critical service is unavailable during working hours when staff and customers need it. The trick is to move the things that can tolerate an outage during a planned window (usually a Friday evening to Sunday), and to keep the things that cannot tolerate an outage — inbound phone calls, email, line-of-business applications — running continuously by cutting them over in the right order.
In practice, a well-run office IT relocation separates the estate into three tiers. Tier one is anything customer-facing or revenue-generating: the main phone number, email, the website, card payments and any client portal. These must never go dark. Tier two is internal-but-essential: file shares, the accounting package, the CRM, printing and Wi-Fi. A short weekend outage here is acceptable if it is planned and communicated. Tier three is everything else: meeting-room AV, the office music system, the spare monitors in the store cupboard. These can follow at leisure.
The reason relocations fail is almost never the physical move. It is the lead-time items — the new internet circuit, the number porting, the firewall configuration — that were ordered too late. A leased line can take 30 to 90 working days to deliver in the UK because it often needs civil engineering works and a Cloudflare-style wayleave from the landlord. If you book the removals firm before you order the circuit, you have already lost.
Start the IT relocation plan the day the new lease is signed — not the day the move is announced. The single longest lead-time item, your primary connectivity circuit, needs ordering first because everything else (firewall, phones, cloud cutover) depends on the network being live and tested before move weekend.
Office IT relocation by the numbers — the UK 2026 reality
Before the plan, the context. These figures reflect what mid-market UK businesses typically encounter when they move premises in 2026, and they explain why connectivity and telephony dominate the risk register.
DIY move versus a managed IT relocation — how they compare
Plenty of businesses attempt the IT side of a move themselves, reasoning that they own the kit and know their own systems. That works for a five-person office with a broadband router and cloud-only apps. It rarely works once you have an on-premises server, a phone system, a rack of switches and a leased line, because the failure modes are unforgiving and the lead-time items are unfamiliar. The comparison below is deliberately blunt.
Self-managed move
Internal team, no specialist support
Managed IT relocation
Specialist partner runs the workstream
The decisive difference is not competence — internal teams are often extremely capable — it is parallel running. A managed relocation keeps the old site fully operational until the new site is proven, so there is always a working fallback. That is very hard to arrange if you are also doing your day job. If your current support is stretched, our guide to in-house versus outsourced IT support for UK SMEs is a useful companion read before you decide who owns the move.
Where office-move downtime actually comes from
When relocations go wrong, the post-mortem almost always points at the same handful of causes. Understanding the distribution lets you concentrate effort where it pays off. The chart below reflects the relative frequency of root causes we see cited in UK office-move retrospectives.
Notice that the top three causes are all planning failures, not technical ones. They are entirely preventable with lead time. The connectivity question in particular deserves its own decision early on — our leased line versus broadband guide walks through which circuit type suits which premises and uptime requirement, and the ordering timelines involved.
Relocation readiness scoring — where most UK businesses sit today
Before committing to a move date, score your own readiness honestly against the three domains below. Most businesses discover they are strong on the physical logistics and weak on the connectivity and telephony workstreams — which is exactly the wrong way round, because those are the long-lead, high-risk items.
A high-risk badge is not a criticism — it is a signpost. Every red item on this grid is something to close out in the first month of planning, while there is still time to change the move date if a circuit cannot be delivered in time. Before the move is also the moment to confirm you have a genuinely restorable backup: follow the 3-2-1 backup rule and test a restore, because a server can be dropped, a drive can fail in transit, and the move is the one moment when losing data is most likely and least forgivable.
Office IT relocation cost breakdown
Costs vary with headcount, circuit type and how much on-premises kit you still run, but the table below gives realistic 2026 UK planning figures for a typical 30–60 person office move. Treat these as budgeting anchors, not quotes — the connectivity line in particular swings widely depending on whether your new address is already served by fibre.
| Cost item | Typical range (ex VAT) | Notes |
|---|---|---|
| New leased line install & first year | £2,500 – £9,000 | Higher if civils / excess construction charges apply |
| Structured cabling (Cat6A, 40 points) | £3,500 – £7,500 | Depends on floor plan and containment |
| Firewall, switches & Wi-Fi refresh | £2,000 – £8,000 | Often the right moment to upgrade |
| VoIP porting & handset provisioning | £500 – £2,500 | Per-number port fees plus config time |
| Managed relocation project fee | £2,500 – £9,000 | Planning, weekend engineers, parallel run |
The number worth internalising is the cost of not spending on the managed workstream: a single lost working day for a 40-person firm runs to roughly £18,000 once you combine payroll, lost billable hours and the reputational cost of a dead phone line. Against that, a four-figure project fee to guarantee a clean weekend cutover is cheap insurance. If a network refresh is on the cards anyway, weigh an SD-WAN versus traditional WAN approach at the same time — moving premises is the natural moment to modernise the edge.
Relocation readiness gauge
Aggregate the three domains above into a single readiness score. A business sitting below 60 should not commit to a fixed move date until the connectivity and telephony gaps are closed. The gauge below shows the level at which a zero-downtime cutover becomes realistically achievable.
Reaching 72 or above means your long-lead items are ordered, your rollback is documented, and your telephony continuity is tested — the three things that separate a boring, uneventful weekend from a Monday-morning crisis.
The office move timeline — what a real zero-downtime relocation looks like
A zero-downtime office move is a twelve-week project for most SMEs, front-loaded with the connectivity order and back-loaded with the physical cutover. This is the sequence we run, compressed into the milestones that matter.
Cutover progress — how the workstreams stack up on move weekend
On the weekend itself, the different workstreams complete at different points. Tracking them as a live checklist keeps the move honest — nobody declares victory while a critical service is still amber. These are the completion states we aim for by Sunday afternoon.
Move-weekend completion by workstream
The two workstreams that must hit 100% before Monday are connectivity and firewall — everything else can be finished during hypercare. Telephony should be functionally live even if a handful of call-flow refinements trail into the following week; keeping call quality high on the new circuit is its own discipline, covered in our VoIP call quality troubleshooting guide.
How much of the estate is genuinely move-critical
Not everything needs the white-glove treatment. Sorting the estate by criticality is what makes a zero-downtime move affordable — you spend your engineering hours on the services that cannot go dark and let the rest follow. In a typical SME estate, the proportion that is truly tier-one and must be continuously available is smaller than people fear.
That two-thirds is where you can be pragmatic: power it down Friday, move it, bring it back Sunday. The critical third — inbound telephony, email, the primary line-of-business app, payment processing — is where the parallel-run discipline earns its keep. Cloud-hosted services help enormously here, because a mailbox in Microsoft 365 does not care where your office is; if an email migration is also on your roadmap, the Microsoft 365 email migration checklist pairs naturally with a move.
A real-world example — a 45-person move done right
A professional-services firm in Leeds outgrew its offices and took a larger floor eight streets away. On paper it was a short move; in reality the new building had no fibre to the comms room and the incumbent broadband would not have carried the firm’s cloud workloads or its VoIP traffic. Because the IT partner ordered a leased line the week the lease was signed — eleven weeks before the move — the circuit was delivered, tested and running live traffic a full fortnight before anyone touched a desk. Number porting was lodged with four weeks’ notice, and every handset was pre-provisioned so it only needed plugging into a labelled floor box.
The physical move happened over a single weekend. The old office kept its circuit live in parallel until the following Friday, so if anything had failed there was always a working fallback. Nothing did. Staff arrived Monday, plugged in, and the only visible change was the view out of the window.
“We’d braced the whole company for a bad week and it simply never came. The phones rang on Monday, email never blinked, and the finance team closed the month on schedule. The only thing anyone complained about was the coffee machine, which was nothing to do with IT.” — Operations Director, Leeds professional-services firm
The lesson is not that this firm was lucky. It is that the risky part of the move was finished weeks before the vans arrived. By the time the physical relocation happened, the network, the internet and the phones were already proven at the new address.
The zero-downtime office move checklist — the 12-point essentials
This is the working checklist. Run it in order; each item unlocks the next. Do not let the physical move date drive the plan — let the connectivity delivery date drive it, because that is the one thing you cannot compress.
- Order connectivity at lease signing. Primary circuit plus a diverse or 4G/5G backup path, and request the landlord wayleave the same day.
- Commission a site survey. Comms room, power, cooling, cable routes, rack space and floor-box positions at the new premises.
- Design the network. VLAN plan, IP scheme, firewall ruleset and Wi-Fi coverage before any hardware is bought.
- Install and test structured cabling. Cat6A to every desk, certified and labelled, with the comms room fitted out and signed off.
- Submit number porting. Lodge the port with at least four weeks’ notice and configure call failover to mobiles as a safety net.
- Pre-stage and lab-test the firewall and switches. Configure off-site, then it is a plug-in job on move weekend.
- Prove the new circuit early. Deliver it two weeks before the move, run real traffic, validate throughput and QoS.
- Take a full verified backup. Test a restore before anything is unplugged; do not assume the backup works.
- Photograph and label everything. Every cable, port and rack position, so re-racking is deterministic, not guesswork.
- Impose a change freeze. No new deployments or configuration changes in the final week before the move.
- Keep the old site live in parallel. Do not cease the old circuit until the new one has run clean for a week.
- Plan hypercare. Engineers on site at first login Monday, a snag list, and a named owner for every open issue.
Print this checklist and assign a named owner and a due date to every line. A relocation fails silently when everyone assumes someone else has ordered the circuit or lodged the port. Ownership, not enthusiasm, is what delivers a zero-downtime move.
Common office relocation mistakes to avoid
Every failed move we are asked to rescue shares a subset of the mistakes below. None of them are exotic; all of them are avoidable with lead time and a rollback plan.
- Booking the removals firm before ordering the circuit. The van is the easy part. The internet circuit is the long pole — order it first, and let its delivery date set the move date.
- Assuming the new building already has fibre. Many do not have it to the comms room. Always check availability at the exact address before you commit to a date.
- Leaving number porting until the week of the move. Ports take weeks and cannot be rushed. A late port means a dead main line on Monday.
- No parallel run. Ceasing the old circuit the day you move removes your only fallback. Keep both live for a week.
- Trusting an untested backup. The move is when hardware is most likely to be damaged. An unverified backup is not a backup.
- Ignoring QoS on the new circuit. A circuit that passes a speed test can still deliver poor call quality if voice traffic is not prioritised.
- Forgetting the address records. DNS, disaster-recovery runbooks, alarm and CCTV callouts, and supplier records all need updating.
- Treating security as an afterthought. A new firewall is a fresh ruleset — get the baseline right rather than copying old rules blindly.
The most expensive mistake is treating the move as a physical project with an IT afterthought, rather than an IT project with a physical component. If your plan starts with the furniture and ends with “and IT will sort the network out that weekend”, you do not yet have a plan — you have a hope. A new site is also the right moment to confirm your security baseline against Cyber Essentials.
At a glance — the zero-downtime office move summary
The whole guide, condensed to the facts worth keeping in front of you while you plan.
| Factor | What to know |
|---|---|
| Core promise | No business-critical service is down during working hours |
| Longest lead item | Leased line install — 30 to 90 working days |
| Start planning | The day the new lease is signed, not the day the move is announced |
| Number porting notice | At least 4 weeks; configure mobile failover as a safety net |
| Minimum IT lead time | 12 weeks for a safe zero-downtime cutover |
| Top failure cause | Connectivity ordered too late (88% of failed moves) |
| Move-critical estate | Only about a third needs continuous availability |
| Golden rule | Keep the old site live in parallel until the new one is proven |
| Cutover window | Friday evening to Sunday, with Monday hypercare on site |
| Cost of one lost day | ~£18,000 for a 40-person firm |
| Readiness threshold | Score 72+ before committing to a fixed move date |
| Backup discipline | Full verified restore before anything is unplugged |
Planning an office move? Get the IT workstream right from day one
Cloudswitched runs the whole IT relocation for UK businesses — connectivity, network, telephony and servers — so your team walks into the new premises and simply carries on.
Talk to an IT Office Move SpecialistFrequently Asked Questions
How far in advance should I start planning an office IT relocation?
Start the IT workstream the day the new lease is signed — realistically twelve weeks before the move for a zero-downtime cutover. The single longest lead-time item is the primary connectivity circuit, which can take 30 to 90 working days to deliver in the UK if the new address needs civil works or a landlord wayleave. Everything else — firewall, telephony, servers — depends on the network being live and tested first, so if you leave connectivity late the whole plan compresses into a window that cannot deliver a clean move.
Can a business really move office with zero downtime?
Yes, for almost any SME, provided the risky work is finished before the physical move. A zero-downtime office move means no business-critical service — inbound phones, email, line-of-business apps, payments — is unavailable during working hours. You achieve it by proving the new network and circuit weeks ahead, keeping the old site live in parallel as a fallback, and doing the physical cutover over a weekend. Some servers do power down, but never during the hours staff or customers need them.
How long does it take to move a business phone number to a new office?
Porting a UK business number typically needs two to four weeks’ notice, and it cannot be rushed once submitted. Lodge the port request around six weeks before the move and configure call failover to mobiles as a safety net. With modern VoIP, the number is not tied to the building at all, so the handsets simply need pre-provisioning and plugging into the new network — the port keeps the same public number ringing through the transition.
What is the biggest risk in an office IT relocation?
Ordering connectivity too late. It is cited in the overwhelming majority of failed moves because the leased line is the one item you cannot compress — you are dependent on the carrier’s build schedule and sometimes on street works. Book the removals van before the circuit and you have already put the move date at the mercy of an installation you do not control. Order the circuit first and let its delivery date set the move date.
Should we upgrade our IT during the move or move first and upgrade later?
A move is the natural moment to refresh network hardware, connectivity and Wi-Fi, because you are cabling and configuring a new site from scratch anyway. Upgrading the firewall, switches and circuit as part of the relocation avoids a second disruption later and lets you design for current needs rather than replicating old constraints. The exception is major application migrations — keep those on a separate change so you are not debugging two big changes at once on move weekend.
Do we need a backup circuit at the new office?
For any business that depends on cloud applications or VoIP, yes. A single circuit is a single point of failure, and an outage on your only line takes down phones and cloud apps together. A diverse second circuit or a 4G/5G failover gives you continuity if the primary drops, and it also provides cover during the move itself. The cost is modest against the price of a full-office outage, and it is far easier to install both circuits during the relocation than to retrofit resilience afterwards.
How do we protect our data during the physical move?
Take a full, verified backup before anything is unplugged and test a restore — do not assume the backup works. The move is the moment hardware is most likely to be dropped or damaged, so a proven, off-site restore point is essential. Follow a 3-2-1 approach: three copies, on two media types, with one off-site. Photograph and label every cable and rack position so re-racking is deterministic, and keep the old kit intact until the new site is confirmed healthy.
Who should own the IT relocation — internal IT or a specialist partner?
It depends on the estate. A small, cloud-only office can often self-manage. Once you have an on-premises server, a phone system, a leased line and a rack of switches, a specialist partner reduces risk substantially — mainly because they can keep the old site running in parallel while they build and prove the new one, which is very hard to do alongside a day job. The decision mirrors the wider in-house versus outsourced support question, and the two are often best answered together.
What happens on the actual move weekend?
Friday evening the servers are shut down cleanly, decommissioned and transported. Saturday they are re-racked, powered up, reconnected and tested against the pre-built network. Sunday is full application and telephony validation with a user-acceptance walk-through, so problems surface on Sunday afternoon rather than Monday morning. Engineers stay on site for first login Monday — the hypercare period — and the old circuit is kept live for a week as a fallback before being ceased.
How much does a managed office IT relocation cost in the UK?
For a 30–60 person office, budget roughly £2,500 to £9,000 for the managed project fee, on top of connectivity, cabling and any hardware refresh. That may look significant until you weigh it against the cost of downtime: a single lost working day for a 40-person firm is around £18,000 once you combine payroll, lost billing and the reputational hit of a dead phone line. A guaranteed clean weekend cutover is inexpensive insurance by comparison.
Related reading
Move premises without a broken phone system or a lost week
From connectivity lead times to weekend cutover and Monday hypercare, Cloudswitched delivers zero-downtime IT office moves for UK businesses — planned, tested and proven before the vans arrive.
Talk to an IT Office Move Specialist
CloudSwitched
London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.
