Office Move IT Checklist: Internet, Cabling and Devices

Moving an office is not just a furniture project. Internet service, cabling, Wi-Fi, computers, phones, printers, cloud access and vendor handoffs all have to work together before employees arrive. The safest approach is to give the technology move its own owner, timeline, acceptance tests and fallback plan.

This office move IT checklist organizes that work from early planning through the first business day. Adjust the timeline for construction, carrier lead times, building access and the complexity of your environment.

8–12 weeks before the move: define the technical plan

Assign one move owner and one decision path

Name one person who can coordinate leadership, the landlord, building management, movers, the internet provider and every technology vendor. Document who can approve changes, spending and service interruptions. A single decision path keeps a last-minute cabling or carrier issue from bouncing between people.

Create a contact sheet with the primary and backup contact for each vendor. Include account numbers, escalation routes, appointment windows and access requirements. Keep an offline copy available on move day in case cloud access is temporarily unavailable.

Build a complete technology inventory

List every laptop, desktop, monitor, dock, phone, printer, scanner, conference-room device, wireless access point, firewall, switch, server, battery backup and specialty system. Record the owner, current location, destination, serial number, power requirement, network connection and whether the item will move, be replaced or retired.

This is more than a packing list. CISA recommends maintaining an inventory of physical and logical IT assets and understanding which systems support critical business services. That principle helps you decide what must come online first at the new location. See the CISA StopRansomware Guide for the underlying asset and dependency guidance.

Map critical services and dependencies

Write down what the business needs to operate on the first morning: email, shared files, cloud applications, phones, payment systems, printers, shipping tools, cameras, access control and line-of-business software. For each service, identify its internet, network, power, account and vendor dependencies.

Set a recovery priority. Revenue, customer service, security and regulatory obligations usually come before convenience systems. NIST contingency-planning guidance emphasizes documented roles, equipment requirements, vendor contacts, system interconnections and clear step-by-step procedures. Although the NIST guide is written for federal systems, those planning concepts translate well to a commercial move. Review NIST SP 800-34 Rev. 1.

6–8 weeks before the move: order circuits and design the network

Confirm internet service in writing

Do not assume the service available at the old office can be transferred on the date you need. Confirm the exact service address, suite, demarcation point, installation date, bandwidth, upload speed, equipment, contract term, static IP requirements and support escalation process.

Choose capacity based on real usage: number of users, cloud applications, voice and video traffic, backups, guest Wi-Fi and any remote-access needs. The FCC advises considering upload as well as download performance and evaluating service, contract terms and upgrade options. Its Broadband Made Simple guide provides a useful starting framework.

For a business that cannot operate without connectivity, consider a secondary circuit or cellular failover. Document what the backup connection can support and test it before the move.

Approve the floor plan before cabling

Mark every workstation, access point, printer, phone, conference room, camera, point-of-sale device and network closet on the floor plan. Count data drops by location and add spare capacity where future staff or equipment is likely.

The network closet needs secure access, ventilation, reliable electrical service, grounding where required, rack space and room for patch panels, switching, firewall equipment and battery backup. Coordinate low-voltage work with building rules and construction schedules. Sosa Solutions NYC can help with network cabling and Wi-Fi installation, including layout planning, installation and testing.

3–4 weeks before the move: prepare devices, accounts and vendors

Standardize, update and back up

Confirm that business data is backed up and that a restore has been tested. Install operating-system and application updates before the final change freeze, not while users are waiting at the new office. Verify disk encryption, endpoint protection and multifactor authentication on systems that support it.

Create a device packing label that shows the user, destination room or desk, device set and priority. Photograph complicated cable arrangements before disassembly. Record firewall, switch, access-point and printer configurations securely so the environment can be rebuilt if a device fails in transit.

Create the cutover runbook

Schedule every dependency in order: building access, carrier handoff, cabling completion, network rack installation, firewall and switching, Wi-Fi, devices, phones, printers, applications and user acceptance testing. Give each task an owner, start time, success test and fallback action.

Confirm which vendors will be onsite and which will be available remotely. Share only the access they need, and remove temporary access after the move. If you want one technical coordinator across providers and equipment, review Sosa Solutions NYC’s on-site IT support and managed IT services.

Final week: freeze changes and rehearse opening day

Avoid nonessential system, password, network and application changes during the final days. Confirm backups again, print the runbook and contact sheet, and hold a short readiness review with every owner.

Use this final-week gate:

• Internet installation is complete and tested from the network closet.

• Cabling is labeled at both ends and every required drop has passed testing.

• Firewall, switches and wireless access points have approved configurations.

• Critical cloud applications and licenses are ready for the new location.

• Devices, chargers, docks and peripherals are labeled by destination.

• Phone numbers, call routing and emergency information are confirmed.

• Printers and specialty devices have drivers, addresses and test procedures.

• A fallback connection and work location are documented.

• Employees know the move schedule, support route and first-day expectations.

Move day: restore services in business-priority order

Start with the network closet and internet handoff. Bring up the firewall, switches and wireless access points, then confirm internal connectivity, DNS, cloud access and the backup circuit. Restore priority workstations and business systems before convenience devices.

Test with real workflows, not only green status lights. Send and receive email, open a shared file, place and receive a call, print a document, join a video meeting and complete a safe test transaction where applicable. Confirm guest Wi-Fi is separated from business systems and that remote management and monitoring still work.

Track every issue with an owner, priority and next update time. If a critical service fails, follow the runbook’s fallback instead of improvising undocumented changes under pressure.

First business day: support users and close the gaps

Provide a clearly advertised support channel and keep technical coverage available during the busiest arrival period. Watch internet stability, Wi-Fi performance, authentication failures, printing, voice quality and application access. Fix patterns before handling cosmetic requests.

At the end of the day, record unresolved issues, update diagrams and inventories, remove temporary vendor access and confirm that backups and monitoring are running in the new environment. Schedule a short after-action review within the week so lessons become permanent documentation.

A successful office move is a tested service transition

The move is complete when employees can perform their priority work reliably—not when the last box reaches the new address. An inventory, dependency map, approved network design, cutover runbook, fallback plan and real workflow tests turn a risky relocation into a controlled transition.

Planning an office move in New York, New Jersey, Connecticut or Florida? Contact Sosa Solutions NYC to coordinate internet, cabling, network equipment, device setup and opening-day IT support.