Most office moves do not fail on the truck. They fail on the things that were nobody's job: the internet circuit that is not live, the printer nobody mapped, the DNS record that still points at the old building. Staff then arrive on Monday to a floor where they cannot work.
This checklist runs in time order, from planning through the first 30 days. Use it as a template and adjust the dates to your lease and your carrier. It covers the IT side only. Furniture and boxes belong to your mover.
What should an office move IT checklist include?
An office move IT checklist should cover internet circuits, the network design, cabling, Wi-Fi, devices, phones, printers, move day roles, testing and the exit from the old site. Order it by time, because the early items have the longest waits.
The five stages below are a planning frame, not a rule. If your move date is closer than 12 weeks, start with circuits and the network plan, then work down the list.
What should you do 8 to 12 weeks before the move?
Eight to 12 weeks out, order the internet circuits and settle the design of the new site. Circuits are the longest wait, and the design decides everything built after it.
Circuit delivery can take weeks or longer. Order first, decide who places the order, and ask the carrier for a written install date. Do not plan the move around a verbal estimate.
- Survey the new office: network closet, power, cable pathways, ceiling access and where the carrier line enters (the demarcation point).
- Get the landlord's rules for contractor access, deliveries, lift bookings and after-hours work.
- Mark a floor plan with desks, printers, meeting rooms, reception and the network closet.
- Plan cabling and Wi-Fi from that floor plan. Run a survey of the new floor if the layout is open or dense.
- Inventory every asset. Decide what moves, what is replaced and what is retired.
- Plan IP ranges and VLANs for the new site, and list the DNS and firewall changes they need.
- Decide how phones and printing will work at the new site.
- Name the roles for move day: who decides, who accepts, who answers the phone.
What should you do 4 to 6 weeks before the move?
Four to 6 weeks out, build and test the new site while the old office keeps running. The aim is a network that works before the first desk arrives.
- Install and test the cabling, and keep the test results.
- Rack the network closet: patch panels, switches, firewall and access points.
- Stage switches and access points on a bench, configured and tested before they are mounted.
- Confirm each circuit install date in writing with the carrier.
- Verify backups, and run a restore test on at least one important system.
- Tell staff the dates, what to pack themselves and what to leave alone.
What should you do in the last 1 to 2 weeks?
In the final one to two weeks, label everything, pack by list and rehearse the weekend. Labels and lists are what keep a fast move from turning into guesswork.
ANSI/TIA-606, the administration standard for telecommunications infrastructure, rests on one idea: give each space, cabinet, panel and cable a unique identifier, and keep records that match the labels. You do not need the full standard. You do need one scheme used the same way on cables, ports, desks and the asset list.
- Label every desk, port, device and cable end. Print a desk map that matches the labels.
- Write pack lists per area, with the new desk or room for each item.
- Stage equipment that is new or replaced, so it ships to the new office ready to connect.
- Walk the weekend runbook with everyone who has a role. Test the rollback for the circuit cutover.
What happens on move weekend?
On move weekend, shut down in order, label and move, then rebuild and test by desk. Keep the old circuit and network ready to return to until the new site is accepted.
- Shut down in the written order, and record the time.
- Disconnect and label as you go. Photograph the closet and key desks.
- Movers carry the equipment. Check it against the pack list at both ends.
- Rebuild the network closet first, then the desks, printers and meeting rooms.
- Run the test list by desk: network, Wi-Fi, login, printing, phone, badge reader and key applications.
- Hold a rollback decision point for the circuit cutover, and agree in advance who calls it.
- Sign off area by area, and write down what is still open.
What should you do from day 1 to day 30?
From day 1 to day 30, support staff on the floor, work a snag list and then close the old site properly. The move is not done when the Monday email goes out.
- Day 1: put floor walkers on the floor to fix problems at the desk, and keep a visible way to report them.
- Keep one snag list with an owner and a date for each item, and review it daily at first.
- Update the asset register with the new locations and any changes.
- Sanitize data-bearing devices you are retiring, following your own policy. NIST SP 800-88 Rev. 2 helps choose techniques based on how sensitive the data is. Keep a record by serial number.
- Return leased equipment and collect proof.
- End the old circuits only after the new site is accepted, and check the notice period in each contract so you know the cancellation dates.
What fails most often in an office move, and who does what?
The most common failures are late circuits, missing labels, printers and badge readers, forgotten dependencies, and nobody owning acceptance. Most come from a gap between two parties, not from one party's mistake.
Dependencies hide in DNS, certificates, static IP addresses and ISP changes. A new carrier often means new public IP addresses. Check what trusts the old ones: partner allowlists, VPN peers, email sender records and firewall rules. Lower DNS record TTLs ahead of time, because Cloudflare notes that a longer TTL delays when a change reaches users.
Give every task one owner. The table shows a common split.
| Party | Typical responsibility |
|---|---|
| Customer IT | Network design, accounts, DNS, firewall rules, backups, acceptance |
| Facilities or landlord | Building access, lift bookings, closet power and cooling, the carrier entry point |
| Carrier | Circuit delivery, install dates, handover at the demarcation point |
| Mover | Furniture and boxes, moving crates, delivery to the right floor |
| Field engineers | Cabling, staging, rack and connect, testing, floor support |
How should a small office with no IT staff handle a move?
A small office with no IT staff should outsource the technical build and keep the decisions. A partner can do the survey, cabling, staging, connection and testing. Someone inside the company must still own the dates, the accounts and the final acceptance.
Keep the carrier account, the domain and DNS logins, the admin passwords and the asset list in your own hands. Outsource cabling, Wi-Fi, device connection, testing and floor support. Give one person authority to say the office is ready, and write the test list before the weekend.
Key takeaways
- Order circuits first and get a written install date. Never plan around a verbal estimate.
- Build and test the new site before the move, and keep the old one running until acceptance.
- Label everything with one scheme, and test by desk against a written list.
- Check DNS, certificates, static IPs and printers, and name one person to accept the result.