The Hidden Costs of an Office Move: A UK Business Guide to Budgeting for IT Relocation in 2026

Almost every office move IT budget we see arrives at the same shape: a removals quote, a furniture allowance, a signage line, a contingency of ten per cent, and a single row labelled “IT” carrying a number somebody sense-checked against the last move they did. That row is where UK relocation budgets break. Not because the number is small, but because it was built from the visible half of the work — unplugging computers in one building and plugging them in at another — while the costs that actually consume the money sit in lease overlaps, cabling contracts, circuit lead times, equipment that does not survive the journey, and the hours nobody could work while a system was down.

This guide takes the hidden cost categories first, in the order they tend to appear on the final invoice rather than the order they appear in a project plan. It then sets out a budgeting framework you can build from your own numbers — per desk, per circuit, per hour of downtime — and finishes with a cost-avoidance checklist and the mistakes that most reliably turn a controlled relocation into an expensive one. The figures throughout are UK ranges for 2026, sized around the 40 to 80 seat moves that make up most of the market, and every one of them is the kind of number you can put in front of a finance director and defend line by line.

What an IT relocation budget actually covers — and where the standard quote stops

An IT relocation budget is not the cost of moving computers. It is the cost of standing up a working technical environment in a building that does not currently have one, while continuing to operate the business out of a building you are leaving, and then closing the first building down in a way that satisfies your lease, your regulator and your insurer. Three parallel workstreams, three separate cost bases, and only the middle one — the physical relocation of hardware — is what most removals-led quotes actually price.

The quote you receive from an office relocation firm typically covers crates, packing materials, transport, labour on the day, and often a general IT technician to disconnect and reconnect desk equipment. It is a genuine service and it is usually priced fairly for what it is. What it does not include, and does not claim to include, is the new site’s structured cabling, the comms room build, the data circuits, the telephony migration, the wireless design, the access control integration, the network hardware that has to be specified and bought in advance, the migration of anything still running on-premises, the professional time to plan and test the cutover, the out-of-hours premium for doing the work outside business days, or the decommissioning obligations at the site you are leaving. Each of those is a cost. Several of them are contractual commitments made months before move day, which means they cannot be trimmed when the budget gets tight.

The second thing the standard quote does not price is time. An office relocation has a hard, externally imposed deadline — the lease end date at the outgoing property — and one workstream on the critical path that no amount of money reliably accelerates: connectivity delivery. When that workstream slips, the organisation absorbs the slip somewhere, and the two places it lands are dual-running costs at both properties or downtime at the new one. Both are expensive, neither appears in a removals quote, and the decision about which one you pay is usually made too late to be a decision at all.

The third omission is the one that surprises people most: the outgoing building. Ceasing a leased line before its term expires can trigger the remaining rentals as an early termination charge. Removing cabling and making good the demise can be a reinstatement obligation under the lease. Disposing of end-of-life hardware carries WEEE duties and, if that hardware ever held personal data, an evidenced sanitisation trail. None of this is optional, all of it is invoiced after you have moved, and by then the project budget is usually closed.

The numbers that set the scale of an office move IT budget

Before breaking the spend into categories, it helps to anchor on four figures that shape everything downstream. They are median UK values for professional and financial services moves in the 40 to 80 seat band during 2025 and 2026, and they vary with building age, floorplate, and how much of the estate is already in cloud services.

The per-desk figure is the one to argue with, because it is the one that scales. At £1,250 a desk, a 60-seat move carries roughly £75,000 of IT relocation cost before anyone buys a single new laptop. That number lands badly in a first budget meeting, and the instinctive response is to challenge it. The challenge is worth having, because the figure moves substantially with three variables: whether the new demise is a fitted Category B space or a shell requiring cabling and a comms room from scratch, whether an existing circuit can be transferred or a new one must be ordered, and whether any workloads still run on physical servers at the current site. A fully cloud-hosted business moving into a fitted floor with a live circuit can land closer to £500 a desk. A firm with an on-premises file server, an analogue phone system and a shell unit will exceed £2,000.

The multiplier in the third card is the number that matters most for budgeting discipline. A ratio of 2.4 does not mean the original estimate was incompetent; it means the original estimate priced a different scope. It priced the move. The final invoice priced the move plus the new site build plus the transition plus the old site exit. Understanding that gap is the entire purpose of the categories that follow.

Removals-led versus IT-led: two ways to run the same relocation

The structural decision that determines whether the hidden costs surface early or late is who owns the programme plan. In a removals-led move, the relocation firm sets the schedule from the lease dates backwards and IT is a workstream inside it, usually engaged once the space is chosen. In an IT-led move, the connectivity and cabling lead times set the schedule and everything else is planned around them. The cost difference between the two is rarely visible in the quotes; it shows up in dual-running, in expedited charges, and in downtime.

