A data center relocation typically takes two to three months for a handful of racks, four to nine months for a few dozen racks, and a year or more for large enterprise estates. The physical move is the shortest phase. Discovery, planning, and circuit lead times decide whether a lease or contract date is achievable.
Most schedules that slip do so for reasons visible on day one: an inventory nobody trusts, a circuit nobody ordered, a dependency nobody mapped. Understanding the phases and what stretches each one is the only reliable way to test a target date before committing to it.
Why Does Discovery Take So Long?
Every relocation starts with an inventory, and most inventories are wrong. Devices appear that nobody can explain. Records describe servers decommissioned two years ago. Applications turn out to depend on a box in a corner rack that was never documented.
Discovery reconciles the physical estate against the records, identifies owners for every system, and establishes how applications talk to each other. The last part takes longest, because it depends on interviewing people who are busy with other work. Mapping application dependencies properly is what allows move groups to be built later, and skipping it is the most common reason move events get pulled apart and rescheduled.
For a small environment with good records, discovery can take a few weeks. For a large estate with poor documentation and many application owners, it can take several months on its own.
Design and Planning
With a trusted inventory, the move itself can be designed. That means deciding the method (forklift, phased, or replicate-and-cut-over), grouping systems into move events, defining outage windows with the business, and laying out the destination: rack elevations, power distribution, cooling capacity against the ASHRAE thermal guidelines, network topology.
The destination needs its own inspection. A pre-move site survey covers loading docks, freight elevators, floor loading, power availability, and the route from truck to rack. Findings here can change the plan significantly. A floor that cannot carry fully loaded racks means de-populating them, which changes crew size, packaging, and duration.
Planning also includes business approvals. Outage windows need sign-off from application owners, and change freezes need to be negotiated around quarter-end, audits, and peak trading periods. Those conversations take calendar time regardless of how fast the technical work moves.
Which Lead Times Set the Real Move Date?
Procurement lead times, carrier circuits above all, most often set the real move date. This phase runs in parallel with design rather than after it.
Carrier circuits are the usual constraint. Provisioning a new circuit to a destination facility commonly takes months, and longer where the carrier has to build into the building or obtain permits. Circuits should be ordered as soon as the destination is known, even before the design is final.
New network equipment, racks, PDUs, and cabling have their own lead times, which vary with market conditions and can shift during a project. Where the move includes a hardware refresh, the new equipment has to arrive, be received, tagged, and burned in before anything can migrate onto it.
Destination build-out adds more. If the colocation cage needs power circuits installed, or the new room needs cooling work, those contractors work to their own schedules and to electrical inspections under the National Electrical Code (NFPA 70).
Pre-Staging
Pre-staging is everything that can be done before the outage window so the window contains only what must happen during it. Racks are installed and powered. Network cores are built, configured, and tested. Cabling is run and labeled. Circuits are turned up and verified end to end.
Where possible, crews rehearse. A dry run of a single move group, or a walk-through of the path from dock to rack, exposes timing assumptions that look fine on paper. This phase typically takes several weeks and compresses badly when procurement runs late.
How Long Does the Physical Move Take?
The physical moves are usually the shortest part of the project. A single move event, covering shutdown, de-installation, packing, transport, installation, and power-on, is typically planned inside a weekend or overnight window.
Larger environments rarely move in one event. They move in waves over weeks or months, with each wave sized to what the team can move, bring up, and validate inside one outage window. The number of waves is driven by dependency groups and business tolerance for outages more than by equipment count.
Stabilization
After the last truck, the project is not finished. Each move group needs post-move validation against a test plan agreed before the move. Hardware that failed on power-up needs replacing. Your IT team needs to update monitoring, data-protection schedules, and support contracts to reflect the new location. The source site needs decommissioning and returning to the landlord in the condition the lease requires.
A stabilization period of a few weeks after the final move event is common, and longer where the source site has significant decommissioning work.
What Are Realistic Timelines by Environment Size?
With every caveat above, some rough ranges hold for planning purposes. A small environment of a handful of racks, with good records and no new circuits required, can often move within two to three months from kickoff. A mid-sized environment of a few dozen racks with multiple move waves more commonly takes four to nine months. Large enterprise moves with hundreds of racks, new carrier builds, and many application owners routinely run a year or more.
These ranges assume the organization can make decisions promptly. They stretch when application owners are unavailable, when the destination is not ready, when a circuit order stalls, or when the business rejects proposed outage windows late in planning.
The practical test for any target date is to work backward from it. Subtract stabilization, the move waves, pre-staging, and the longest lead-time item. If the circuit order has to go in last month, the date is already at risk, and it is better to know that before signing anything that depends on it. Teams planning a data center relocation against a fixed lease date should start that calculation at the first meeting, not after discovery.