Moving offices is one of the most disruptive IT events a business faces. Follow this practical checklist to keep downtime to a minimum and avoid the common mistakes that catch Melbourne businesses off guard.
An office move ranks alongside a major system upgrade as one of the IT events most likely to cause unplanned downtime. The physical chaos of a relocation - removal trucks, new floor plans, staff on different schedules - masks a dozen IT decisions that need to be made weeks in advance. Get them wrong and you’re facing days without internet, phones that don’t work, or servers that never made it to the rack in one piece.
This checklist is built from hard experience managing relocations for Melbourne businesses of all sizes. Work through it in the order given - the sequencing matters.
8–12 Weeks Before Move Day
Audit your current cabling and infrastructure. Before you plan the new space, understand exactly what you have. Document every switch, patch panel, access point, and server. Photograph rack layouts. This is also the time to identify what’s worth moving versus what should be replaced.
Order your internet connection at the new premises immediately. This is the step most businesses get wrong. NBN Business and dedicated fibre connections can have lead times of 4–10 weeks depending on the building and provider. If you haven’t ordered by now, you may not have connectivity on day one. Check whether the building has existing in-building infrastructure (many Melbourne CBD buildings have building-wide fibre that dramatically shortens lead times) and confirm who is responsible for internal cabling between the building entry point and your tenancy.
Engage an IT cabling contractor. Your new office will need structured cabling - data points, patch panels, rack location - before any IT equipment goes in. Coordinate with your fitout team to ensure the cabling contractor has access during the build phase, not after. Nothing adds cost like having to lift freshly installed carpet to run cables.
Review your phone system. If you’re on a legacy PBX, a relocation is a natural trigger to move to a cloud-based phone system (Microsoft Teams Calling, or a hosted VoIP solution). This avoids the cost and complexity of relocating physical PBX hardware. If you’re keeping an existing system, confirm with your telco the process for porting or redirecting numbers - this needs to be initiated well in advance.
Confirm your server relocation plan. Physical servers going into a new rack need a shutdown procedure, transport plan (ideally in original packaging with anti-static precautions), and a defined bring-up sequence. If your environment is virtualised and running on-premises, this is also a good time to evaluate moving workloads to Azure or another cloud platform rather than relocating hardware at all.
4–6 Weeks Before Move Day
Design the new network layout. Where does the rack go? How many data points per workstation? Where are the access points going, and have you done a wireless survey of the new space? Don’t assume your old access point count translates directly - open plan offices, glass partitions, and concrete ceilings all affect coverage differently.
Update your DNS, firewall, and VPN configurations. If your new office has a different public IP address, update any DNS records, firewall rules, or VPN configurations that reference the old IP. This includes third-party services (payment gateways, some SaaS platforms, and remote access tools often have IP whitelisting).
Notify vendors and update your address. Cloud licensing, hardware warranties, ISP accounts, backup monitoring services - all of them have your old address. Create a checklist and work through it methodically.
Brief your staff. Tell people what IT services will be available on move day, what to expect, and who to call if something doesn’t work. Set expectations around the first 24–48 hours. Even a well-planned move will have minor issues; managing expectations prevents panic.
1–2 Weeks Before Move Day
Stage and test equipment off-site if possible. Rack up servers, switches, and patch panels in a staging environment. Power everything on and test connectivity before it goes into the new premises. This surfaces hardware failures and configuration issues in a controlled setting.
Label everything. Every cable, every patch panel port, every device. A few hours of labelling now saves days of troubleshooting later. Use a consistent scheme across both ends of every cable run.
Back up everything - again. Yes, your backups run nightly. Do an out-of-band backup of critical systems immediately before the move anyway. If a server is damaged in transit, you want the freshest possible restore point.
Confirm your cutover window. Agree on an exact time that services will be taken offline at the old premises and brought online at the new ones. Communicate this to staff and to any third parties who need to know (hosted service providers, offshore teams, etc.).
Move Day and After
Have an IT technician on-site. Not just available by phone - physically present. Things will come up that need hands-on troubleshooting. This is not the day to try to remote-support a cabling issue.
Test in a defined sequence. Internet up first, then core switching, then servers, then workstations, then phones. Don’t declare success until each layer is confirmed working before moving to the next.
Document what changed. Update your network diagrams, asset register, and configuration documentation to reflect the new layout. This is painful to do after the fact - do it while it’s fresh.
Run a 48-hour check. Revisit any open issues at the 48-hour mark. Some problems (intermittent connectivity, VoIP quality, printer discovery) only show up under normal workload conditions.
A well-managed IT relocation is absolutely achievable - it just requires the same planning discipline as any other project. If you’re planning a Melbourne office move and want expert support from initial audit through to go-live, CX IT Services handles end-to-end IT relocations.