The point of the comparison is not that one approach is professional and the other is careless. Removals-led programmes are the default because property decisions are commercial decisions, and they are made by people whose deadlines are legal and financial rather than technical. The problem is a sequencing one: by the time a lease is signed, the connectivity clock has already been running against a fixed occupation date, and every week of delay in ordering compresses the window in which the circuit can arrive without a bridge.

There is a second, subtler difference. An IT-led programme produces a specification early enough to be tendered. A removals-led one produces a requirement late enough that it has to be bought from whoever can deliver in the time remaining, which is a materially different purchasing position. Expedited cabling, short-notice out-of-hours engineering and emergency connectivity are all available in the UK market; they are simply bought at a premium of roughly 25 to 60 per cent over the same work planned properly.

Where hidden IT relocation costs actually land

If you ask finance teams after a completed move which lines overran, the answers cluster tightly. The chart below shows the proportion of UK office relocations in which each category either exceeded its original budget line materially or was absent from the budget entirely. It is worth reading as a risk register rather than a league table: the categories at the top are not the largest in absolute terms, they are the ones most reliably mispriced at the point the budget is signed off.

Connectivity tops the list for a structural reason: it is the only line in the budget whose price can be revised upward by a third party after you have committed to it. A carrier quotes a leased line on a desktop basis, then conducts a physical survey. If the survey finds that fibre must be blown through a duct that is blocked, that a new duct must be dug across a road, or that a wayleave is required from a neighbouring landowner, the carrier issues excess construction charges. These routinely run from £2,000 to £15,000 and, in genuinely awkward city-centre or business-park cases, into six figures. You can decline them and cancel, at which point you have lost weeks of lead time and are back at the start of a 60-day clock.

Cabling comes second because it is almost always specified by someone other than the person who has to run a network on it. A landlord’s Category A fit-out delivers a shell with power and a floor. The Category B works — the ones the tenant pays for — include the data outlets, the containment, the comms room, and the terminations. If IT is not in the room when that specification is written, you get the contractor’s default: two outlets per desk position on a floorplate laid out for the previous tenant, no allowance for wireless access points or ceiling-mounted devices, no separate containment for the cabinet, and no independent certification of the installed links.

Dual-running is third and is the most avoidable of the three. It is also the one finance directors dislike most, because it is a pure carrying cost with nothing to show for it: rent, service charge and business rates on two properties simultaneously, plus in many cases two sets of circuits. For a 60-seat office in a regional city at £25 per square foot on 6,000 square feet, an eight-week overlap is roughly £23,000 in rent alone before service charge and rates. Some overlap is deliberate and sensible — you want the new site working before the old one closes. Uncontrolled overlap, caused by a circuit that arrived late, is not a strategy.

IT relocation readiness — where UK businesses actually sit at the point of signing

The scoring below reflects the pattern we see when a business relocation IT planning exercise begins. It is grouped by the three columns of the budget: the new site, the transition, and the old site. Each row is scored by how frequently it is unresolved at lease signature, which is the last point at which resolving it is cheap.

The clustering of high-risk rows in the first and third cards is not accidental. Both sit outside the moving weekend, which is what people mentally picture when they think about an office move, and both involve counterparties — carriers, landlords, disposal firms — who work to their own timescales and their own contracts. The middle card is the one most organisations feel prepared for, and it is where the least money is usually lost.

The hidden cost ledger — a line-by-line office relocation cost estimate

The table below is the ledger we would build for a 60-seat move from a fitted office into an unfitted Category A floor in a UK regional city, with a mixed cloud estate and one remaining on-premises file and print server. Ranges are 2026 UK figures. The commitment column is as important as the cost column: it tells you when the money stops being a decision.

Two observations about this ledger are worth making explicitly. The first is that the line most people think of as “the IT move cost” — physically transporting equipment — is around five per cent of the total. The second is that more than half the total is committed before the move month begins, which is why the budget cannot be managed reactively. By the time a project manager is chasing crates, the expensive decisions were made a quarter earlier.

Note also that the ledger deliberately separates the recurring lines from the one-off ones. Circuits, failover and any new managed services are annual costs that persist long after the relocation project closes. A move is one of the few moments when a business re-tenders its connectivity from a genuinely open position, and treating those lines as project costs rather than as a three-year operating commitment is how organisations end up locked into the wrong contract at the wrong price. Our guide to business broadband failover and redundancy covers how to size the secondary circuit properly rather than defaulting to whatever the primary carrier bundles.

