The Keys Arrive Before the Broadband Does: Running an Office Move as an IT Project

  • 4 days ago
  • 0

The lease is signed and the keys are handed over. Then someone discovers the previous tenant’s line is being ceased, the landlord has not approved new cabling, the phone numbers cannot move as quickly as the furniture, and the “ready to go” comms cupboard contains one ageing switch, an unlabelled patch panel and a fan that has not turned in years.

The move date was set by the property lawyers. Nobody set an IT date.

The move date is a property date, not an IT date

A building can be legally yours before it is operationally ready. The gap between “we have the keys” and “the business can trade from here” is filled by services, permissions, equipment and decisions, each with its own lead time.

Build the IT timeline backwards from the first working morning. Start with what staff must be able to do: access business systems, communicate with customers, print essential documents and complete any critical transactions. Then work back through the tests, installations, approvals and orders that make those tasks possible.

One named person must own the IT workstream and have authority to get decisions made. Without that owner, suppliers hear different instructions, issues wait for someone else to pick them up, and important details fall between the property, operations and technology teams. One accountable owner matters more than any single piece of equipment.

A strategic IT Consultancy can set the sequence, dependencies and decision points. The implementation may involve several suppliers, but the business needs one view of what must happen, by whom, and by when.

Survey the building before you commit, not after

A viewing is not a technical survey. Before committing to the premises, inspect the comms room or cupboard: is there space for the equipment you need, suitable power and cooling, a lock, and clarity about who can enter? In a shared building, check whether the cupboard or riser serves other tenants and how access is arranged.

Look closely at existing cabling and containment. A patch panel with no labels may still be usable, but first someone has to establish where its connections go. Check where external lines enter the building, what fixed connectivity is already installed and whether it is operational and suitable for your requirements. Test mobile signal inside the actual offices and stockroom, not just on the pavement outside.

Then check the lease and building arrangements. Does the landlord permit the cabling or building work you need? Will a wayleave, landlord consent or managing-agent approval be required? These processes can take time, particularly where a provider needs access through shared areas or third-party property. Find out early; the building’s connectivity plan should not depend on an approval nobody has requested.

A neglected comms cupboard with an ageing switch and unlabelled patch panel

Order connectivity and phone numbers first

Check what connectivity is actually available at the new address. Do not assume that the old provider, service or speed will simply follow you. A new connection may require surveys, landlord permissions or work inside the building; ordering it late does not make it arrive sooner.

Keep the old site live until the new one has been tested and proven. For a period, you may pay for two locations. That overlap is a planned transition cost, not waste: it gives you a route back if a critical service is not ready.

Plan the phone number move deliberately. Confirm who is authorised to request a port, and do not port numbers until the new voice service is working and tested. Agree a fallback route for the day of the change, so customers and staff can still reach the business if the port or service does not behave as expected.

For a business that depends on Cloud Solutions, the new building’s connection is not a utility in the background. It is the production line. Your Voice and Connectivity and Network Solutions should be planned around how people and systems need to work, not left until the desks are in place.

Decide what moves and what does not

A relocation is a sensible point to review equipment: it may be cheaper to retire a device than to move, reconnect and maintain it. But moving premises is usually a poor moment to run a major change programme as well. Combining the two can put the move date at the mercy of extra scope.

Keep “move decisions” separate from “improvement projects”. Decide what travels, what is retired and what is replaced like-for-like. Separately, agree which new systems or ways of working will be delivered as a later, governed project. This makes the move itself easier to test and keeps ambition from holding readiness hostage.

Any system with a fixed operational role needs an explicit plan. For on-site IBM i systems, that means a planned shutdown, planned power-down and documented restart sequence, not a shout across the room as the van arrives. A move can also be a useful moment to re-test Disaster Recovery assumptions for the new site. If a wider business-systems change is already being considered, a Dynamics 365 Jump Start may be relevant as a separate piece of planning, not something to slip into the relocation without a decision.

The physical move is where data goes missing

Before unplugging equipment, match it to the asset register and label it for its destination. Record what leaves, who is responsible for it and where it should arrive. Reconcile the equipment at the new site against the departure list. A device that cannot be accounted for is not an admin detail; it may contain business or personal information.

