Free Tool
Data center relocation timeline estimator
Rough planning ranges for each phase of a data center move, and the item most likely to set your real move date.
A data center relocation timeline estimate splits a move into discovery, design and planning, procurement, pre-staging, move events and stabilization, then adds up a range for each. The physical move is the shortest phase. Discovery, planning and carrier circuit lead times usually decide whether a target date is achievable.
The ranges are rough planning ranges based on our data center relocation timeline guide, with every assumption listed below. They are not measured industry statistics and will not match any specific project exactly.
Rough total range
20 to 39 weeks
About 4.5 to 9 months from kickoff. Mid-sized (11 to 60 racks).
Critical path item
New carrier circuits
New carrier circuits outlasts design and planning, so it decides when pre-staging can start. Start it as soon as the destination is known.
| Phase | Range | What drives it |
|---|---|---|
| Discovery | 5 to 10 wk | Inventory reconciliation and application dependency mapping. Scaled by 1.25x for fair documentation. |
| Design and planning | 4 to 8 wk | Move method, move groups, outage windows, destination layout, site survey and business approvals. |
| Procurement and lead times | 8 to 16 wk | Runs in parallel with design. Longest item: new carrier circuits. |
| Pre-staging | 2 to 4 wk | Racks installed and powered, network built and tested, circuits turned up, rehearsal of one move group. |
| Move events (3 waves) | 3 to 5 wk | Each wave fits inside a 48-hour outage window. Assumes 1 to 2 weeks between waves to validate before the next. |
| Stabilization | 2 to 4 wk | Post-move validation, hardware replacements and source site decommissioning. |
- Discovery: weeks 0 to 10
- Design and planning: weeks 10 to 18
- Procurement and lead times: weeks 10 to 26 (parallel)
- Pre-staging: weeks 26 to 30
- Move events (3 waves): weeks 30 to 35
- Stabilization: weeks 35 to 39
Check before you commit
- About 10 racks per wave must be shut down, moved, installed, powered on and validated inside 48 hours. Rehearse one move group to confirm the timing before committing to the window.
Worked example with the default inputs
30 racks moving in 3 waves, new carrier circuits needed, minor destination build-out, fair documentation and a 48-hour outage window per wave. That is a mid-sized (11 to 60 racks) environment.
| Phase | Range | What drives it |
|---|---|---|
| Discovery | 5 to 10 wk | Inventory reconciliation and application dependency mapping. Scaled by 1.25x for fair documentation. |
| Design and planning | 4 to 8 wk | Move method, move groups, outage windows, destination layout, site survey and business approvals. |
| Procurement and lead times | 8 to 16 wk | Runs in parallel with design. Longest item: new carrier circuits. |
| Pre-staging | 2 to 4 wk | Racks installed and powered, network built and tested, circuits turned up, rehearsal of one move group. |
| Move events (3 waves) | 3 to 5 wk | Each wave fits inside a 48-hour outage window. Assumes 1 to 2 weeks between waves to validate before the next. |
| Stabilization | 2 to 4 wk | Post-move validation, hardware replacements and source site decommissioning. |
| Total | 20 to 39 wk | About 4.5 to 9 months. Procurement overlaps design, so only the longer of the two counts. |
Critical path item: New carrier circuits. New carrier circuits outlasts design and planning, so it decides when pre-staging can start. Start it as soon as the destination is known. The total sits inside the four to nine months the guide gives for a few dozen racks moving in several waves.
How is this calculated?
The estimator follows the phase order and logic in our timeline guide. Discovery comes first. Design and procurement start together once the destination is known, and pre-staging waits for whichever finishes last. Move waves follow, then stabilization.
The guide describes phase lengths in words: discovery takes "a few weeks" for a small, well-documented environment and "several months" for a large estate with poor records; circuits "commonly" take months; pre-staging takes "several weeks"; stabilization "a few weeks". The week values below are our assumptions that turn those words into numbers, tuned so the totals land inside the guide's overall ranges. Summing the low ends and high ends of every phase gives a wide range on purpose.
| Assumption | Up to 10 racks | 11 to 60 racks | Over 60 racks |
|---|---|---|---|
| Discovery, good documentation | 2 to 4 wk | 4 to 8 wk | 12 to 20 wk |
| Design and planning | 2 to 4 wk | 4 to 8 wk | 8 to 16 wk |
| Equipment, rack and cabling lead times | 2 to 4 wk | 4 to 8 wk | 4 to 8 wk |
| Pre-staging | 1 to 2 wk | 2 to 4 wk | 4 to 8 wk |
| Stabilization | 2 to 3 wk | 2 to 4 wk | 4 to 8 wk |
- Discovery multiplier for documentation: good x1, fair x1.25, poor x1.5.
- New carrier circuits: 8 to 16 wk. Longer where the carrier must build into the building.
- Destination build-out: minor 4 to 8 wk, major 12 to 24 wk, set by contractors and electrical inspections.
- Move events: 1 week for the first wave, plus 1 to 2 weeks for each further wave to validate before the next.
- Procurement time is the longest single item, since items are ordered in parallel.
- The critical path item is the longest of discovery, the longer of design or procurement, and the move waves, compared at range midpoints.
- Decisions are made promptly. Unavailable application owners, late outage-window rejections or a stalled circuit order stretch every range.
What should you do with the result?
Use the estimate to test a target date before committing to it, not as a schedule. Work backward from the date: subtract stabilization, the move waves, pre-staging and the critical-path item. If that puts a circuit order or a build-out contract in the past, the date is already at risk.
Act on the critical-path item first. If it is carrier circuits, order them as soon as the destination is known, even before the design is final. If it is discovery, start reconciling the inventory and mapping application dependencies now, because skipping that work is the most common reason move events get pulled apart and rescheduled.
Then turn the phases into a working plan. Our 90-day relocation checklist breaks the final months into tasks, and the relocation risk register guide shows how to give each schedule risk an owner. When you are ready to plan the physical move, our data center relocation team can work from your timeline.
How long does a data center relocation take?
As rough planning ranges: a handful of racks with good records and no new circuits can often move within two to three months from kickoff, a few dozen racks over multiple waves more commonly takes four to nine months, and large estates with hundreds of racks and new carrier builds routinely run a year or more.
What is usually the critical path in a data center move?
Procurement lead times, carrier circuits above all, most often set the real move date. Where no new circuits are needed, discovery and dependency mapping usually take longest, especially when documentation is poor and many application owners need to be interviewed.
Why is the physical move such a small part of the timeline?
A single move event, covering shutdown, de-installation, packing, transport, installation and power-on, is typically planned inside a weekend or overnight window. Everything around it, from inventory and design to circuit lead times and post-move validation, takes far more calendar time.
How should I use the estimate against a fixed lease date?
Work backward from the date. Subtract stabilization, the move waves, pre-staging and the longest lead-time item. If the circuit order already needed to go in last month, the date is at risk, and it is better to know that before signing anything that depends on it.
Sources and related reading
Planning a move?
Have a date you need to hit?
Share your rack count, waves and target date, and we will plan the physical move around them.