The twelve-week readiness benchmark

Twelve weeks before move day is the diagnostic point. It is late enough that every long-lead decision should already be made, and early enough that the consequences of a missed one can still be mitigated rather than simply absorbed. The gauge below is the median score we observe when a relocation is reviewed at that point, using a weighted model across the three budget columns.

Forty-one is a score for a project that will complete, but not cleanly. The weighting explains the number. Two components carry roughly half the model between them: whether the primary circuit has a confirmed delivery date from the carrier rather than an estimated one, and whether the cabling contractor has been appointed with a certified test schedule in the contract. At twelve weeks out, a well-run programme scores full marks on both. A typical one has an order acknowledgement with no committed date, and a cabling quote that has been accepted verbally.

The components that pull scores up are the ones organisations do naturally: the asset list exists, the desk plan is agreed, the removals firm is booked, and someone has a spreadsheet. The components that pull them down are the ones with an external dependency and a contractual consequence. That asymmetry is consistent enough to be useful — if you want to know where a relocation stands, do not ask how much planning has been done, ask which third parties have given a date in writing.

A score in the seventies at twelve weeks generally correlates with a move that costs what it was budgeted to cost. A score below thirty is a strong predictor of an unplanned dual-running period, because at that point the only remaining lever is time at the old building.

The IT relocation timeline — twenty-six weeks to move day

Every hidden cost in this article is a function of the schedule. The timeline below works backwards from occupation and shows where each commitment falls. It assumes a new circuit is required, which is the case for the large majority of moves; if you are fortunate enough to be moving into a building with an existing usable service, you can compress the first three phases considerably.

The phase people compress when the schedule tightens is the soak test in weeks six to three, because it is the only one that looks like waiting rather than working. It is also the phase whose removal most reliably converts a planned weekend of downtime into an unplanned week of degradation. If something has to give, give up a feature at the new site rather than the soak period.

How UK office moves perform against plan

The benchmarks below describe outcomes rather than intentions, drawn from completed relocations in the 40 to 80 seat band. They are useful mainly as a sanity check on your own assumptions: if your plan implicitly assumes performance at the top of these ranges on every line, it is not a plan, it is a hope.

The gap between the first row and the third is the whole story of this article. Three quarters of moves happen on the day they were meant to happen; fewer than a third happen for the money they were meant to cost. Relocations are not usually late. They are usually bought, at short notice, at the price short notice commands.

The two lowest rows deserve a moment. Rehearsing a restore before a physical move is cheap insurance on the one occasion when hardware is being subjected to genuine mechanical stress, and it is done by roughly a quarter of organisations — a pattern consistent with what we described in our guide to backup and restore testing. Resourcing post-move support is even rarer, despite the demand spike being entirely predictable in both timing and magnitude.

Connectivity is the critical path, and the critical path sets the budget

Across the relocations we review, connectivity is the workstream that determines the achievable move date more often than any other. Not the fit-out, not the furniture lead times, not the removals calendar — the circuit. That single fact drives more hidden cost than any other feature of an office move, because when the critical path slips the organisation buys its way out with either dual-running or a temporary service, and both are billed at premium rates for an unplanned duration.

The lead times are worth stating plainly, because the gap between what people assume and what carriers deliver is the source of most of the trouble. A fibre-to-the-premises service into a building that already has infrastructure can be delivered in 20 to 35 working days. A dedicated Ethernet leased line to a building with existing fibre typically runs 45 to 70 working days. A leased line requiring new civil works, a road crossing or a wayleave from a third-party landowner runs 90 to 160 working days, and the wayleave element is genuinely unbounded — it depends on a landowner who has no contractual relationship with you and no incentive to hurry. Business parks and converted period buildings are the two categories that most often produce the long tail.

Excess construction charges are the financial expression of the same problem. The carrier prices the order on a desktop basis, then surveys. Where the survey finds blocked or absent duct, a road crossing, a long internal run or a need to build into the building, the charge is passed through. There is no meaningful negotiation available at that point: you accept, you cancel, or you look for a different carrier and restart the clock. The mitigation is not commercial, it is temporal. Order early enough that a survey outcome you dislike still leaves you time to take a different route.

Three practical measures reduce this exposure materially. First, check connectivity at address level during site shortlisting, not after signature — carriers will do a pre-sales availability check on a specific postcode and building, and the difference between two shortlisted units is often stark. Second, order the primary circuit subject to contract as soon as the property decision is commercially probable, accepting a small cancellation exposure in exchange for weeks of schedule. Third, plan the bridge deliberately rather than as an emergency: a temporary bonded broadband or 5G fixed wireless service, ordered in advance and tested, costs a fraction of the same capability procured in a panic during move week, and it converts a potential outage into a period of reduced performance.

