Your office can move over a weekend. Your server rack has to be running by Monday morning, when everyone logs in.
In most office moves, the server room is the smallest space and carries the most risk. A file server, firewall, or phone system that won’t come back online stops work for everyone. According to the Uptime Institute’s 2025 outage analysis, most outages caused by human error trace back to procedures that were skipped or flawed. A relocation is one long procedure, so the plan matters.
Here’s how to manage a server rack relocation during an office IT move.
Map everything before you unplug anything
Start weeks ahead, with a complete picture of what’s in the rack.
- Inventory every device. List each server, switch, firewall, storage unit, and UPS with its serial number and rack position.
- Map dependencies. Note which systems need others running first. Your phone system may depend on a switch that depends on the firewall.
- Draw rack diagrams for both locations. Show where each device sits now and where it will go.
- Label and photograph every cable. Tag both ends, then photograph the back of the rack before disconnecting anything.
- Check the new room early. Confirm power circuits, cooling, rack space, and floor access well ahead of move week.
Tip: Order your new internet circuit as soon as you sign the lease. Installs can take weeks.
Protect your data and your uptime
A drive can fail on a bumpy ride, so back up everything before shutdown.
Confirm every backup actually restores. CISA recommends the 3-2-1 rule: three copies of important files, on two types of storage, with one copy kept off-site.
For true zero-downtime needs, keep key services running somewhere else during the move:
- Fail over temporarily. Keep critical services running elsewhere during the move by shifting email, files, or key apps to the cloud for the move window.
- Move in phases. If you have redundant equipment, move one set first, bring it online, then move the rest.
- Move off-hours. Shut down Friday evening and use the weekend to install and test.
Tip: Write a rollback plan. Decide in advance what happens if a critical system won’t start at the new site, and who makes that call.
Move day: shut down, pack, and transport
Shut down in order. Use your dependency map in reverse: Shut down your applications first, then move on to servers and storage, and finally, network gear and power.
Decide whether to de-rack. Shipping a rack fully loaded sounds faster, and sometimes it is. But it only works if the rack is rated for transport and rides on a shock-absorbing pallet. Most office racks aren’t built for that, so each server, switch, and storage unit usually comes out and gets packed on its own.
Pack for shock and static. Use anti-static wrap, padded cases or crates, and an air-ride truck that softens road vibration. Keep a sign-off record of who handled each device and when.
Give it time to warm up. Cold equipment can collect condensation indoors. IBM’s hardware guidance calls for letting packaged equipment acclimate for up to 24 hours before powering on, unless the product’s own instructions say otherwise. Plan for it in winter.
Tip: Send servers with a trained IT moving team rather than a general furniture crew. JK’s office IT relocation services use A+ certified technicians and custom packing for server and network equipment.
After the move: Bringing it all back online
This is where all the labeling pays off. Re-rack each device according to your new rack diagram. Next, reconnect the cables, using your labels and photos.
Power up in the reverse of your shutdown order: power and network first, then storage, servers, and applications.
Before anyone logs in, test everything – internet, firewall, wireless, then every critical app, shared drive, printer, and phone line. It’s far easier to fix a mapped drive on Sunday afternoon than at 9 a.m. Monday.
Your server rack relocation checklist
8-12 weeks out
Order your internet service for the new office first, since it can take the longest. Then take inventory of the rack, map which systems depend on each other, and draw rack diagrams for both locations. Visit the new server room to confirm the power, cooling, and space.
2-4 weeks out
Back up your data and test that it restores. Write your rollback plan, and set up any cloud failover you’ll need during the move.
Move day
Run one last backup. Photograph and label every cable, shut down in order, and de-rack. Pack each device in anti-static wrap, and log every handoff.
After the move
Give cold equipment time to acclimate. Re-rack, power up in order, and test everything before your team logs in.
For everything else, see our office moving checklist.
When to bring in professionals
If your rack runs systems your business can’t work without, plan with an IT relocation team from the start. Look for experienced office and commercial movers who will assign one project manager to the whole move, so IT and furniture run on one schedule.
Summary
A server rack relocation succeeds or fails on its planning. Put time early into inventory, backups, and testing, and have your team walk in on Monday and log in like any other workday.