Decommission the old site safely
Once the move is complete and everyone is happily working in the new office, it’s tempting to forget about the old one. But there are a few important tidy‑up tasks:
- Cancel or migrate any remaining internet, voice and monitoring services
- Remove old switches, servers and security devices that shouldn’t be left behind
- Securely dispose of or recycle obsolete equipment and cabling
- Ensure no sensitive data is left on forgotten devices or storage
A structured exit prevents you from paying for services you no longer use – and avoids leaving anything behind that could pose a security or compliance risk.
Capture documentation and support plans
Finally, treat the new office network as a fresh starting point:
- Update network diagrams, cabinet layouts and patching schedules
- Make sure Wi‑Fi designs, SSIDs and security configs are documented
- Record circuits, providers, contact details and contract dates
- Agree support arrangements for cabling, network hardware and critical systems
This is also the right moment to think about ongoing IT maintenance and refresh cycles. Building cabling and infrastructure into a planned programme is far less painful than waiting for the next big move or failure.
FAQs: IT and network checklist for office relocation
Q: When should IT start planning for an office move?
Ideally 3–6 months before move‑in, depending on the size and complexity of the office. This gives enough time to design cabling and comms rooms, order circuits with long lead times and coordinate with the fit‑out programme.
Q: Can we reuse the cabling that already exists in the new office?
Sometimes – but don’t assume it’s fit for purpose. You’ll need to check the age, category (Cat5e/Cat6/Cat6A), condition and coverage of existing cabling. In many cases, it makes sense to reuse some runs and replace others as part of a structured design rather than simply inheriting whatever the last tenant left.
Q: How do we avoid downtime during the move?
The key is to build and test the new network before you move, then plan a phased migration with clear change windows. Use parallel running or temporary links where needed, and avoid last‑minute big‑bang cutovers wherever possible.
Q: Do we have to move all our servers, or should we go cloud at the same time?
An office move is a natural moment to review your on‑premises vs cloud strategy. Many organisations use it as an opportunity to retire or consolidate servers and move suitable services into the cloud – reducing what physically needs to move. Just be careful not to take on too many major changes at once; sequence projects sensibly.
Q: Who should own the IT part of the office relocation?
Ideally, a joint team involving IT, facilities, project management and your chosen network/cabling partner. IT should have a clear voice in decisions about space planning, programme and budget to ensure the office is not just beautiful, but also technically robust.
