Moving offices without disrupting technology takes more than packing computers. You need working internet, tested cabling, phones, Wi-Fi, business applications, security systems, and a plan for anything that does not work on schedule.
Start at least eight weeks before move day. For fiber installations or construction work, start earlier: provider lead times depend on the building, location, permits, and available infrastructure. Your provider, not a generic estimate, must confirm the actual install date.
Use this checklist to organize the work, assign owners, and reduce the risk of opening day becoming an IT recovery project.
8+ WEEKS OUT: SET THE PLAN
Name one person to coordinate the IT move. Confirm the move date, acceptable outage window, decision-makers, budget, and who can approve a rollback if the new site is not ready.
Create an inventory of equipment and services at both locations. Include servers, storage, firewalls, switches, Wi-Fi access points, phones, printers, UPS units, cameras, access-control devices, cloud services, and vendor contacts. Note what will move, what will be replaced, what will migrate to the cloud, and what will be securely retired.
Then check the new space with your landlord, general contractor, ISP, and technology vendors. Confirm:
- Where the internet service enters the building and whether the cabling route is accessible.
- Whether the communications room has secure access, suitable power, cooling, and room for a rack.
- When walls, ceilings, furniture, and electrical work will be ready.
- Which equipment requires wired connections, including printers, conference-room systems, cameras, and access readers.
- Whether your current internet service can transfer, and how long you need to keep the old service active.
A written scope and schedule help everyone work from the same plan. Our infrastructure services cover the systems beneath your applications, including networks, servers, storage, and reliability planning.
6–8 WEEKS OUT: ORDER INTERNET AND DESIGN THE NETWORK
Order the primary internet circuit as early as possible. Installation can take several weeks, and construction, permits, or building access can extend the schedule. Ask the provider to confirm the expected date in writing and clarify who handles inside wiring, equipment, and testing.
Ask whether the new circuit needs a static IP address. If it does, identify systems that may depend on the current address, such as remote access, firewalls, or vendor allowlists. Keep the old circuit active until the new location has passed testing.
Consider a backup connection if losing internet would stop essential work. A different provider or connection type may offer more resilience, but only if the backup is genuinely independent enough for your situation. Have your IT team test failover rather than assuming it will work.
Plan network and cabling around the actual floor plan. Mark desk locations, meeting rooms, printers, access points, cameras, and other devices that need wired connections. Decide where Wi-Fi coverage matters, including conference rooms and shared spaces. A site survey can help identify coverage gaps before furniture and staff make them harder to fix.
Agree on cable type and capacity with your cabling contractor. Require both ends of each run to be labeled, the work to be tested, and the final cable map to be documented. Confirm cable routes, power, and equipment locations before walls or ceilings close.
4–6 WEEKS OUT: DECIDE WHAT MOVES
Not every business needs to move every server. Compare the effort and risk of moving existing equipment with migrating suitable services to cloud platforms. Cloud-first does not mean every application should move; compatibility, licensing, data transfer, security, cost, and recovery requirements all matter.
For equipment that will move, plan the shutdown, packing, transport, installation, and startup. Record how systems connect, including rack locations, cables, power, and dependencies. Back up configurations and important data before the move, and verify that your backups can be restored.
For a cloud migration or other major change, treat it as a separate project with its own schedule, testing, and rollback plan. Combining it with a physical office move can increase risk if there is not enough time to test both.
Include phones in the plan. Confirm whether your phone system is cloud-based or on-site, whether numbers or call routing need to change, and how phones will connect at the new office. Test inbound and outbound calls, voicemail, call transfers, and any conference-room phones.
Include cameras and access control, too. Confirm that devices have suitable cabling, power, network access, and any required connections to a monitoring or access platform. Assign a responsible vendor or internal owner for testing them.
2–3 WEEKS OUT: PREPARE AND REHEARSE
Prepare network equipment before it reaches the new office. Where practical, configure and label firewalls, switches, and access points in advance. Document network settings and take configuration backups. Write a cutover runbook that lists the order of work, the person responsible for each step, and the checks that must pass.
Tell staff what to expect. Share packing and device-labeling instructions, explain the outage window, and provide a way to contact support during the move. Identify a remote-work or temporary-connectivity option if the new office is not ready on time.
Use a simple go/no-go rule: do not make the old site unavailable until the new site has the connectivity and systems required to operate, or until business leaders knowingly approve the risk and fallback plan.
MOVE DAY: FOLLOW THE RUNBOOK
Keep the old location available until the new one passes its critical checks. If equipment is being physically moved, shut it down properly and protect it for transport. Do not assume that unplugging devices and reconnecting them later is a reliable migration plan.
At the new location, bring services up in a planned order:
- Confirm power and UPS operation.
- Verify the internet handoff and firewall.
- Bring up core network equipment, identity services, and storage.
- Start servers and business applications in dependency order.
- Bring up Wi-Fi, phones, printers, cameras, and access control.
- Test the systems employees need first.
Record what was tested and the result. If a critical check fails or the agreed outage limit is reached, use the rollback plan instead of making undocumented changes under pressure.
BEFORE STAFF ARRIVE: TEST THE FULL WORKDAY
A link light on a switch does not mean the office is ready. Test the experience employees and customers depend on.
Verify:
- Internet access, Wi-Fi coverage, and any planned backup connection.
- User login, authentication, business applications, shared files, and email.
- Printing, scanning, video meetings, and conference-room equipment.
- Inbound and outbound calls, voicemail, and call routing.
- Cameras and access-control devices.
- Remote access, vendor connections, monitoring, and backup jobs.
Use representative devices and test from more than one part of the office. Record problems, assign an owner, and confirm that fixes work before opening. Plan extra IT support during the first few business days; some issues only appear when staff and devices are active.
DECOMMISSION THE OLD SITE SECURELY
Do not leave data-bearing equipment behind or hand it to a mover without controls. Confirm that no applications, backups, users, or vendors still depend on the old site. Keep any required data and configuration backups, and verify that they are usable before retiring systems.
Track equipment by asset or serial number as it leaves the office. Store it securely while awaiting reuse, recycling, or destruction. Have storage media sanitized using a method appropriate to the device and data. If a qualified provider performs the work, keep the sanitization or destruction records.
The UK National Cyber Security Centre’s decommissioning guidance explains why asset inventories, recovery planning, secure handling, and documented sanitization matter.
MISTAKES THAT CAUSE MOVE-DAY DOWNTIME
The same avoidable gaps show up repeatedly:
- Ordering the internet circuit after construction is nearly complete.
- Designing cabling after desks, walls, or ceilings are already in place.
- Assuming an ISP installation date is guaranteed without confirming access and responsibilities.
- Moving servers without a verified backup, configuration records, or recovery plan.
- Changing the network, moving equipment, and migrating applications in one untested cutover.
- Forgetting phones, cameras, printers, access control, or devices in meeting rooms.
- Canceling the old internet service before the new office has passed acceptance testing.
- Skipping a real test and assuming that equipment powering on means the business is ready.
A small office move may need only a focused cutover and short stabilization period; a move involving server migrations, extensive cabling, or building work needs a broader schedule. The scope and cost depend on your inventory, site conditions, carrier work, and how much technology is changing. We will not guess at a universal price. Ask for a written estimate that separates circuit work, cabling, equipment, migration, testing, and decommissioning.
MAKE THE MOVE A PLANNED IT PROJECT
Reliable relocation depends on clear ownership, realistic lead times, documented dependencies, and testing before employees arrive. The same discipline used in good network management services and IT consulting services can help your team prepare, manage the cutover, and stay in control after the move.
We’ll also help your internal team understand what changed and how to support the new setup. Our goal is a reliable handoff, not making you dependent on us.
If you are planning an office move, let’s have an honest conversation about your timeline, equipment, and risks. There is no pressure to commit. Book a 30-minute conversation with a real consultant, and we’ll help you identify practical next steps.
