Project Planning and Management

What does project planning cover in a data center move?

Project planning covers everything that has to be decided before the first device is unplugged. Physical infrastructure projects fail most often not because of a dropped server, but because of a missed dependency, an uncoordinated vendor, or a change window that did not account for upstream impacts. That is why we treat planning as a first-class discipline, not an afterthought bolted onto the physical work. Every engagement begins with structured discovery: site surveys, stakeholder interviews, asset inventories, dependency information gathered from your application owners, and risk assessments. From there we build a project plan with a work breakdown structure, resource allocations and contingency windows, and keep a Gantt-chart schedule current for every stakeholder. Our project managers are experienced infrastructure professionals who speak the language of both the loading dock and the NOC. See data center migration planning and strategy for how a plan is built from concept to move day.

What should a pre-move site survey document?

A pre-move site survey documents every physical condition that could stop equipment getting from its current rack to its new one. At both origin and destination, that means loading docks and truck access, freight elevator size and weight limits, door widths, floor loading, and the full route from dock to rack. Inside the room, it means rack positions, power circuits and receptacle types, cooling capacity, cable pathways, and fire protection. The ASHRAE TC 9.9 guidelines frame the temperature and humidity questions, and NFPA 75, the fire protection standard for IT equipment rooms, frames the questions for the facilities team. Findings change the plan: a floor that cannot carry fully loaded racks means de-populating them, which changes crew size, packaging and duration. See site surveys and pre-move assessments and our pre-move site survey checklist.

What is a migration workbook and why does it matter?

A migration workbook is the single record of what is moving, where it is now, where it is going, and when. Each row is a physical asset: hostname, make, model, serial number and asset tag, source rack and position, destination rack and position, move group, crate or cart ID, and the port map for its cabling. The workbook drives labeling, packing lists, truck manifests and the chain-of-custody record, so a discrepancy found in planning is a discrepancy fixed before move day. Columns your IT team owns sit alongside ours: application owner, shutdown and startup order, and the tests that prove each system works afterwards. Keeping one shared document, rather than a spreadsheet per team, is what stops the night-of question “which rack does this go in?” from becoming a delay. See migration workbook and runbook development and our article on the migration workbook as a single source of truth.

Who does what during planning and move day?

DataTech plans and runs the physical work. Your IT team plans and runs the systems. We build the schedule for surveys, packing, transport and installation, and we coordinate with your teams, colocation providers, OEM field engineers, network carriers and facilities management so that physical work is sequenced correctly. Your engineers decide what shuts down when, move any data, and confirm that each application is back.

DataTech Logistics project team	Your IT team
Site surveys and physical risk register	Application dependencies and move-group sign-off
Asset inventory and workbook physical columns	Shutdown and startup order
Crew, truck, crate and escort scheduling	Data copies, replication and cutover
Physical-work details for change requests	Change advisory board approval
Carrier and colocation access coordination	Carrier circuit orders and turn-up tests
Move-day command of physical work	Go/no-go on each system
Physical validation and as-built records	Application testing and acceptance

How is move day run?

Move day runs from a command center that tracks every task against the workbook and makes decisions fast. One bridge, staffed by our project manager and your IT lead, follows each move group through shutdown confirmation, de-installation, packing, loading, transport, installation and power-on. Crews report milestones, and anything late or wrong is escalated against agreed thresholds, not debated. Change advisory board submissions, maintenance window requests and carrier cross-connect orders are prepared in the weeks before as integrated workstreams, so the night itself carries no paperwork surprises. Every move group has an agreed point at which your team decides to proceed or roll back, and the physical plan includes what it would take to return equipment to its original racks. Stakeholders get scheduled status updates instead of ad hoc calls. See move-day command center operations for how the bridge is staffed and what it tracks.

What happens after the move?

After the move, two kinds of validation run side by side, then the project closes out. Physical validation is ours: every device is powered on, link lights are checked, labels and port maps are verified against the workbook, and racks are photographed front and rear. Application validation is your IT team’s: services start, data is reachable, monitoring reports normal, and owners sign off against a test plan agreed before the move. Hardware that fails to power up is logged and replaced through your OEM or spares. Closeout includes a lessons-learned review, a final documentation package with as-built rack elevations and cable schedules, and reconciliation of the physical inventory against your CMDB so records match reality at the new site. See post-move validation and stabilization and our guide to post-move validation that proves it works.