Moving the server room and network closet in an office relocation means de-installing and transporting servers and switches, building out a new closet with power, cooling, and cabling, and having carrier circuits live before staff arrive. It is small in square footage but carries most of the move's risk, on lead times unrelated to the furniture schedule.
Office relocations are usually planned around furniture, floor plans, and lease dates, with the server room often assigned to the same general mover handling desks and filing cabinets. That works until Monday morning, when two hundred people sit down at new desks and nothing connects.
Can a General Mover Handle the Server Room?
Usually not on its own. General commercial movers are good at what they do: furniture, crates of files, office equipment, and tight building schedules. Most are not set up to handle rack-mounted servers, switches, storage, and the cabling and documentation that go with them.
The difference shows up in specific places. Servers should be de-installed from their racks and packed in proper cases rather than moved loaded on rails. Rack-mounted equipment needs labeling that maps every device to its destination position. Drives and other data-bearing equipment need custody documentation from the moment they leave the room until they are installed at the new site. Racks need to be re-assembled, leveled, and anchored where required.
A common approach is to split the work. The general mover handles furniture and general office contents, and an IT equipment specialist handles server relocation, network equipment, and the closet build-out. Both work to one schedule owned by the project lead.
Why Order Carrier Circuits First?
Because internet and telecom service at the new address is the longest lead item in most office moves. Fiber circuits, especially to a building where the carrier has no existing presence, can take weeks or months to deliver. Construction, permits, and building access for the carrier all extend the timeline.
Order circuits as soon as the lease is signed. Confirm where each carrier will place its demarcation point in the new building and how service will get from there to your closet. In multi-tenant buildings, that path often runs through a shared building telecom room, and the landlord may control access to it.
Plan for overlap. Keeping the old circuits active for a period after the move gives your IT team a fallback if the new service is late or has problems. The cost of a month of overlapping service is small next to a week of an office without connectivity.
What Does the New Network Closet Need?
The network closet at the new office should be ready before any equipment arrives. That means the room itself, not just a space on the floor plan.
Check it against the basics. ANSI/TIA-569 covers telecommunications pathways and spaces and is a useful reference for size, location, and access, and BICSI's installation standards cover the same spaces from the cabling side. In practical terms, the closet needs:
- Dedicated electrical circuits sized for the equipment, with the correct receptacles, installed to the National Electrical Code (NFPA 70)
- Cooling that can handle the heat load with the door closed
- A lockable door and controlled access
- Grounding and bonding for the racks and cable tray
- Pathways for horizontal cabling to every work area
Install racks, cable management, and patch panels before move day. Horizontal cabling to desks should be installed, terminated, labeled, and tested well ahead of time. A closet that is still under construction when the servers arrive forces equipment to sit in a hallway. The planning steps for telecom MDF and IDF relocation apply to an office closet at a smaller scale, and the detail in MDF and IDF relocation planning is a good checklist even for a single room.
In What Order Should Furniture and IT Move?
Cabling and closet work first, furniture second, servers and network third, desktops last. The order matters as much as the work itself.
Cabling and closet work go in first, while the space is empty and installers have clear access to ceilings and walls. Furniture comes next, so desks and cubicles are in place before network drops are connected to workstations. Server and network equipment moves after the closet is ready, usually over a weekend or other low-use window. User desktops, monitors, and peripherals come last.
Running these in the wrong order creates rework. Furniture installed before cabling forces cable installers to work around desks. Equipment moved into an unfinished closet gets dusty and is handled twice. Desktops delivered before the network is live sit unused and invite helpful staff to start plugging things in.
Your IT team owns the system side of the cutover: shutting down services at the old office, bringing them up at the new one, and confirming that applications, phones, and printers work. Agree on a timeline that gives the team time between the arrival of the closet equipment and the arrival of users. Communicate the plan to staff ahead of time, including when services will be unavailable, using the approach in communicating a planned outage.
Desktops Last
User workstations are the most numerous items in the move and the least complicated individually. They are also the ones users notice first.
Label every workstation, monitor, and dock with the user's name and destination desk before it is packed. Pack cables and peripherals with the equipment they belong to, in labeled bags. At the new office, place each set at its labeled desk and connect power and network as specified. Leave the login and testing to the user and the help desk.
Plan a walk-through on the first morning. Have IT staff on the floor, not just on the phone, to handle the predictable problems: a dock that needs a different cable, a desk drop that was not patched, a monitor that arrived at the wrong desk. Most of these take minutes when someone is standing there.
Close out the old space after the new one is confirmed working. Walk the old server room and closet one last time for equipment, cabling, and anything left in a rack, and record where every device ended up.