The final point on connectivity is that a move is the natural moment to fix resilience rather than replicate the old arrangement. If the outgoing building had a single circuit and the business tolerated it, the new building will inherit that risk along with everything else. Adding a diverse secondary path at the point of order costs a fraction of retrofitting it eighteen months later, when the ducts are sealed and the cabling contractor has demobilised.

How to cost IT downtime during an office move

Downtime is the largest hidden cost in most relocations and the only one that never appears on an invoice, which is precisely why it goes unbudgeted. If you want the rest of the budget to be argued on its merits, you need a defensible number for what an hour of unavailability costs, agreed with finance before the debate about the cabling quote begins. Without it, every protective measure — the soak period, the secondary circuit, the hypercare cover — looks like discretionary spend rather than insurance with a calculable premium.

The simplest model that survives scrutiny has three components. The first is loaded staff cost: annual salary multiplied by roughly 1.3 to cover employer national insurance, pension and overheads, divided by about 1,750 productive hours a year, multiplied by headcount affected and by a productivity impairment factor rather than by 100 per cent. Very few outages stop all work; most degrade it. A factor of 0.5 to 0.7 for a general office outage is defensible, and higher where the affected system is the one people work in all day.

The second component is deferred or lost revenue. For most professional services firms, a day of disruption defers billable work rather than destroying it, so the honest figure is the financing cost of the delay plus whatever genuinely cannot be recovered. For businesses that take orders, book appointments or answer inbound calls, the loss is real and immediate, and the phone system matters more than the network. For regulated firms, add the cost of any obligation you cannot meet on time.

The third component is recovery cost: the overtime, the supplier callout rates, the expedited shipping, and the two weeks of elevated support demand afterwards. This is the component people forget, and in a relocation it is unusually large because everything is happening at a weekend, at premium rates, with contractors on site.

Worked through for a 50-person professional services firm on an average loaded cost of £46,000, the arithmetic gives roughly £34 an hour per person, or £1,700 an hour across the firm at full impairment, and around £1,000 an hour at a realistic factor of 0.6. Over a seven-hour working day that is close to £7,000 before deferred revenue and recovery costs, which is where the £4,800 median in the stat cards above comes from once partial working and recovery are netted out. Whatever your own number is, calculate it once and use it consistently: it is the exchange rate that converts every schedule decision in the relocation into money.

The reason this matters for an office move specifically is that downtime here is largely elective. Unlike an outage caused by a failure, relocation downtime is the consequence of a set of scheduling decisions you control. Ordering the circuit four weeks earlier, keeping the soak period intact, or paying for a bridge service are all purchases of avoided downtime, and each can be evaluated against the hourly figure rather than argued about on instinct. The same logic underpins how response commitments are priced in a support contract, which we cover in our guide to IT support SLA response times.

A real relocation, costed both ways

A 54-person insurance broker relocating from a town-centre office in the Thames Valley to a business park eight miles away provides a clean illustration, because the first budget and the final position are both documented. The initial move budget carried £312,000 in total, of which £28,000 sat on a single line marked IT. That line had been built from the removals firm’s quote for equipment handling, a modest allowance for new switches, and a figure for “cabling” taken from the fit-out contractor’s outline.

The connectivity check was run after the lease was signed. The business park unit had no fibre in the building and the nearest carrier infrastructure sat on the far side of an access road, producing excess construction charges of £11,400 and a delivery estimate of 94 working days against a move date 61 working days away. The available options at that point were all expensive: accept a 33-working-day gap covered by a bonded 4G bridge at £2,900 for the period plus installation, or extend at the outgoing property. The firm did both in the end, holding a small footprint at the old office for six weeks at a cost of £16,800 in rent, rates and service charge while a bridge service carried the new site.

The cabling scope also grew. The contractor’s outline assumed one outlet per desk on the previous tenant’s layout; the broker’s desk plan had 54 positions plus 12 hot desks, wireless access points needed ceiling drops, and the comms room specified in the Category A drawings had no dedicated power circuit or cooling. Cabling, containment and comms room came in at £24,600 against the £9,000 outline. Separately, the audit found the core switch and firewall were both past end of software support, which made recommissioning them at a new site an unacceptable risk rather than a cost saving, adding £12,800.

Two analogue services were discovered in move week: the lift emergency line and the intruder alarm signalling path, both of which had been carried on the old site’s legacy lines and neither of which had an equivalent ordered at the new building. With the January 2027 PSTN switch-off already closing off new analogue provision, both had to be re-engineered onto digital alternatives at short notice, at a combined £3,900 including a temporary roaming SIM arrangement for the lift while the permanent solution was configured.

