A new office can be ready for desks and boxes while still being unready for work. Internet service may not be active, Wi-Fi coverage may miss key rooms, phones may depend on a network configuration that has not moved, and the meeting room system may be waiting on a cable or account. If IT planning begins after the move date is set, the business inherits avoidable downtime at exactly the moment employees need to settle in.
Make technology a workstream in the relocation plan, not a task for the final weekend. Give one person responsibility for the IT cutover, connect that owner to facilities and business leads, and work backward from the first day people need to operate at the new location. The goal is not simply to power up old equipment. It is to confirm that the right services, access, and support are ready in the new space, with a fallback if a dependency slips.
Start with a move inventory and service map
Begin with an inventory of what the business uses today and what must work on day one. Include internet circuits, firewall and network equipment, wireless access points, phones, printers, scanners, conference-room systems, cameras, door access, servers or network-attached storage, and any specialized equipment. Record who owns each service, who supports it, how it is connected, and whether it must move, be replaced, or can be retired.
Then map the services to people and workflows. A list of devices alone will not tell you that a shipping station needs a wired connection, a conference room needs a room account, or a remote employee depends on a VPN profile to reach an application. Identify business-critical activities such as taking payments, answering calls, dispatching work, approving invoices, and joining customer meetings. For each, name the business owner, the technology dependencies, and the longest acceptable interruption.
Walk the new site with a floor plan. Mark the internet handoff point, wiring closets, desk areas, conference rooms, printers, access points, and places where equipment needs power or wired network connections. Check the basics early: building access for installers, available cabling paths, power, rack or cabinet space, ventilation, and any landlord or construction approvals. For Teams Rooms deployments, Microsoft advises confirming physical room readiness and preparing the corporate network as distinct deployment steps, with coordination across network, facilities, and audiovisual teams. Its overview is at https://learn.microsoft.com/en-us/microsoftteams/rooms/rooms-deploy.
Order connectivity and cabling before move week
Contact the internet and voice providers as soon as the address and move date are firm. Confirm that the new location can receive the required service, what must be installed, who can authorize the order, when the provider can access the building, and whether the current service can remain active during transition. Separate the date equipment is installed from the date service is tested and ready; a modem or circuit present in a closet does not prove that business applications will work.
Ask the provider to document the service handoff, circuit identifiers, static IP details if applicable, support contacts, and any equipment they expect the business or IT provider to supply. Coordinate that information with the firewall configuration, remote-access settings, phone service, and any allowlists used by business partners. If the internet circuit is delayed, decide in advance whether a temporary connection or backup path can support essential work. Do not wait until the day before the move to compare fallback options.
Plan structured cabling around real room use, not desk count alone. Include access points, conference-room equipment, shared printers, security systems, and devices that need wired connections. Label and test ports before furniture blocks access, and assess wireless coverage for room layout, walls, and user density rather than assuming the old router placement will work.
Coordinate network and audiovisual work together. Teams Rooms have specific environmental and network preparation requirements, so confirm room layout, cabling, network access, resource accounts, and device management before the installers arrive. Microsoft’s environment preparation guidance is available at https://learn.microsoft.com/en-us/microsoftteams/rooms/rooms-prep. A meeting-room system that is powered on but cannot authenticate or reach required services is not ready for a customer call.
Design the cutover around how the business works
Create a cutover runbook with dates, owners, dependencies, vendor contacts, expected downtime, and a go/no-go decision. Put work in dependency order: finish cabling, activate the circuit, configure the network, reconnect critical devices, validate applications, and communicate move-day support. Assign an owner and completion check to each critical step instead of relying on “IT has it covered.”
Decide which services can move ahead of employees and which must change during the final cutover. Where possible, stage and label network equipment before it reaches the new site, prepare configurations, and test devices in advance. For cloud services, confirm that sign-in, multifactor authentication, device management, and remote access remain available from the new network. For phones, verify number routing, call queues, voicemail, and emergency calling arrangements with the provider; for printers and scanners, confirm their network and application dependencies.
Tell employees when to pack equipment, how to reconnect, and where to report issues. Share the help contact and cutover sequence, and book provider, cabling, security, and audiovisual vendors against the same calendar with building access confirmed.
Set a rollback or contingency for the services that matter most. This does not mean keeping every old system active indefinitely; it means agreeing on what the team will do if the circuit is not live, a key application fails, or a critical device cannot connect. Options could include keeping the old office available briefly, using an approved temporary internet connection, shifting essential work to a cloud workflow, or delaying a nonessential part of the move. Make the decision owner and trigger clear before pressure rises.
Test the workflows before the first workday
Use a checklist that reflects real work, not just a green light on each piece of equipment. Test wired and wireless connections in the places people will use them. Sign in with representative user accounts. Open the applications employees need, place and receive calls, print and scan a sample document, join an external meeting, and confirm that shared drives or cloud files are available. Check that the right people can reach printers, cameras, and access-control systems without exposing them to the wrong network segments.
Test each conference room end to end: reserve it, join a meeting, use the camera and microphone, share content, and confirm the room account and display work. Microsoft's Teams Rooms guidance separates site readiness, network preparation, account setup, deployment, and testing—a sequence that can expose missing dependencies before the first customer meeting.
Schedule a final readiness review with the move owner, facilities, business leads, and IT. Review open issues, confirm that high-priority tests passed, and decide whether unresolved items are blockers or can be handled through a documented workaround. Provide employees with a short first-day guide: where to get help, how to connect, what to do if a room or printer is unavailable, and how to report an issue without interrupting the whole team.
Close out the old site and capture what changed
Update records with the new circuit and support details, network diagrams, equipment and room locations, wireless coverage notes, vendor access, and new dependencies. Remove obsolete firewall rules, wireless networks, device records, and services. Confirm that access to the former site and its systems is handled deliberately.
Track issues during the first few weeks. Repeated dead zones, poor call quality, or login failures can signal coverage, network, or identity gaps. Assign owners and target dates, then compare results with the original move plan. This feedback can make future expansions or renovations less disruptive.
An office move is a business change with a technology cutover inside it. Start early, map the physical and digital dependencies, coordinate the people who own them, and test the work employees actually perform. With a clear runbook and contingency, the new office can open as a place to work—not another project waiting on the network.
