A hybrid office relocation is a different problem from the one most move checklists were written to solve. The traditional plan treats the building as the unit of concern: pack it on Friday, cable it on Saturday, test it on Sunday, and accept that nobody can work until it is done because nobody could get in anyway. That logic held when the office was where the work happened. It does not hold when forty per cent of your staff were never going to be in the building on Monday, are not affected by the boxes, and are entirely dependent on systems that are currently in the back of a van.
This guide covers the part the standard checklist misses. It starts with the continuity risks that exist only in hybrid moves — the on-premises dependencies that remote staff reach without knowing it, and the failures that are silent precisely because nobody in the building notices them. It then works through the principle that makes hybrid moves manageable, which is decoupling those dependencies before any furniture is touched; equipment logistics for staff who never visit the site and therefore cannot simply carry their laptop to the new desk; a communication plan that reaches four different audiences on four different schedules; desk ratios and cabling design for a building that will never hold everyone at once; and the sequencing that keeps remote worker continuity intact across the move weekend. The general mechanics of a low-downtime relocation are covered separately in our zero-downtime office relocation checklist; this is the hybrid layer on top.
Why hybrid changes the shape of the problem
In a fully office-based move, downtime and disruption are the same thing, and both are bounded by the weekend. Staff arrive Monday, some things do not work, the provider fixes them, and the incident is visible to everyone at once because everyone is in the same room complaining about it. That visibility is genuinely useful: problems get reported within minutes.
Hybrid breaks that alignment in three ways. First, the affected population is no longer co-located with the event. A remote worker who cannot reach the file server on Monday morning does not know whether it is the move, their broadband, or something they did. They raise a ticket if they are the sort of person who raises tickets, and otherwise they work around it and say nothing, which means the organisation loses productivity it never measures.
Second, the failure modes become silent. The classic example is hybrid identity: if the directory synchronisation server lives in the office being moved, cloud authentication continues working perfectly while password changes, new account provisioning and group membership updates quietly stop. Nobody notices on move weekend. Somebody notices eleven days later when a new starter has no mailbox and the person who would have investigated is still reconciling asset lists.
Third, the window is no longer a weekend. Hybrid organisations typically have staff working compressed hours, part-time patterns, some in other time zones, and a field or client-facing group whose Saturday is a working day. A Friday-evening-to-Sunday-evening outage window is a fiction in most hybrid businesses, and planning against it produces a move where the outage lands in the middle of somebody’s billable day.
The practical consequence is that the hybrid move plan has to identify, for every system, not just when it will be unavailable but which population depends on it and whether that population will notice. Systems only office staff use can tolerate a weekend outage. Systems remote staff depend on need to be unavailable for minutes or not at all — and the way to achieve that is almost never a faster van.
Before writing any plan, produce a two-column list: every system in the comms room, and who reaches it from outside the building. Most organisations discover two or three entries they had not considered — a licence server, an on-premises component of a cloud service, a scanning workflow, an authentication dependency. Each of those is a system that a purely building-focused plan would have treated as a weekend task and which actually determines whether a third of your workforce can work on Monday. The list takes an afternoon and it reorders the whole project.
Hybrid relocation in UK businesses — the numbers
The figures below reflect what we typically see across UK office relocations for organisations of 30 to 300 staff operating hybrid working patterns. They describe moves planned competently against a traditional checklist, rather than badly managed ones.
The first figure is the one that should reframe the plan. If forty-three per cent of the workforce is remote on Monday, then the move has two distinct success criteria rather than one, and the remote criterion is the harder of the two because it cannot be fixed by walking to somebody’s desk. It also means that a move judged successful by everyone in the building may have been invisible chaos for a substantial minority.
The second figure is the most common cause of a move going badly wrong, and it has nothing to do with hybrid working — it simply becomes more damaging in a hybrid context, because a site without its primary circuit cannot host the systems remote workers need. Circuit lead times are measured from order to delivery and routinely extend when a wayleave is required from a landlord or a neighbouring freeholder, or when the route needs civils work. Ordering at heads of terms rather than at lease completion is the single highest-value scheduling decision in the project.
The fourth figure has a technical consequence people miss. A building designed for 0.65 desks per head is not simply a smaller version of the old one: it needs a booking system, standardised docking at every position, denser wireless coverage because people move around, and more meeting spaces equipped for hybrid calls rather than fewer. Cabling and access point design should follow expected peak occupancy and movement patterns, not headcount, and getting that wrong is expensive to correct after the ceiling is closed.
Traditional move plan against a hybrid-aware one
The difference is less about effort than about what the plan treats as the unit of risk. The comparison below sets out how the two approaches diverge on the decisions that matter for staff outside the building.
Traditional plan
The building is the unit of concern
Hybrid-aware plan
Populations and dependencies are the unit
The third row is where the real work sits, and it is the row that determines whether the rest of the plan is achievable. If the file server, the directory synchronisation host, the licence server and the telephony gateway are all still physical machines in the old comms room on the Friday, then no amount of communication planning changes the fact that remote staff lose those services for as long as the hardware is in transit and being recommissioned. Decoupling is not a nice-to-have in a hybrid move; it is the mechanism by which the move becomes survivable for people who are not there.
The last row is worth noting because it costs almost nothing and is almost always omitted. A remote test script — a short list of checks that named remote staff run at agreed times during and after the cutover, reporting results to one place — converts silent failures into reported ones within minutes. Six volunteers across different teams, connection types and locations will find more real problems in twenty minutes than the project team will find from inside the new building all weekend.
What remote staff lose when the comms room moves
The chart below shows how often each on-premises dependency is still physically located in the office being vacated, across UK hybrid organisations we assess before a relocation. Each one is a service that remote staff reach from outside the building, and therefore a service whose outage window is dictated by a van rather than by a maintenance plan.
The second row is the one that produces the most expensive surprises, because its failure is entirely invisible during the move. Directory synchronisation between an on-premises directory and a cloud tenant is a one-way flow running on a single server, and when that server is powered down, cloud sign-in continues working from the data already synchronised. Nothing breaks visibly. What stops is the propagation of changes: password resets made on-premises do not reach the cloud, new accounts do not appear, disabled accounts stay enabled. That last one is a security issue rather than an inconvenience, and a leaver processed during a two-week move window can retain cloud access throughout it.
The backup row deserves separate attention because it creates a risk window rather than an outage. Moving a backup appliance means a period with no backups being taken, and that period frequently coincides with the highest-risk activity the organisation performs all year: physically transporting every server it owns. The mitigation is straightforward — take a verified full backup to a cloud or off-site target before anything is unracked, and confirm it is restorable rather than merely present — and it interacts directly with how retention and verification are set up, which we cover in our guide to backup retention policy.
Telephony at thirty-one per cent is lower than it once was, but where an on-premises gateway still handles calls, a move affects remote staff immediately and conspicuously. Cloud-hosted telephony with no on-premises component is one of the few areas where the hybrid move problem has largely solved itself, provided the migration happened before the relocation rather than being bundled into it. Bundling a telephony migration into move weekend is a recurring and avoidable error, and the platform decision is worth making separately — something we work through in our guide to choosing a VoIP provider and hosted PBX.
Where hybrid moves fall down
The grid below groups the recurring weaknesses we find when reviewing a relocation plan written for a hybrid organisation. The badges reflect how much each gap threatens continuity for staff outside the building, rather than overall project risk.
The asset register item in the third card is worth more attention than its unglamorous description suggests. In an office-based organisation, the register can be reconstructed by walking the floor. In a hybrid one, a meaningful share of the estate is in people’s homes, and there is no floor to walk. Organisations routinely discover during a move that they cannot account for a double-digit number of laptops, docking stations and monitors — not because anything was stolen, but because kit was issued during a period of rapid change and never recorded. A move is the natural forcing function for fixing this, and the reconciliation is considerably easier before the move than during it.
The disposal row is rated lower for continuity and should not be read as low importance generally. Decommissioned servers, firewalls and end-user devices hold business and personal data, and disposing of them requires secure erasure or physical destruction with documentation to evidence it. Waste electrical equipment obligations apply to the hardware itself. Neither is difficult, but both are easy to leave until the old building has to be handed back, at which point the temptation is to let the clearance contractor take everything — which is how a domain controller ends up in a skip.
Lead times and costs that drive the schedule
The table below gives indicative UK figures for 2026, excluding VAT, for the items that most often determine when a hybrid move can actually happen. Lead times are from order placement and assume no unusual obstacles; costs vary substantially with site, building and distance to the nearest point of presence. The broader budget picture, including the items people forget, sits in our guide to the hidden costs of an office move.
| Item | Typical lead time | Indicative cost | Why it drives the hybrid schedule |
|---|---|---|---|
| Leased line at destination site | 45–90 working days, longer with civils | £280–650 per month plus install | Without it the new site cannot host anything remote staff depend on |
| Wayleave or landlord consent for the circuit | 4–16 weeks, largely outside your control | Legal fees, sometimes a landlord charge | Runs in parallel with the circuit order and frequently becomes the critical path |
| Temporary bonded 4G or 5G bridge | 5–10 working days | £150–450 per month | The insurance policy that lets the move proceed if the circuit slips |
| Structured cabling and wireless install | 2–5 weeks after site access | £140–260 per outlet installed | Must follow an occupancy-based design, not a headcount one |
| Courier collection and delivery to home-based staff | 3–10 working days per wave | £18–45 per shipment each way | The only route to refreshing or recovering kit from staff who never visit |
The first two rows together are the reason most relocation projects that fail, fail. A leased line order placed when the lease is signed, with a wayleave requirement discovered a month later, can comfortably exceed six months before the circuit is live — which is longer than most lease overlap periods. Ordering at heads of terms carries a modest risk that the deal does not complete and the order has to be cancelled, and that risk is almost always smaller than the cost of moving into a building with no primary connectivity. Ask the supplier to survey for wayleave requirements at the point of quotation rather than at the point of order.
The temporary bridge in the third row is the item most often cut from the budget and the one that most reliably saves a project. A bonded cellular service delivering a few hundred megabits is not a substitute for a leased line, but it is entirely adequate to run a new site for a few weeks while the permanent circuit completes, and it keeps remote staff connected to whatever has been relocated. At a few hundred pounds a month it is cheap relative to the alternative of delaying the move or operating from two buildings.
The last row is the line item that traditional move budgets omit entirely, because in an office-based move staff transport their own equipment. Hybrid organisations have to plan and fund physical logistics to and from residential addresses, including for staff who are leaving or joining during the move period, and including the reverse journeys needed to recover kit. Capacity planning for the new site’s bandwidth should account for the same shift in working patterns, which we cover in our guide to bandwidth planning for a growing UK business.
Decouple first, then move
The single principle that makes a hybrid move manageable is to reduce the number of things whose availability depends on a physical location before changing the physical location. Every dependency removed from the old comms room converts a continuity risk into a furniture problem, and furniture problems do not affect people working from home.
Move what you can to cloud services, well before move day
File shares, identity synchronisation, application servers and telephony gateways can in most cases be migrated to cloud equivalents or cloud-hosted virtual machines as a separate project, completed and stabilised weeks before the relocation. This is more work than moving the hardware, and it is work the organisation was probably going to do eventually. Sequencing it ahead of the move rather than after it means the move itself becomes low-risk, and it means any problems with the migration are diagnosed in a normal week rather than during a weekend when everything else is also in flux.
Where migration is not viable, relocate early and separately
Some systems cannot move to cloud on the available timescale — a legacy application with a hardware dependency, a system whose vendor support requires a specific configuration, or something whose migration cost cannot be justified in the window. For these, move the hardware to the new site or to a colocation facility as a discrete exercise ahead of the main move, once the destination has connectivity. A server relocated on its own, with its own plan and rollback, is a fundamentally different risk from the same server moved alongside forty desks and a hundred monitors. The specifics of doing this well are covered in our guide to planning a server room relocation.
Accept a short overlap where you can afford it
If the lease terms allow any overlap between buildings, use it. Running both sites for two to four weeks lets systems be moved individually with the old site as a fallback, which is the cheapest form of insurance available in a relocation. Where there is no overlap, the temporary connectivity bridge and an early separate server move become correspondingly more important, because there is no fallback to return to.
Do not bundle upgrades into the move
The move is a tempting moment to replace the firewall, change the telephony provider, upgrade the wireless standard and refresh the laptop fleet, because the disruption is already priced in. Resist it for anything remote staff depend on. Bundling means that when something does not work on Monday, the cause could be the move, the new hardware, the new provider or the new configuration, and diagnosis becomes an exercise in elimination while people cannot work. Do the upgrades before or after, with clear water between them.
Hybrid move readiness — where most organisations sit
Combining the assessment areas gives an indication of how well a relocation plan protects staff who are not in the building. The gauge reflects a first review of a UK hybrid organisation of 30 to 300 staff that has a move date and a plan written against a conventional checklist.
A score in the high thirties has a consistent composition. The physical logistics usually score well, because removals firms and IT relocation providers are good at the building side and it is the part everybody thinks about. Destination site readiness scores moderately, with connectivity lead time the usual weak point. Continuity for remote staff scores badly, because a conventional plan does not contain the concept. Communication scores worst, because the default is a single all-staff email written for people who will be walking into a new reception.
The encouraging feature is how much of the gap closes through planning rather than spending. Identifying dependencies by audience is an afternoon. Nominating remote testers and writing a test script is an hour. Segmenting the communication plan costs nothing. Ordering the temporary connectivity bridge is a few hundred pounds a month. The expensive item — migrating on-premises systems to cloud before the move — is work most organisations have on their roadmap anyway, and the move is a legitimate reason to bring it forward rather than an additional cost created by it.
As always, the benchmark measures the presence of practices rather than the outcome. A twelve-person business whose entire estate is already cloud-based, whose staff all work from laptops, and whose move genuinely is a furniture exercise will score poorly here and has nothing to worry about. The score matters in proportion to how much still lives in the room being emptied.
The hybrid move sequence — six months to move day
The timeline below assumes a 30 to 300 person hybrid organisation with some on-premises estate and a lease overlap of a fortnight or less. If the estate is already fully cloud-based, phases three and four largely disappear and the whole project compresses to about ten weeks.
Two features of that sequence are worth drawing out. The first is that the heaviest technical work happens in months five to three, not on move weekend — which is the intended design. A hybrid move goes well in proportion to how little is left to go wrong on the weekend itself. The second is that move weekend appears as a single item because, if the earlier phases were done, it genuinely is one: furniture, desk kit, commissioning and testing.
The phase most often compressed is the stabilisation period in month three, and compressing it is a false economy. A migration completed the week before a relocation means that any latent problem surfaces during the move, at which point nobody can tell whether the cause is the migration or the move. Three weeks of normal operation between the two is what makes the eventual diagnosis possible.
Equipment logistics for staff who never visit
In an office-based move, equipment logistics means moving equipment between two buildings. In a hybrid organisation it also means moving equipment between a building and an indeterminate number of residential addresses, in both directions, for people whose working patterns you do not fully control. This is a distinct workstream and it needs an owner.
Start from an accurate register
Everything else depends on knowing who holds what. Most hybrid organisations have a register that was accurate at some point and has since drifted, particularly for monitors, docking stations, headsets and keyboards, which tend to be issued informally. Reconcile it before the move by asking staff to confirm what they hold, ideally through a short form rather than an email thread, and accept that a first pass will not be complete. A move is the best opportunity in years to fix this, because there is a legitimate reason to ask.
Plan the waves, not the day
Courier collection and delivery to residential addresses runs in waves over weeks, not on a single day, and each wave needs a delivery window, a recipient who will be at home, packaging that protects the kit, and a return path for anything being recovered. Build in slack: a proportion of shipments will need rescheduling because somebody is away, and chasing those is the bulk of the effort. Where staff do visit occasionally, a scheduled hand-over day at the old or new site is cheaper and faster than couriering to them, but it only works for people who can realistically attend.
Treat kit in transit as data in transit
Laptops and servers being moved contain business and personal data, and the move is the period when they are least well controlled. Confirm full-disk encryption is active on every device before it is shipped or transported, maintain a chain of custody for anything holding significant volumes of personal data, and use a carrier and service level appropriate to what is inside the box rather than the cheapest option. A device that goes missing in transit is a very different incident if it was encrypted and documented than if it was neither.
Handle joiners and leavers during the window
People will join and leave during a six-month project, and the normal processes for issuing and recovering equipment will be running against a moving target. Decide in advance who provisions kit for a new starter during the move period and from where, and make sure recovery from leavers does not stall because the person who normally handles it is packing boxes. This is also where the directory synchronisation risk noted earlier becomes concrete: a leaver whose account should have been disabled may not be, if the synchronisation host is offline.
Benchmarks — hybrid move practice against what we find
The figures below reflect how often each practice is in place across UK hybrid organisations at the point we first review a relocation plan. They describe planning maturity rather than outcomes, and they are all within the organisation’s own control.
Adoption of hybrid-aware relocation practices
The distance between the first row and the rest is the whole argument. Eighty-seven per cent plan the physical move properly, because that is what removals firms and relocation providers sell and what project sponsors ask about. Between twelve and thirty-five per cent do any of the things that specifically protect the people who will not be in the building. The gap is not a skills problem; it is that the conventional checklist does not prompt for them.
The two cheapest rows are the two lowest. Segmenting a communication plan means writing three or four versions of a message instead of one. Nominating remote testers and issuing a script means asking six people to run five checks at three agreed times. Together they cost perhaps a day of effort and they address the two failure modes — silent problems and uninformed staff — that define a bad hybrid move.
The number that should set the plan
If one figure had to define the scope of a hybrid move plan, it would be the proportion of staff who will not be in the building on the first working day after the cutover. It determines how much of the plan needs to be about continuity rather than logistics, and it is a number the organisation already has from its own occupancy or booking data.
Forty-three per cent is a large enough minority that a plan addressing only the other fifty-seven is not a plan with a gap in it — it is a plan covering little over half the workforce. It also means the conventional definition of a successful move, which is that the office works on Monday, can be fully satisfied while a substantial part of the organisation is unable to do its job.
The number is worth calculating specifically rather than estimated, because it varies enormously by organisation and by day. A business with a Tuesday-to-Thursday attendance pattern moving over a weekend has a very different Monday from one with core days mid-week. Where the figure is high, consider scheduling the cutover so the first working day afterwards is a low-attendance day — not to hide problems, but because the office population is easier to support in person and a quieter building gives the team room to work.
Where the figure is genuinely low, the traditional plan is largely adequate and this guide is mostly unnecessary. That is a legitimate outcome of doing the calculation, and it is better to establish it deliberately than to assume it. The organisations that get caught out are usually the ones whose working patterns changed substantially over several years without the relocation playbook being revisited.
The communication plan
Communication is the cheapest intervention available in a hybrid move and the one most often reduced to a single all-staff email. The email is written for somebody walking into a new reception: where the building is, where to park, which floor. It contains nothing for the person at home who needs to know whether the file share will be reachable on Monday and who to contact if it is not.
Write for four audiences, not one
Office-based staff need the building information. Home-based staff need to know which systems will be unavailable, when, and what to do instead. Field and client-facing staff need to know what to tell customers and how to reach support from outside. Contractors and third parties — the people who will discover that their access has stopped working — need advance notice and a route to report problems. These are four short messages rather than one long one, and writing them separately takes about an hour.
Publish a single source of truth
During cutover, staff need one place to look that is not email, because email may be among the things that is degraded and because a thread of updates is unreadable. A simple status page or pinned channel post, updated on a fixed schedule with a timestamp, resolves this. Update it even when there is nothing to report: to somebody at home, silence and failure are indistinguishable, and an update saying that commissioning is on track at midday prevents a dozen tickets.
Be specific about the support route
The normal way of raising a problem may be the thing that has moved. State explicitly, in advance, how to get help during the cutover window — a phone number, an email address that is definitely working, a channel that is being monitored — and who is covering it and when. A remote worker who cannot work and does not know how to report it will usually wait, and waiting is the most expensive response available.
Set expectations about what will not work
Honesty here buys goodwill and reduces load. If the line-of-business application will be unavailable from Friday 18:00 until Sunday 14:00, say so in those terms rather than describing a general disruption window. People plan around specifics and complain about vagueness, and a named restoration time that is met is worth more to confidence than an optimistic one that is missed.
What this looks like in practice
A 110-person insurance broker in Reading moved from a building it had occupied for fourteen years to a smaller office eight miles away, on a plan built around a conventional relocation checklist supplied by its removals contractor. Roughly half the staff worked a two-day-in-office pattern, and the claims team of nineteen was almost entirely home-based following a restructure two years earlier.
The plan was competent about the building. Cabling was installed, desks were allocated, the removals firm had a floor-by-floor schedule, and the comms room hardware was scheduled to move on the Saturday with commissioning on the Sunday. The circuit had been ordered at lease completion, which left twelve days of contingency against a 62-working-day delivery. Nobody had mapped which systems the claims team reached from home.
Three things went wrong, and only one of them was visible from inside the new building. The circuit slipped by nine working days because a wayleave was required from the freeholder of an adjoining property, discovered after the order was placed. With no temporary bridge arranged, the new site opened on a single business broadband connection intended for guest wireless. Office staff found it slow; the claims team, whose case management application had moved to a server now sitting behind that connection, found it unusable.
Second, the directory synchronisation server was powered down on the Saturday and, because it was not on the commissioning priority list, was not brought back until the following Wednesday. Cloud sign-in worked throughout, so nobody noticed. What did not work was password resets and account changes, which meant two new starters that week had no access and a leaver processed on the Monday retained cloud access until the Thursday.
Third, the claims team received the same all-staff email as everyone else. It explained the new address and parking arrangements. On the Monday, nineteen people discovered independently that their application was unreachable, assumed it was their own connection, and between them raised four tickets over two days. The operations manager later established that the team had lost most of two working days, which nobody had recorded because there was no mechanism to record it.
The remediation was not complicated but it was all reactive. A bonded cellular service was installed within a week at a higher price for a short contract. The synchronisation server was rebuilt as a cloud virtual machine, which had been on the roadmap for eighteen months. The leaver access was reviewed and documented as an incident.
The move was declared a success on the Monday afternoon because everyone in the building was working. It took a fortnight to understand that the part of the business that never comes into the building had effectively been offline. The checklist we used was perfectly good and simply did not have a section for people who were not there, and neither did the way we thought about it.
Two points generalise. The first is that both technical failures were consequences of a single omission — the dependency and audience map — which would have taken an afternoon to produce and would have put the case management server and the synchronisation host at the top of the priority list. The second is the wayleave: ordering at heads of terms rather than at completion would have absorbed a nine-day slip without anybody noticing, and the cost of doing so would have been nothing unless the deal had collapsed.
The 12-point hybrid office move checklist
Items one to four happen at the earliest possible point, months before the move. Items five to eight are the build and preparation. Items nine to twelve cover cutover and closing out the old site.
- Order the destination circuit at heads of terms, and ask for a wayleave survey at quotation. Lead times of 45 to 90 working days extend further when consent is needed, and this is the most common cause of a failed relocation.
- Arrange a temporary bonded cellular bridge as insurance. A few hundred pounds a month that lets the move proceed on schedule if the permanent circuit slips, and keeps remote staff connected to whatever has relocated.
- Map every comms room system against the populations that reach it. Distinguish office-only from remote-dependent. This one document reorders the whole project and takes an afternoon.
- Calculate what share of staff will not be in the building on the first working day. From your own occupancy or booking data. It sets how much of the plan should be about continuity rather than logistics.
- Decouple remote-dependent systems to cloud, as separate projects. File shares, identity synchronisation, application servers, telephony. Stabilise for at least three weeks before move day.
- Design cabling, wireless and power to peak occupancy, not headcount. Hybrid buildings run at roughly 0.65 desks per head with people moving around, standardised docking at every position, and more hybrid-equipped meeting space.
- Reconcile the asset register including kit held in homes. Ask staff to confirm what they hold via a form. A move is the best opportunity you will get to fix a register that has drifted.
- Plan courier waves for home-based staff in both directions. Delivery windows, packaging, return paths for recovered kit, and slack for reschedules. Confirm full-disk encryption before anything ships.
- Take a verified restorable backup before any kit is unracked. Prove the restore rather than confirming the job completed. The transit window is the period with the highest physical risk and often no backup running.
- Publish a segmented communication plan and a single source of truth. Four short messages for four audiences, a status page updated on a fixed schedule even when there is nothing to report, and an explicit support route.
- Nominate remote testers and issue a test script. Six people across different teams, locations and connection types, running agreed checks at agreed checkpoints, reporting to one place. Converts silent failures into reported ones.
- Close out the old site deliberately. Cabling removal where dilapidations require it, secure data destruction for decommissioned kit with documentation, and waste electrical disposal. Do not let the clearance contractor take unassessed hardware.
If only three items are ever completed, make them items one, three and eleven. Ordering connectivity early removes the failure mode that sinks whole projects. The dependency and audience map is what makes every other continuity decision possible and costs an afternoon. The remote test script is what tells you within minutes, rather than within a fortnight, that something a third of your workforce depends on is not working. Together they cost perhaps two days and a small monthly fee.
Common hybrid relocation mistakes
The errors below recur across hybrid moves. Almost all of them stem from applying a checklist written for a fully office-based organisation to one that is no longer fully office-based.
- Defining success as the office working on Monday. With roughly forty per cent of staff elsewhere, that test can pass while a substantial part of the business cannot work. Success needs two criteria, and the remote one is harder.
- Ordering connectivity at lease completion. Circuit lead times plus a possible wayleave routinely exceed the contingency in a move plan. Order at heads of terms and accept the small cancellation risk.
- Skipping the temporary connectivity bridge. It is the cheapest insurance in the project and the first thing cut from the budget. Without it, a circuit slip becomes a business continuity event rather than an inconvenience.
- Moving the directory synchronisation host with everything else. Its failure is silent: cloud sign-in keeps working while account changes, password resets and leaver disablement quietly stop, which is a security issue as well as an operational one.
- Transporting servers with no verified backup in hand. The move is the highest-risk physical handling the organisation does all year, and it is frequently also the window in which the backup appliance is in a van.
- Forgetting kit held in homes. Hybrid organisations cannot reconcile an asset register by walking the floor, and a double-digit shortfall discovered during the move is common and avoidable.
- Bundling upgrades into the move. Replacing the firewall, changing telephony provider and refreshing laptops at the same time makes Monday diagnosis an exercise in elimination while people cannot work.
- Sending one all-staff email. Written for somebody walking into reception, it tells the person at home nothing about which systems will be down, when, or how to get help.
Be careful how the productivity impact on remote staff is accounted for after the move. Because those losses are invisible and unrecorded, the organisation tends to conclude that the relocation went well and to reuse the same plan next time. If a team lost two days, capture it — not to assign blame, but because the post-move review is the only mechanism that will improve the playbook. A short survey asking remote staff specifically what did not work and for how long, sent a fortnight after the move, is the cheapest way to make the next relocation better and the one step almost nobody takes.
At a glance — hybrid office move summary
| Question | Short answer |
|---|---|
| What makes a hybrid move different? | A large share of staff are not co-located with the event, so failures are silent and the outage window is no longer a weekend |
| The governing principle | Decouple remote-dependent systems before moving anything physical. Every dependency removed becomes a furniture problem. |
| Staff typically not in the building on day one | About 43 per cent in a UK hybrid organisation |
| The most common project-killer | Circuit lead time — 45 to 90 working days, longer with a wayleave. Order at heads of terms. |
| Cheapest insurance available | A temporary bonded 4G or 5G bridge at roughly £150–450 per month |
| The silent failure to watch for | Directory synchronisation host offline — cloud sign-in works while account changes and leaver disablement stop |
| Highest-risk window | Hardware in transit with the backup appliance also in transit. Verify a restorable backup first. |
| Desk ratio in a new hybrid office | Around 0.65 desks per employee, so design cabling and wireless to occupancy and movement |
| Equipment logistics for home-based staff | Courier waves over weeks in both directions, roughly £18–45 per shipment each way |
| Communication plan | Four short messages for four audiences, plus a status page updated on a schedule even when nothing has changed |
| How to catch silent failures fast | Nominated remote testers running a short script at agreed checkpoints, reporting to one place |
| What not to do during the move | Bundle upgrades. Do firmware, telephony and fleet refreshes before or after, with clear water between. |
| Realistic timeline | About six months with on-premises estate; roughly ten weeks if already fully cloud-based |
| Closing out the old site | Dilapidations cabling removal, documented secure data destruction, and waste electrical disposal |
How Cloudswitched handles hybrid relocations
Cloudswitched plans and delivers IT office moves for UK organisations, and for hybrid businesses the work starts earlier than the removals date. That means the connectivity order and wayleave survey at heads of terms, the dependency and audience map that establishes which systems matter to staff outside the building, decoupling those systems to cloud as discrete projects ahead of the move, an occupancy-based design for cabling and wireless at the destination, equipment logistics for home-based staff in both directions, the segmented communication plan and status page, and remote testers running checks through the cutover. We also handle the unglamorous end: documented data destruction and disposal for whatever does not make the journey.
Move the building without moving the problem
We plan hybrid relocations around both populations — the people walking into the new office and the people who will never see it — so remote access holds through the cutover.
Talk to an IT Office Moves SpecialistFrequently Asked Questions
How is a hybrid office move different from a normal office move?
In a fully office-based move, disruption and downtime are the same thing and both are bounded by the weekend, because nobody can get into either building anyway. Hybrid breaks that in three ways. The affected population is no longer in the same room as the event, so problems go unreported. Failure modes become silent — the classic case being a directory synchronisation host powered down while cloud sign-in continues working perfectly. And the outage window is no longer a weekend, because hybrid organisations have staff on compressed hours, part-time patterns and other time zones. The plan therefore has to identify, per system, not just when it will be unavailable but which population depends on it.
What should we do first when planning a hybrid relocation?
Two things, both cheap and both early. Order the connectivity for the destination site at heads of terms rather than at lease completion, and ask the supplier to survey for wayleave requirements at quotation. Then produce a two-column map of every system in the comms room against the populations that reach it, distinguishing office-only from remote-dependent. The first removes the most common cause of relocation failure. The second takes an afternoon and reorders the entire project, because it tells you which systems need to be decoupled rather than carried.
How long does a new office circuit take in the UK?
Typically 45 to 90 working days from order for a leased line, and materially longer where a wayleave is needed from a landlord or an adjoining freeholder, or where the route requires civils work. That is the figure that should set your move date, not the other way round. Because the survey that reveals a wayleave requirement often happens after the order is placed, ask for it at quotation stage. And arrange a temporary bonded 4G or 5G service as a bridge regardless, at roughly £150 to £450 a month, so that a slip becomes an inconvenience rather than a continuity event.
Which systems most often break for remote workers during a move?
In order of how often we find them still physically in the building being vacated: on-premises file shares, the directory synchronisation or hybrid identity host, line-of-business application servers, the VPN concentrator or remote access gateway, the backup appliance, telephony gateways, and licence servers or internal certificate authorities. Each is something remote staff reach from outside the building without necessarily knowing it exists, which means a plan that treats them as weekend tasks has scheduled an outage for a population it has not considered.
Why is the directory synchronisation server such a problem?
Because its failure is invisible during the move. Synchronisation between an on-premises directory and a cloud tenant runs on a single server, and when that server is off, cloud sign-in continues working from data already synchronised. Nothing appears broken. What stops is the propagation of changes: password resets do not reach the cloud, new accounts do not appear, and disabled accounts stay enabled. That last one is a security issue, because a leaver processed during the move window can retain cloud access for as long as the host is down. Put it near the top of the commissioning priority list, or migrate it to a cloud virtual machine before the move.
Should we move our servers or migrate them to the cloud first?
Migrate first where it is viable, as a separate project completed and stabilised at least three weeks before the relocation. This is more work than moving hardware and it is work most organisations have on their roadmap anyway; sequencing it before the move converts continuity risks into furniture problems and means migration issues surface in a normal week. Where migration is not viable on the timescale, relocate the hardware early and separately, once the destination has connectivity, with the old site as a fallback. A server moved on its own plan is a different risk from the same server moved alongside forty desks.
How do we handle equipment for staff who never come into the office?
As a distinct workstream with its own owner. Start by reconciling the asset register, including kit held in homes, by asking staff to confirm what they hold through a short form rather than an email thread. Then plan courier collection and delivery in waves over weeks rather than on a single day, with delivery windows, protective packaging, return paths for recovered equipment, and slack for the proportion that will need rescheduling. Confirm full-disk encryption is active before anything ships, and use a carrier and service level appropriate to what is in the box rather than the cheapest option.
What should the communication plan cover?
Four audiences rather than one. Office-based staff need building information. Home-based staff need to know which systems will be unavailable, when, and what to do instead. Field and client-facing staff need to know what to tell customers and how to reach support from outside. Contractors and third parties need advance notice that their access may be affected. Alongside those, publish a single source of truth that is not email — a status page or pinned post, timestamped and updated on a fixed schedule even when there is nothing to report, because to somebody at home silence and failure look identical.
How do we find out quickly if something is broken for remote staff?
Nominate remote testers and give them a script. Six volunteers across different teams, locations and connection types, running five agreed checks at three agreed checkpoints during and after the cutover, reporting results to one place. It costs about an hour to set up and it will find more real problems in twenty minutes than the project team will find from inside the new building all weekend. Only about twelve per cent of organisations do this, which is why so many hybrid move problems are discovered a fortnight later rather than the same afternoon.
How many desks should a new hybrid office have?
UK hybrid offices commonly land around 0.65 desks per employee, against 1.0 in the building being vacated. The important consequence is technical rather than spatial: a building at that ratio is not a smaller version of the old one. It needs a desk booking system, standardised docking at every position, denser wireless coverage because people move around during the day, and proportionally more meeting space equipped for hybrid calls. Design cabling, access points and power to expected peak occupancy and movement patterns rather than to headcount, because correcting it after the ceiling is closed is expensive.
Should we upgrade equipment at the same time as the move?
Not for anything remote staff depend on. The move looks like a convenient moment to replace the firewall, change telephony provider, upgrade wireless and refresh laptops, because the disruption is already priced in. The problem is diagnosis: when something does not work on Monday, the cause could be the move, the new hardware, the new provider or the new configuration, and working through that takes time during which people cannot do their jobs. Do upgrades before or after the relocation with clear water between them, and keep the move itself as boring as possible.
What should happen to equipment left behind in the old office?
Deal with it deliberately rather than leaving it to the clearance contractor. Decommissioned servers, firewalls, network equipment and end-user devices hold business and personal data, so they need secure erasure or physical destruction with documentation to evidence what was destroyed and when. Waste electrical and electronic equipment obligations apply to the hardware itself. Check the lease for dilapidations requirements covering cabling removal, which is frequently overlooked and occasionally expensive. The failure mode to avoid is a domain controller going into a skip because the building had to be handed back on Friday.
Related reading
More guidance on planning, moving and running UK business IT:
A relocation that both halves of your workforce survive
Cloudswitched plans UK hybrid office moves from the connectivity order forward — dependency mapping, decoupling to cloud, equipment logistics for home-based staff, and remote testing through the cutover.
Talk to an IT Office Moves Specialist
CloudSwitched
London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.