Treat equipment that will not travel as a decommissioning project, not as a skip decision. Old laptops, drives, multifunction printers and phones can retain client and staff data. The NCSC’s asset management guidance explains why knowing what assets you hold is fundamental to security. Its guidance on decommissioning assets covers planning, secure handling and keeping evidence that disposal has been completed. The ICO’s guidance on disposal and deletion also sets out the importance of secure disposal and appropriate records.

An unplugged network device beside a plain labelled cardboard box

The cutover is a change, not a weekend with a van

Write a runbook for the cutover: the order of work, who is responsible for each step, what must be tested and what happens if a test fails. Schedule disruptive work out of hours where practical. Identify who will be on site and who will be available by phone, and make sure staff know where to report problems.

Before anyone settles at a desk, test the services the business needs to operate. That may include logging in, accessing essential systems, sending and receiving email, making and receiving calls, printing, scanning and completing a representative business task. Agree what counts as a pass, who signs it off and what the fallback is if it fails.

A Monday morning is an expensive time to discover that a port was never labelled. Plan for a first-week surge in tickets and make Helpdesk Support part of the transition. Record recurring faults properly: several people reporting the same symptom may point to one underlying cause, not a collection of unrelated annoyances.

What reliably breaks after a move

The obvious systems may be ready while smaller dependencies are not. Printers and scanners can still point to the old address or network settings. Door access controllers and CCTV may be powered but not recording. Meeting-room equipment may need to be registered again. Changes to static IP addresses or DNS can quietly affect remote access and inbound mail, and the forwarding rules that sent enquiries to a particular inbox. Payment terminals may fail to reconnect, and a line-of-business application may still have the old address recorded.

Make a supplier list and notify every organisation holding a relevant contract. Some require a change of address in writing. Include providers for payments, security, building access, software and business applications, not only the internet and telephone supplier. Ask each one what needs updating, who can authorise it and when the change should take effect.

The bills that follow you

Services at the vacated premises can keep billing after staff have left. The planned overlap between sites is useful, but it should be reviewed deliberately rather than allowed to continue by inertia.

Use Technology Expense Management to reconcile what the business is paying for against what is in use at the new site. Identify which old services must remain active during transition, which can be cancelled, and who will confirm each closure. Check the contract’s notice terms and give notice accordingly; optimism is not a cancellation instruction.

A back-to-front plan: decisions and owners

Work backwards from the first working morning. The timings will vary by building and service, so assign owners and confirm supplier lead times rather than relying on a generic calendar.

  • Months out, executive sponsor and IT owner: confirm the move date, name one owner for IT, survey the site, check lease permissions and shared-building access, and start connectivity orders and landlord approvals.
  • Weeks out, IT owner and suppliers: confirm what moves or retires, arrange and test cabling and network equipment, agree the phone-number sequence, notify suppliers, and complete the asset and data-disposal plan.
  • Week of the move, technical lead and operations lead: confirm the runbook, staff communications, equipment labels, contacts and escalation route. Freeze avoidable changes and confirm the old site remains available for the agreed overlap.
  • First morning, site lead and service owners: run the agreed checks before normal work begins, record results and issues, and make the fallback decisions if a critical test fails.
  • First month, IT owner and finance or procurement owner: review recurring faults, confirm supplier changes and old-service cancellations, reconcile equipment, and check that the new site’s recovery assumptions and costs match the plan.

A newly cabled network cabinet with tidy patch leads in labelled ports

Readiness is a different date

A move exposes whether IT has been run as an estate with a strategy or as a series of accidents that happened to work. The Fractal IT Director owns the sequence and the decisions; Managed IT Services, Network Solutions and Helpdesk Support can sit beneath that strategy as execution services, supported by a trusted network of specialists where specific expertise is needed. For the wider group of services, evestaff.co.uk is the gateway.

The keys arrive on the date the lawyers agreed. Readiness is a different date, and it has to be planned.

SEO keywords:

Cloud Solutions, Managed IT Services, Network Solutions, Helpdesk Support, Voice and Connectivity, Disaster Recovery, Dynamics 365 Jump Start, IBM i Management, Technology Expense Management, Fractal IT Director, IT Consultancy

Join The Discussion