The final IT-attributable cost, counting the dual-running the connectivity delay caused, was just over £96,000 against the £28,000 line — a multiple of 3.4. Reconstructed afterwards, the counterfactual is instructive. Had the connectivity check been run during shortlisting, the same firm could have chosen either of two other shortlisted units with fibre already in the building, or ordered the circuit at the point of exclusivity and had it live with three weeks to spare. The avoidable elements were the £16,800 of dual-running, the £2,900 bridge, roughly £2,400 of expedited cabling premium, and the £3,900 of emergency analogue re-engineering: about £26,000, or slightly less than the entire original IT budget.

We did not overspend because anyone made a bad decision. We overspent because every decision was made four weeks after the point where it would have been cheap. The lease was signed before anyone asked whether the building had fibre, and everything after that was us paying to catch up with our own timetable.

The remaining £70,000 was not waste. Cabling a new floorplate properly, replacing unsupported network hardware and building a comms room are real costs of occupying a new building, and they would have appeared in any honest office relocation cost estimate written at the outset. The lesson of the case is not that the move was expensive; it is that the budget described the wrong scope, and the difference between a £70,000 truth and a £28,000 assumption was discovered in the most expensive possible way — incrementally, under time pressure, after commitment.

Telephony, analogue services and the 2026 timing problem

Any office move planned in late 2026 carries a constraint that moves before it did not. The PSTN switch-off completes at the end of January 2027, and the stop-sell of new analogue lines has been in force across the UK for some time. In practical terms, an organisation relocating now cannot assume that a service which worked on a copper line at the old building can be recreated the same way at the new one. Everything that used to sit quietly on an analogue pair has to be identified, re-engineered and paid for, and it has to happen before move day rather than after it.

The list of services that hide on analogue lines is longer than most people expect and almost never lives in the IT asset register, because it was installed by a lift company, an alarm firm or a facilities contractor. Lift emergency telephones are the most commonly missed and the most consequential, because a lift without a working emergency line should not be in service. Fire alarm signalling and intruder alarm signalling paths are next, both usually contracted to a monitoring provider with its own requirements. Then come door entry panels, gate intercoms, franking machines, card payment terminals, fax lines still used by insurers or the NHS, out-of-hours answering arrangements, and the modem on an ageing building management system.

Each of these has a digital replacement path — a GSM or roaming SIM unit, an IP-based signalling path, a SIP adapter, or a redesigned service — and each replacement path has a lead time, a supplier, and in several cases a compliance dependency on the monitoring contract or the insurer. Discovered at twelve weeks out, these are routine items costing a few hundred pounds each. Discovered in move week, they are emergency procurements, they attract expedited installation charges, and one of them may stop you occupying the building.

The main telephone system carries its own timing risk in the form of number porting. Porting a range of direct dial numbers between providers is a coordinated process between carriers with defined notice periods, and it cannot be safely compressed into the move weekend as an afterthought. The failure mode is not that the numbers are lost; it is that inbound calls route to the wrong place for a period, which for any business with a phone-driven revenue line is straightforwardly expensive. Book the porting window early, keep the old service live in parallel until the port completes, and treat the parallel period as a planned cost rather than a mistake. Our PSTN switch-off and VoIP migration guide covers the porting mechanics and the digital replacement options for analogue services in more detail.

There is an opportunity in the constraint. A relocation forces a telephony decision that many organisations have been deferring, and it forces it at the one moment when the cost of change is lowest, because the physical environment is being rebuilt anyway. Moving to a cloud-hosted voice platform during a relocation avoids paying to install a legacy system into a building you have just cabled, and it removes the site dependency from the phone system altogether — which, the next time the business moves, will make the telephony workstream close to free.

The twelve-point IT relocation cost-avoidance checklist

This is the sequence that removes the largest share of avoidable cost from a UK office move. It is ordered by when each item must happen, not by importance, because in a relocation those are almost the same thing. Items one to four are the ones that pay for themselves several times over; they are also the four most often skipped, because they fall before the point at which most organisations consider the project to have started.

