An office relocation looks like a moving-truck exercise until the Monday morning after the move, when nobody's phone works and the print server is unreachable. IT and cabling drive the go/no-go on every office move; the moving truck is the trailing edge, not the leading edge, of the project.
- Kickoff four to six months before move date for anything over 50 seats.
- Cutover, not install, is the risk-critical window.
- Coordinate with carriers 45–60 days ahead; circuits are the long-lead item.
- Freeze scope four weeks before move; changes after freeze cause weekend outages.
Executive summary
A successful office move is a stack of parallel timelines — cabling, carriers, furniture, security systems, and end-user IT — that converge on a single cutover weekend. The IT project manager owns the critical path, the cabling contractor owns the building infrastructure, and the carriers own the wide-area circuits. Missing any of these dates cascades.
Why moves fail
The move itself is not the problem. The problem is that the cabling was completed on Friday, the carriers turned up the circuit on Saturday, the phone system was configured on Sunday, and nobody discovered that the primary Internet circuit was provisioned to the wrong suite until Monday at 8:30 AM. Sequencing and validation are what separate the successful move from the memorable one.
Timeline
| Weeks before move | Milestone |
|---|---|
| 16–24 | Space finalized, IT scope defined, contractor selection |
| 12–16 | Cabling design, carrier orders placed |
| 8–12 | Cabling install begins, MDF/IDF hardware ordered |
| 6–8 | AP survey and access-control design |
| 4–6 | Circuits delivered and tested, scope freeze |
| 2–4 | Furniture, workstations staged, pilot users cutover |
| Move weekend | Bulk cutover, validation, day-one support ready |
| +1 week | Punch list closeout |
Common mistakes
- Ordering circuits after cabling starts — carriers routinely miss dates.
- No pilot cutover — the first person to plug in on Monday morning finds every configuration bug.
- No pre-move Wi-Fi survey — density is wrong, roaming is broken, complaints start day one.
- No documentation of the old space — hard to identify what needs to be reproduced.
Best practices
- Build a single unified schedule with cabling, carriers, security, and furniture on it.
- Assign one IT project manager as the single point of accountability.
- Pilot cutover with a small group two weekends before the main move.
- Prestage everything: rack switches, program phones, image workstations.
- Staff the help desk with 2× normal Monday coverage for at least the first week.
Checklist by category
- Cat6A horizontal to every seat
- Diverse fiber to backbone
- Server room commissioned with UPS and cooling
- All drops labeled and certified
- Fiber Internet primary + secondary
- SIP trunks configured
- Circuits tested end-to-end 2 weeks before move
- Post-install survey
- Guest and staff SSIDs
- Roaming tuned
- Access control programmed for all employees
- Cameras online with retention verified
- Alarm system tested
When to call a professional
Any move over 25 seats or involving a new building should have a low-voltage contractor on retainer for the duration. Circuit-only moves can sometimes be self-managed; anything that touches building infrastructure benefits from a partner who has done it 100 times before.