Start IT planning 60 to 90 days out and order your connectivity first, because circuit and porting lead times, not packing boxes, decide whether your move causes two hours of downtime or two weeks. Work through five phases: audit, order, pre-stage, run the move-day runbook, then verify. Three things separate a clean move from a disaster: verified backups you’ve actually restored, one named owner who makes the calls, and a written runbook with a clear rollback point.
TL;DR:
- Ordering circuits and porting phone numbers early is critical, as provisioning delays often cause the longest move downtime and cannot be sped up later.
- Completing a full audit with detailed labeling and photographing assets ensures proper tracking and minimizes equipment mismatches during reinstallation.
- Confirming cabling, power, and network readiness in advance prevents costly and disruptive retrofitting after the move; pre-staged and tested core equipment streamlines reconnecting.
- Running verified, offsite backups and exporting device configurations before disconnection safeguards data and system settings against transit risks.
- Designating a single move owner, establishing clear communication, and creating a detailed runbook with rollback triggers reduce errors and provide authority during the transition.
Table of Contents
- How do you build an office IT relocation checklist timeline?
- What goes in your IT asset register before the move?
- When should you order internet and phone services for a move?
- What does comms-room readiness look like before move day?
- How do you back up data safely before an office move?
- What’s the move-day sequence for shutting down and reconnecting IT?
- How long should snagging and stabilisation take after a move?
- Who should coordinate suppliers and communicate with staff?
- Techbug’s perspective: what we enforce on every relocation
- How Techbug can support your IT relocation
- Useful sources for the move
- FAQ
How do you build an office IT relocation checklist timeline?
Furniture and fitout schedules get all the attention in office moves, but IT is usually the real critical path. Cabling, power and connectivity need to start weeks before anyone books a removalist.
- 60 to 90 days out. Walk the new site, confirm which ISPs actually service that address, and place your circuit and phone orders immediately. Run a full asset audit of every device you own, and decide now which gear gets relocated and which gets retired.
- 30 to 45 days out. Lock in cabling and electrical trade dates, and start pre-staging comms-room equipment. Confirm the exact windows for number porting and place orders for any replacement hardware, since supply delays hit at the worst possible moment otherwise.
- One to two weeks out. Run full backups and test-restore a sample of that data. Label every device, export firewall and switch configurations, and freeze non-essential changes to the network so nothing shifts under you.
- Move weekend and week one. Reconnect in sequence, run a small group of pilot users before the full team logs on, and staff a triage desk that logs and assigns every fault as it’s reported.
The pattern behind this schedule is simple: everything with a long lead time (circuits, cabling, hardware orders) goes first; everything reversible (configuration, testing) goes last.
What goes in your IT asset register before the move?
You cannot pack, transport or reinstall equipment you haven’t properly counted. A full audit and inventory before disconnection prevents lost devices, mismatched cables, and the two-day scramble to find out which monitor belongs to which desk.
For every asset, record:
- Make, model and serial number
- Current location and destination location in the new office
- Assigned user and department
- Network port and VLAN assignment
- Warranty status and physical condition
Colour-coded or numbered labels on each device, paired with a desk map for the new floor plan, turn reinstallation into a matching exercise rather than a guessing game. Photograph every rack and patch panel before you touch a cable. For replace-versus-relocate decisions, weigh age, remaining warranty and transport risk; a five-year-old switch nearing end of life is rarely worth the freight cost of moving it. Fragile items like UPS batteries and older storage arrays need their own handling plan, since knocks during transport can shorten their working life significantly.
Pro Tip: Export your switch, firewall and phone system configurations before the audit ends, and give each exported file the same ID you used on the physical label. When it’s time to reinstall, you’re matching numbers, not memories.
When should you order internet and phone services for a move?
Order the moment your move date is confirmed, not when the lease starts. Provisioning circuits and porting phone numbers commonly become the single biggest cause of relocation delay, and starting late is the one mistake this checklist can’t fix retroactively.
- Check with providers about lead times for the exact new address, not just the suburb, since building-specific infrastructure varies enormously.
- Keep your old circuit live and running in parallel rather than cancelling it on move day. That overlap window is your safety net if the new line has problems.
- Start number porting early, and avoid scheduling the port for the same day as the physical move. A failed port on move day, stacked on top of everything else going on, is a bad combination.
- Prepare a fallback: cellular failover for critical systems, a temporary VPN setup for staff working from home, or simply keeping limited operations running at the old site for a few extra days.
Failure to order early is one of the most common causes of extended downtime in office relocations, precisely because it’s the one task with no way to speed it up once you’re behind. Everything else on this list can be compressed under pressure. Circuit provisioning can’t.
What does comms-room readiness look like before move day?
Walk the new space before anything is installed and map out rack position, power outlets and data points against your actual floor plan. Plan for two data outlets per desk at minimum, plus spares for growth or hot-desking, because retrofitting cabling after fitout is expensive and disruptive.
- Have structured cabling installed and properly certificated rather than relying on a quick patch job.
- Document a patch schedule and label every patch panel to match your asset register IDs.
- Pre-stage and configure core switches, firewalls and wireless controllers in the comms room before move weekend arrives, so move day is a reconnection exercise, not a build exercise.
- Test and certify the cabling and network performance before any equipment goes live on it.
If you’re weighing wired versus wireless coverage for the new floor plan, it’s worth understanding the trade-offs between ethernet and wifi before the cabling contractor finalises the outlet count. Adding data points later costs far more than including them at fitout stage.
How do you back up data safely before an office move?
- Run a full backup well ahead of the move, then verify it by actually restoring a sample of that data. A backup nobody has tested is a hope, not a plan.
- Store that backup offsite or in the cloud, never solely on the equipment being physically moved. If the truck has a bad day, your data shouldn’t.
- Export firewall, switch and phone system configurations, and keep copies with the move team, not locked inside the device being disconnected.
- Check for encrypted drives, software licences tied to hardware, and vendor lock-ins that could block reactivation once the equipment lands at the new site.
A hardened backup approach, along the lines of immutable backups, adds a layer of protection here: even if something goes wrong physically during transit, your last verified copy stays untouched and recoverable.
What’s the move-day sequence for shutting down and reconnecting IT?
- Hold a go/no-go meeting 48 hours before disconnection. Confirm cabling is certified, circuits are live, and backups are verified. If any of those three aren’t ready, delay the move rather than push through.
- Shut down and reconnect in strict order: circuit and firewall first, then core switching and wireless, then servers, then a small pilot group of users, and only then the full staff rollout.
- Maintain a chain of custody for every piece of equipment in transit, with a reconnection checklist specific to each device type so nothing gets plugged in blind.
- Agree rollback triggers before the move starts, not during it: who has authority to call it, and the exact point past which rolling back to the old site is no longer realistic.
Pro Tip: Write the rollback decision point into the runbook as a time, not a feeling. “If core systems aren’t verified by 6pm Sunday, we hold at the old site” removes the argument exactly when everyone is tired and least equipped to have it.
A pre-written, practiced runbook matters more here than speed. Rushing the sequence to save an hour is rarely worth the risk if it means skipping a verification step.
How long should snagging and stabilisation take after a move?
Pilot users should test email, file access, phone lines and core business apps before the wider team logs on, against clear acceptance criteria rather than a gut feeling that “it looks fine.”
- Keep a daily snag list through week one, with an owner and a target date assigned to every open item, not a general pool of unresolved tickets.
- Check internet throughput, VPN stability, backup jobs and application access daily, since wireless coverage and cabling faults often only surface under real daily load.
- Formally hand over to business-as-usual once critical systems meet their acceptance criteria and sign-offs are in, rather than letting the project quietly fade out.
Rapid device repairs matter here too. If a laptop or workstation fails during that first week, a fast local repair turnaround keeps one broken machine from becoming a broader productivity hit.
Who should coordinate suppliers and communicate with staff?
Assign one named owner for the entire relocation and publish their contact details, along with every vendor’s contact and responsibility, so nobody is guessing who to call when something goes wrong.
- Tell staff plainly what will be unavailable, when, and how to reach support during the transition, since clear staff communication cuts support ticket volume far more than any technical fix does.
- Get written confirmation from vendors on the specifics: circuit delivery windows, cabling sign-off dates, and the removalist’s arrival time.
- Set up an escalation path with an emergency contact for anything that qualifies as a critical failure, not just a general help-desk queue.
Techbug’s perspective: what we enforce on every relocation
Vendor-agnostic doesn’t mean unstructured. On every relocation, we hold firm on four things regardless of provider: pre-staged and tested firewall configs, backups that have actually been restored, one named owner with real authority, and a runbook with a rollback point agreed before anyone starts unplugging. Smaller offices with a straightforward setup can often run this checklist in-house. Multi-site networks, complex phone systems or tight compliance requirements are where bringing in managed support earns its keep.
— Ru
How Techbug can support your IT relocation
A managed IT services provider can be the alternative to running a move entirely on internal goodwill and crossed fingers. Our vendor-agnostic approach means we’re not steering you toward one brand of switch or one ISP because of a reseller deal, we’re recommending whatever fits your actual network. For relocations, this can include move-owner services, comms-room pre-staging, runbook creation, hands-on move-day execution and dedicated week-one support to catch the snags before they become entrenched problems.
Because a relocation rarely runs to plan without a hitch, an emergency response team is available if a circuit fails to activate on schedule or a core switch doesn’t come back up cleanly. If you’d rather have an experienced team run the checklist than build and execute it yourself, get in touch with Techbug’s managed IT services to scope your move date and get a plan started.
Useful sources for the move
- JAS‑ANZ certificate record — verify a contractor’s certification status.
- QAssure supplier details — confirm supplier credentials before cabling works begin.
- Databox support portal — check install windows and provisioning status.
- G — verify vendor address and local presence.
FAQ
How far in advance should you start an office IT relocation checklist?
Start 60 to 90 days before the move date, with connectivity orders and the full asset audit as the first two tasks. Circuit and phone porting lead times are usually the longest part of the whole project, so anything ordered late tends to set the entire schedule back.
What’s the biggest cause of downtime during an office move?
Late-ordered internet circuits and phone porting are the most common cause of extended downtime, because provisioning timeframes can’t be compressed once you’re behind schedule. Keeping the old circuit live in parallel with the new one gives you a fallback if provisioning runs late.
Should you replace or relocate ageing IT equipment?
Weigh remaining warranty, age and transport risk before deciding. Equipment near the end of its warranty or already showing hardware faults is often cheaper to replace than to insure, transport and reinstall.
What should be in a move-day IT runbook?
A runbook needs the shutdown and reconnection sequence, named roles for each step, a chain-of-custody process for equipment in transit, and pre-agreed rollback triggers with a clear decision authority. Techbug builds this runbook, including the rollback point, as a standard part of managed relocation support.
How do you test that a data backup will actually work after a move?
Run a full backup, then restore a sample of that data before you disconnect anything, rather than assuming the backup job completing means the data is recoverable. Store the verified backup offsite or in the cloud so it survives even if equipment is damaged in transit.