1. Run an address-level connectivity check on every shortlisted building before heads of terms. Ask each carrier for availability, indicative lead time and known infrastructure at that specific postcode and unit. Record the answers in the property comparison alongside rent and rates, because a twelve-week delivery difference is a real financial difference.
2. Order the primary circuit subject to contract as soon as the property decision is commercially probable. Order the secondary circuit at the same time, from a different carrier and ideally on a diverse physical route. Insist that the carrier survey is scheduled rather than pending.
3. Read the outgoing site’s contracts before serving anything. Check the notice period and remaining term on every circuit, the lease reinstatement obligation for cabling and comms room alterations, and the termination terms on alarm, CCTV and access control agreements. Early cease charges on a leased line are commonly the full remaining rentals.
4. Build the budget in three columns — new site, transition, old site — with a commitment date against every line. Anything committing before lease signature goes to the top and gets decided first.
5. Write your own cabling specification and tender it. Specify outlet count per desk position against the actual desk plan, Cat6A or better, containment routes, ceiling positions for wireless access points, comms room provision, and independent certification of every link as a contractual deliverable.
6. Agree the comms room properly with the landlord: location, dedicated power circuit, cooling under load, physical security, and the licence to alter covering tenant works. Get it in writing before the fit-out programme fixes the layout around it.
7. Audit every device against warranty and end-of-support dates and decide what moves, what is replaced and what is retired. Anything past end of software support should not be recommissioned at a new site; the saving is illusory and the exposure is real.
8. Survey the old building for analogue services — lifts, fire and intruder signalling, door entry, payment terminals, building management. Assign each an owner, a digital replacement path and a lead time, and check the monitoring contract and insurer requirements for each.
9. Calculate your cost per hour of downtime and get finance to agree it. Use it to evaluate every schedule decision, and put it in the paper that justifies the soak period, the secondary circuit and the bridge service.
10. Protect a soak period of at least two weeks between circuit handover and move weekend, with the network built and under synthetic load. Defer a feature at the new site before you defer this.
11. Verify backups and rehearse a restore of anything being physically transported, and confirm the recovery path does not depend on a system that will itself be in a van. Document the rollback point for each cutover step and name the person who can call it.
12. Resource the fortnight after the move. Ticket volumes run at two to four times baseline. Plan the cover, brief the business on what to expect, and only decommission the old site once the new one is demonstrably stable.

The mistakes that make an office move expensive

Every item below is common, and none of them is caused by carelessness. They are caused by the ordinary sequencing of a property transaction, in which the commercial decisions are made by one group of people and the technical consequences are absorbed by another several weeks later.

• Signing the lease before checking connectivity. The single most expensive mistake available in a relocation, because it removes every cheap option at once. Once the building is fixed, the circuit lead time is fixed, and the only remaining levers are dual-running and bridging — both of which cost money and neither of which improves anything.
• Treating the fit-out contractor’s cabling allowance as a specification. An outline allowance is a placeholder for pricing, not a design. It rarely reflects your desk plan, almost never includes ceiling drops for wireless, and typically omits independent certification, which is the only evidence you will ever have that the installed links actually perform.
• Budgeting IT relocation as a single line. One number cannot be managed, challenged or tracked. Thirty line items with commitment dates can be. The single line is also what allows the old-site and dual-running costs to be classified as property costs, which is how they escape the review that would have prevented them.
• Assuming existing hardware will survive the move. Switches, servers, uninterruptible power supplies and wall-mounted access points that have run continuously for years are subjected to genuine mechanical stress in transit. Ageing UPS batteries in particular frequently fail to come back up, and a device already past end of software support should be retired rather than recommissioned.
• Discovering analogue dependencies in move week. Lift lines, alarm signalling and door entry are outside the IT asset register and inside the critical path. With new analogue provision no longer available ahead of the January 2027 switch-off, late discovery means emergency engineering at emergency prices.
• Cutting the soak period to hold the date. The soak period looks like slack and is actually the test. Removing it does not save two weeks; it moves the fault-finding into the working week after the move, when it is being done by people under pressure while users are trying to work.
• Ceasing old-site services on the wrong date. Cease too early and you lose your fallback. Cease too late, or outside the contractual notice period, and you pay the remaining term. Both errors are avoidable by reading the contracts at week 26 rather than week 2.
• Closing the project on move day. The fortnight afterwards contains a predictable support spike, the old-site decommissioning, the disposal evidence, the asset register reconciliation and the address updates at Companies House, the ICO register and every supplier and certificate that references the site. Unresourced, these get done badly or not at all, and the ones with a compliance dimension are the ones that resurface later.

Building the budget: a framework you can defend

The framework that holds up under finance scrutiny has four steps, and it can be built in a couple of days once you have the property shortlist. It is deliberately arithmetic rather than judgemental, because a relocation budget is going to be challenged and the only defence that works is a visible calculation.

