Data center relocation is the physical move of servers, storage, network equipment and racks from one facility to another: site survey, de-installation, packing, transport, re-installation and power-on at the destination. A successful move pairs that physical work with your IT team's shutdown sequencing, data and application cutover, and post-move testing.
Why does a data center relocation need specialized planning?
Because the equipment is interdependent and the cost of getting it wrong is measured in downtime. Unlike moving office equipment, relocating mission-critical infrastructure involves dependencies between servers, storage arrays, network equipment, and the applications they support. A single misstep can cascade into extended downtime, lost data, or compliance violations.
The Ponemon Institute's 2016 study of data center outages put the average cost of downtime at nearly $9,000 per minute for the organizations it surveyed. Whatever the current figure for your business, proper planning is what protects it.
What happens in the pre-move assessment?
The assessment gives you complete visibility into the current environment before a single device moves.
Conducting a Site Survey
A thorough pre-move site survey should document:
- Physical inventory: Every server, switch, storage array, and peripheral device with serial numbers and asset tags
- Power requirements: Current draw, circuit assignments, and UPS dependencies
- Network topology: Physical connections and port maps, plus the VLAN and routing records your network team keeps
- Cooling requirements: Heat output per rack and airflow dependencies
- Cable plant: Structured cabling, fiber runs, and cross-connects
Dependency Mapping
A single database server might support dozens of application servers. Your IT team's dependency map answers the questions that set the move order:
- Which applications depend on which infrastructure components?
- What is the boot sequence for your environment?
- Which systems can tolerate downtime and which cannot?
- Are there regulatory requirements affecting data residency during transit?
Risk Assessment and Mitigation
A formal risk assessment should identify:
- Single points of failure that could extend downtime
- Equipment age and fragility that increases transport risk
- Compliance requirements for chain-of-custody documentation
- Business impact of various failure scenarios
- Rollback procedures if the move encounters problems (NIST SP 800-34 is the federal reference for contingency planning)
Which migration strategy fits: lift-and-shift, phased, or big-bang?
Choose by how much downtime you can absorb and how tightly your applications are coupled to their hardware.
| Strategy | What it is | Works best when | What it requires |
|---|---|---|---|
| Lift-and-shift | Physically relocates existing hardware to the new facility | Equipment is relatively new; applications are tightly coupled to specific hardware; timeline is compressed; the new site can accommodate existing power and cooling | Accurate inventory and a tested power-on sequence |
| Phased | Moves infrastructure in planned waves by application tier or business criticality | You need to validate each wave before the next, keep critical systems running, or refresh hardware along the way | More move events and temporary connectivity between sites |
| Big-bang | Complete cutover in one maintenance window | Systems are too interdependent to split | Extensive pre-planning and rehearsal, an adequate window, tested rollback procedures, and tight coordination across teams |
How is equipment protected in transit?
With climate control, shock protection, and documented custody from dock to dock. Enterprise servers and storage are sensitive to temperature and humidity swings, so professional IT logistics providers use climate-controlled vehicles that maintain:
- Temperature between 50-80°F (10-27°C)
- Humidity below 80% non-condensing
- Vibration dampening for sensitive components
- GPS tracking throughout the route
Those ranges sit in the territory covered by the ASHRAE TC 9.9 thermal guidelines that most facilities design to.
For regulated industries, chain of custody is mandatory. HIPAA's device and media controls, for example, call for a record of hardware movements and the person responsible. That record includes:
- Serial number verification at disconnect
- Tamper-evident seals on equipment and drives
- Photographic documentation at each stage
- Signed handoff documentation between teams
- GPS tracking throughout transport
What does installation at the new facility involve?
Rack-and-stack: placing every device where the floor plan says, powering it correctly, and cabling it to standard. Professional rack-and-stack ensures:
- Correct rack positioning per the floor plan
- Proper power distribution and redundancy
- Cable management following TIA/EIA standards
- Labeling consistency for future maintenance
- Power-on sequencing per dependency maps
What should post-move validation cover?
Two layers, with two owners. The physical layer confirms that every device powers on, every link light is up, labels and port maps match the record, and rack elevations reflect what was installed.
The system layer belongs to your IT team:
- Network connectivity is restored end to end
- Storage volumes mount correctly
- Applications start and function properly
- Monitoring and alerting are operational
- Network latency and throughput, storage IOPS and response times, application response times, and replication performance compare cleanly against pre-move baselines
Finally, update the documentation: network diagrams and IP assignments, rack elevation drawings, cable plant records, CMDB and asset records, and disaster recovery procedures. The guide to post-move validation covers both layers.
What are the most common data center relocation mistakes?
Underestimating the timeline. Moves consistently take longer than planned (see how long a data center relocation takes). Build buffer for undocumented dependencies, equipment issues in transport, configuration problems at the new site, and extended testing.
Insufficient testing. A working ping is not proof of a successful migration. Your IT team should test full application functionality, failover and redundancy, restore procedures, and user acceptance criteria.
Poor communication. Maintain clear channels for executive status updates, technical team coordination, vendor and partner notifications, and end-user communications.
Successful data center relocation requires careful planning, experienced execution, and thorough validation. Whether you're consolidating facilities, moving to a new colocation provider, or repatriating from the cloud, the fundamentals stay the same: plan thoroughly, execute carefully, and validate completely.