Scope the project
Devices, network equipment, phone lines, printers, and any vendor-dependent system are inventoried before a moving-day plan is written.
Office moves & IT projects
An office move, a tenant migration, or a multi-site rollout is not routine support with a bigger to-do list—it is a project, with its own scope, timeline, and price. Handled well, it follows the same rhythm as everyday care: listen to what the business actually needs, clarify the plan, handle the work, and explain what changed.
A move date creates pressure before anyone has confirmed what actually needs to happen.
Devices, network equipment, phone lines, printers, and any vendor-dependent system are inventoried before a moving-day plan is written.
Who approves cost, downtime windows, and changes to the new space is agreed early, along with a realistic sequence for internet and network readiness at the new location.
The move is quoted and scheduled as its own engagement, so routine support elsewhere is not quietly stretched thin to absorb it.
The best moves are the ones where Monday morning looks unremarkable.
Network and internet readiness at the new site is confirmed before the move weekend, so the first task Monday is working, not troubleshooting.
Workstations, network equipment, and business phone lines move with a tracked plan rather than a box-and-hope approach, including coordination with the phone or internet provider on any number or service transfer.
Core systems—mail, shared files, line-of-business applications, printing—are tested working before the team is told to resume normal work.
A project is not finished when the boxes are unpacked; it is finished when the record is closed.
What moved, what changed, any temporary workaround, and any item still open is documented rather than left to memory.
Once the environment is stable at the new location, ongoing support returns to its normal monthly rhythm rather than staying in project mode indefinitely.
Lease-related cabling and electrical work, construction coordination, and building-management requirements remain the responsibility of the appropriate contractor, coordinated rather than performed by IT.
Prepare this
Continue
Bring the context; keep credentials out of the message.
Request an introductionDescribe the interruption, the change ahead, and how your team prefers to be kept informed. A short note is enough to begin a service-fit conversation.