Step one: establish the per-desk baseline. Take the desk count at the new site, including hot desks and meeting positions, and multiply by a per-desk figure appropriate to the building type. For a fitted Category B space with a live usable circuit, £450 to £700 a desk covers the technical work. For a Category A shell requiring cabling, comms room and a new circuit, £1,100 to £1,600. For a shell plus an on-premises server estate plus a legacy phone system, £1,700 to £2,300. This is a sighting shot, not the budget, but it gives the board a number on day one that will not need to be tripled later.

Step two: replace the baseline with the ledger. Work through the fourteen lines in the table above, price each against your own estate, and attach a commitment date. Anything you cannot price yet gets a range and a date by which the range must close. The output is a spreadsheet with three columns of cost and one column of dates, and its most valuable property is that it shows the board which decisions are already urgent.

Step three: add the two variable exposures explicitly. Excess construction charges and dual-running are the only two lines that can move by five figures after commitment. Carry them as named contingency, sized on the specific building: a business park unit with no fibre in the ground carries a much larger exposure than a city-centre floor in a multi-tenanted building with three carriers already present. If the survey comes back clean, you release the contingency; you do not spend it elsewhere.

Step four: convert the schedule into money. Using your cost per hour of downtime and your weekly dual-running rate, price each of the main schedule decisions: ordering the circuit four weeks earlier, keeping or cutting the soak period, buying a bridge service, extending at the old building. This turns the arguments that would otherwise be settled by seniority into comparisons between numbers, and it is usually the point at which the technically correct answer becomes the obviously cheaper one as well.

One structural recommendation to accompany the framework: appoint a single owner for the whole IT relocation, with visibility of all three columns. The classic failure mode in a relocation is that connectivity belongs to IT, cabling belongs to the fit-out contractor, access control belongs to facilities, dual-running belongs to property, and disposal belongs to nobody. Each party manages its own line competently and the total is unmanaged. The costs in this article live overwhelmingly in the gaps between those owners, which is exactly where a business relocation IT planning exercise has to concentrate.

At a glance — IT office move budgeting essentials

If you take one number from the table, take the second row. The multiple is not a criticism of anyone’s estimating; it is a measurement of the gap between the scope people price and the scope they buy. Closing that gap is not difficult work, but almost all of it has to happen before the lease is signed.

How Cloudswitched supports IT office moves

Cloudswitched plans and delivers IT office moves for UK businesses, working across the three columns rather than one: the technical due diligence on shortlisted buildings, the connectivity and cabling procurement, the network and comms room build, the telephony and analogue service migration, the cutover itself, and the old-site decommissioning with the evidence trail that goes with it. Where a relocation is already underway, the most useful engagement is usually a review against the twelve-week readiness model in this article, because it identifies which of the expensive options are still open.

Frequently Asked Questions

How much should I budget for IT in an office move?

As a sighting figure, use £450 to £700 per desk for a fitted space with a usable circuit already in place, £1,100 to £1,600 per desk for a Category A shell that needs cabling, a comms room and a new circuit, and £1,700 to £2,300 per desk if you also have on-premises servers or a legacy phone system to deal with. These exclude any hardware refresh you would have done anyway. Replace the per-desk estimate with a proper line-item ledger as soon as you have a shortlist, because the range within each band is driven almost entirely by the specific building.

Why do IT relocation costs so often exceed the budget?

Because the original budget usually prices the physical move of equipment, which is around five per cent of the true total, while the final invoice covers three separate workstreams: building a working environment at the new site, running the transition, and exiting the old site. The other structural reason is timing. Most of the money is committed before move month, so by the time anyone is actively managing the project, the expensive decisions have already been made and the only remaining levers are dual-running and expedited purchasing.

How long does a new leased line take to install in the UK?

A dedicated Ethernet leased line into a building with existing fibre infrastructure typically takes 45 to 70 working days from order to service. Where new civil works, a road crossing or a wayleave from a third-party landowner are required, expect 90 to 160 working days, and treat the wayleave element as open-ended because it depends on a party with no contractual relationship to you. Fibre-to-the-premises services into an already-served building can be quicker, at 20 to 35 working days. Always order subject to contract as early as the property decision allows.

What are excess construction charges and can they be avoided?

They are the pass-through cost a carrier applies when the physical survey finds that delivering your circuit requires work beyond the standard build — new duct, a road crossing, a long internal run, or building entry works. They commonly range from £2,000 to £15,000 and can be far higher on difficult sites. They cannot be negotiated away once surveyed, but the exposure can be managed: check availability at address level before choosing the building, order early enough that an unwelcome survey result still leaves time to try another carrier, and carry named contingency against the specific site rather than a flat percentage.

Should I keep the old office running during the move?

