Data Center Move-Day Checklist

What does a move-day checklist cover?

It covers the last week of a relocation and the day after, in nine phases: T-7 days, T-1, the pre-shutdown gate, de-install, transport, install, power-on and physical checks, handoff to your IT team, and T+1. Earlier work, from the T-90 inventory and site survey to the T-30 destination build, belongs in the full data center relocation checklist. By T-7 the move should already be designed; the final week is for rehearsing and confirming, not building.

Each phase ends with a sign-off line on purpose. A phase that nobody signed has not finished, however close it looks, and the next phase should not start on assumption. Tasks are written so that one person can tick them: "check each seal against the custody form" rather than "handle security". If a task on your move has no obvious single owner, that is a planning gap worth fixing before the window opens.

Who owns which tasks on move day?

The owner column uses three parties and keeps the line between them strict. The DataTech crew does physical work: labelling checks, de-cabling, de-racking, packing, sealing, loading, transport, racking, cabling, physical indicator checks and the custody paperwork that goes with it.

Your IT team owns everything that touches systems and data: the shutdown order, graceful shutdown itself, the startup sequence, confirming restorable copies, network reachability, and validation of platforms and applications. The crew can tell you a power supply light is amber or a port has no link; only your IT team can tell you the application works. A system that powers on is not a system that works.

The facility owns the building: power at each rack position, cooling, docks, freight elevators, floor protection and after-hours access. A few tasks, such as the run-of-show rehearsal and the debrief, are shared and say so.

When should the pre-shutdown gate be called?

At a fixed time written on the run of show, before any equipment powers down, with objective criteria checked by name. Before shutdown, rollback costs nothing: you cancel. After shutdown it becomes a power-on, after de-cabling a re-cabling job, and once equipment is on a truck the truck turns around and every step repeats in reverse. The move-day rollback plan works through that stage by stage.

Work out the last safe rollback time backwards from the latest acceptable restoration time, the recovery time objective described in NIST SP 800-34 Rev. 1, and write it in the header of the checklist. If the gate is reached late, the lateness is itself a criterion. One named decision maker calls it, with a deputy, and the call is logged with the time. If any criterion is waived, write down who waived it and why, so the decision can be reviewed after the move.

What happens at handoff to your IT team?

Handoff is the point where physical work is finished and your IT team takes the systems back. Before it, the crew has racked, cabled and powered each device to its labelled feeds, and reported indicator and link-light faults to the command center. At handoff, your IT team validates platforms and applications, application owners sign off, and someone from your side signs acceptance at each final position, which closes the chain of custody record.

The crew lists any open physical items with owners and target times, such as a missing rail or a port that needs re-patching, and clears packing materials from the floor. Release to business use is your IT team's call, not the crew's. A move-day command center keeps that sequence on one log, and the command center guide covers roles, gates and status reporting in detail.