Data Center Relocation Gantt Chart: Project Plan Guide
The Problem: Data Center Relocations Have Zero-Tolerance Cutover Windows
A data center relocation is one of the highest-stakes IT infrastructure projects an organization can undertake. The target facility must be ready before the source facility goes dark. Network paths must be provisioned before equipment arrives. Every system must be tested in the new environment before the old one is decommissioned. And all of this must happen with a hard deadline—a lease expiry, a contract end date, or a decommission order that does not move.
The complexity comes from the number of parallel tracks that must converge at the same cutover window: facility preparation, network provisioning, equipment procurement and cabling, application resequencing, carrier circuit provisioning (which has 30–90 day lead times), and staff coordination across multiple teams. Missing any one track delays the whole move.
A data center relocation Gantt chart maps every facility, network, hardware, and application track on a shared timeline with explicit cutover dependencies. gantt-chart.io lets IT project managers and data center managers build this without specialized tooling, free, no sign-up required.
Prerequisites
Before building your data center relocation timeline:
- Source facility end date: Lease expiry or decommission date (the hard deadline)
- Target facility: Colocation contract signed, or build-out underway
- Equipment inventory: Servers, network gear, storage, power requirements
- Application inventory: Criticality tiers, dependencies, downtime tolerance
- Carrier circuit requirements: Bandwidth, redundancy, current provider contracts
Phase 1: Planning and Assessment (Months 1–3)
| Task | Duration | Notes |
|---|---|---|
| Equipment inventory and asset tagging | 2–4 weeks | — |
| Application dependency mapping | 2–4 weeks | — |
| Criticality tiering (business impact analysis) | 1–2 weeks | — |
| Target facility selection and contract | 2–8 weeks | If not selected |
| Power and cooling requirements analysis | 1–2 weeks | — |
| Network architecture design (target) | 2–3 weeks | — |
| Move sequence and wave planning | 1–2 weeks | Based on dependencies |
Application dependency mapping is consistently the most time-consuming and under-resourced task. Application teams often don't document their dependencies until forced to.
Phase 2: Target Facility Preparation (Months 2–5)
| Task | Duration | Depends On |
|---|---|---|
| Rack and cage provisioning | 2–4 weeks | Contract signed |
| Power circuit installation | 2–4 weeks | Facility plan |
| In-row cooling deployment | 2–3 weeks | Power complete |
| Structured cabling installation | 2–4 weeks | Rack layout final |
| Cross-connect ordering (within facility) | 2–4 weeks | Layout final |
| Out-of-band management network setup | 1–2 weeks | Cabling complete |
| Facility security and access provisioning | 1–2 weeks | — |
| Environmental monitoring setup | 1 week | — |
Structured cabling is on the critical path. A cabling vendor with a 4-week lead time in a high-demand colocation can push your entire timeline.
Phase 3: Network Circuit Provisioning (Months 2–5, Long Lead)
| Task | Lead Time | Start By |
|---|---|---|
| Carrier circuit order (Internet, MPLS, DWDM) | 30–90 days | Month 2 |
| Dark fiber provisioning (if applicable) | 60–120 days | Month 1 |
| BGP configuration and IP address planning | 2–4 weeks | Month 3 |
| DNS TTL reduction (pre-cutover) | Start 2 weeks pre-cutover | — |
| Cross-connect installation | 1–2 weeks | Circuits delivered |
Carrier circuit lead times are the longest dependency in most data center moves. Order circuits on day one of the project.
Phase 4: Equipment Procurement and Staging (Months 3–5)
| Task | Duration | Depends On |
|---|---|---|
| New hardware procurement (if refreshing) | 4–12 weeks | Budget approved |
| Hardware delivery to target facility | Per procurement | — |
| Rack and stack at target | 1–3 weeks | Hardware delivered, racks ready |
| OS installation and baseline configuration | 1–2 weeks | Rack and stack |
| Application installation and configuration | 2–4 weeks | OS ready |
| Integration and connectivity testing | 1–2 weeks | Applications installed |
If you're refreshing hardware during the move, order it in month 2. Hardware lead times have extended to 12–16 weeks for some server configurations.
Phase 5: Migration Waves (Months 4–7)
Organize equipment moves in waves, starting with the least critical:
| Wave | Tier | Downtime Tolerance | Approach |
|---|---|---|---|
| Wave 1 | Dev/Test | High | Cold move, extended window |
| Wave 2 | Non-critical Prod | Medium | Scheduled maintenance window |
| Wave 3 | Business-critical | Low | Hot migration or short window |
| Wave 4 | Mission-critical | Near-zero | Parallel run and cutover |
Per-wave tasks: pre-move testing, physical transport (if moving equipment), rack and stack at target, cabling, power-on, OS and app validation, connectivity test, sign-off.
Phase 6: Cutover and Decommission (Months 6–8)
| Task | Duration | Depends On |
|---|---|---|
| Final DNS cutover | Per cutover window | All systems validated |
| BGP route advertisement at new facility | 1–4 hours | Network ready |
| Source facility power-down sequence | Per wave | Cutover complete |
| Data destruction and certificate of destruction | 2–4 weeks | Equipment decommissioned |
| Facility clean-out and handback | 1–2 weeks | Equipment removed |
| Post-move performance monitoring | 4–6 weeks | Go-live |
| Project close-out and documentation | 1–2 weeks | Stable operations |
Build Your Data Center Relocation Timeline
Open gantt-chart.io, map your facility, network, and migration wave tracks against your lease expiry date, and share with your project team. Free, no account required.