A short, deliberate overlap is usually sound practice, because it gives you a fallback if something at the new site does not behave. The problem is unplanned overlap caused by a late circuit, which is a pure carrying cost with no benefit. Size the overlap on purpose, price it per week — rent, business rates, service charge and any circuits still live — and set the decision point at which you either release the old space or extend. For a 60-seat office that figure commonly falls between £1,500 and £5,600 a week.

What IT equipment usually fails to survive an office move?

Ageing uninterruptible power supplies are the most frequent casualty; batteries that have held a float charge for years often fail to come back up after being powered down and transported. Older spinning-disk servers and storage arrays are next, followed by network switches close to end of life and wall-mounted access points that were never designed to be removed. The practical rule is that anything past end of software support should be retired rather than recommissioned, because you are accepting both the mechanical risk and an unsupportable device at a site you have just built.

How do I calculate the cost of downtime during a relocation?

Use three components. First, loaded staff cost: salary multiplied by about 1.3, divided by roughly 1,750 productive hours a year, multiplied by the headcount affected and by a realistic impairment factor of 0.5 to 0.7 rather than 100 per cent. Second, deferred or lost revenue, which is small for firms whose work is merely delayed and large for those taking orders or inbound calls. Third, recovery cost: overtime, callout premiums and the elevated support demand afterwards. Agree the resulting hourly figure with finance and use it to evaluate every schedule decision in the move.

What does the PSTN switch-off mean for an office move in 2026?

New analogue lines are no longer available and the switch-off completes at the end of January 2027, so any service that ran on a copper pair at the old building needs a digital replacement designed and ordered before you occupy the new one. That covers lift emergency telephones, fire and intruder alarm signalling, door entry panels, payment terminals and building management modems. Each has a lead time and often a monitoring contract or insurer requirement attached. Survey for these at least twelve weeks out; discovering them in move week turns routine items into emergency procurements.

Who should own the IT relocation budget?

One person, with visibility of the new site, the transition and the old site together. The common failure is fragmentation: connectivity sits with IT, cabling with the fit-out contractor, access control with facilities, dual-running with property, and disposal with nobody. Each party manages its own line competently while the total goes unmanaged, and the costs described in this article live almost entirely in the gaps between those owners. A single owner with a three-column budget and dated commitments closes those gaps.

How far in advance should IT be involved in an office move?

During site shortlisting, before heads of terms are agreed. The two decisions that most influence total IT cost — which building you take and when you order connectivity — are both made at that stage, and both are irreversible afterwards. Involving IT at that point costs a few days of advisory input; involving IT after signature means the connectivity clock has already been running against a fixed occupation date. A twenty-six week runway is comfortable for a move requiring a new circuit; sixteen weeks is tight; under twelve weeks means planning for a bridge service from the outset.

What should be in a cabling specification for a new office?

Outlet count per desk position measured against your actual desk plan rather than the previous tenant’s layout, Cat6A or better, containment routes, ceiling positions and cabling for wireless access points, provision for any ceiling-mounted or wall-mounted devices such as cameras and door controllers, the comms room build with its cabinet, power distribution and cooling, and independent certification of every installed link supplied as a results file. Tender that specification rather than accepting the fit-out contractor’s outline allowance, which is a pricing placeholder and not a design.

What happens to the old office IT once we have moved?

Four things, all of which cost money and none of which should be improvised. Circuits and service contracts must be ceased at the contractual notice period or you pay the remaining term, which on a leased line can be the full outstanding rentals. Lease reinstatement may require cabling and comms room alterations to be removed and the demise made good. Retired equipment holding personal data needs evidenced sanitisation or certified destruction, retained as a record, and the disposal itself carries duties under the WEEE Regulations. Finally, the asset register needs reconciling to what actually arrived at the new site.

Can we avoid downtime entirely during an office move?

Losing no working days is realistic, and better than half of well-run moves achieve it; achieving literally zero interruption is not usually worth what it costs. The practical target is that all unavailability falls inside a planned weekend window, with a tested fallback if a step does not complete. The things that make that achievable are a circuit delivered and soak-tested weeks in advance, a sequenced runbook with a defined rollback point per step, telephony ported ahead of the move with the old service running in parallel, and enough support cover on the following Monday to absorb the demand spike.

Related reading

These guides cover the workstreams that most often sit on a relocation’s critical path — connectivity, telephony, continuity and support — in more depth than the summary above allows.

• The PSTN Switch-Off: A UK Business Guide to VoIP Migration in 2026
• Business Broadband Failover and Redundancy: A UK Guide
• IT Support SLA Response Times: What UK Businesses Should Specify
• Backup and Restore Testing: A UK Business Guide
• Azure Disaster Recovery and Failover Planning: A UK Guide