A colocation migration is the move of your servers, storage and network equipment from an on-premises data center into rented space, power and cooling in a third-party facility. You keep owning and operating the hardware; the provider supplies the building. Planning covers facility selection, power and connectivity readiness, the physical move in waves, and validation.
Why do organizations move to colocation?
Mostly to stop running a building while keeping control of your own hardware.
- Reduced CapEx: Colocation eliminates the need to build and maintain physical data center infrastructure
- Improved reliability: Purpose-built facilities offer redundant power, cooling, and connectivity
- Scalability: Capacity can grow without constructing new facilities
- Carrier-neutral connectivity: Access to multiple carriers and cloud on-ramps in one building
- Geographic flexibility: Strategic facility locations can reduce latency and improve disaster recovery posture
The trade is that you now work inside someone else's rules. Access lists, dock schedules, and floor policies all become part of your move plan, which is where many first colocation moves lose time.
What should you assess before moving?
Everything you own, measured rather than assumed. A colocation contract prices space and power, so the current-state analysis is also the basis of the commercial negotiation.
- Complete hardware inventory including servers, storage, networking, and supporting equipment
- Power consumption measured at the device and rack level, not taken from nameplate ratings
- Cooling requirements and airflow dependencies
- Network architecture documentation including IP addressing, VLANs, and routing tables (your network team's records)
- Application dependencies and data flow mapping (your IT team's work; see mapping application dependencies)
Measured power matters most. Contracting from nameplate figures overbuys power you will pay for every month; contracting from guesses can leave racks without the headroom they need. Rack weights matter too, because a colocation hall has its own floor loading limits.
How do you choose a colocation facility?
Match the facility to your measured requirements, then check how it operates, not just what it advertises.
| Criterion | What to ask |
|---|---|
| Power density and cooling | Can each cabinet position deliver your measured load plus growth, on A and B feeds? |
| Connectivity | Which carriers and cloud on-ramps are in the building, and what do cross-connects cost and take to provision? |
| Physical security | How are access lists, visitor escorts, and cage keys handled? |
| Compliance | Will the provider share its SOC 2 report and other attestations for your auditors? |
| Location | How far is the facility from users and from your disaster recovery site? |
| Contract | How flexible are terms for scaling up, scaling down, or exiting? |
| Move-in logistics | What are the dock hours, elevator limits, and floor rules? |
How long does a colocation migration take?
Typically several months from contract to decommissioning the old room. Key milestones include:
- Contract finalization and space provisioning
- Network connectivity installation and testing, including carrier circuits, which often carry the longest lead times
- Initial equipment deployment, with configuration by your IT team
- Pilot system migration and validation
- Production workload migration waves
- Legacy facility decommissioning
Order carrier circuits and cross-connects early. They are outside both your control and the move crew's, and a late circuit can idle every other workstream. For realistic ranges, see how long a data center relocation takes.
Should you migrate to colocation in phases?
For most organizations, yes. A phased migration moves equipment in waves rather than all at once, which allows:
- Validation of the process with non-critical systems first
- Identification and resolution of issues before moving production workloads
- Business continuity throughout the transition
- Tuning of the target environment based on lessons from earlier waves
A single-weekend move can still make sense for small, tightly coupled environments, but it needs a rehearsed plan and a tested rollback. The trade-offs are covered in lift-and-shift, cold, and phased migration approaches.
What colocation rules affect move day?
More than most teams expect. Colocation facilities run shared buildings, and your move has to fit their operating rules:
- Dock and elevator bookings: Reserve loading dock time and freight elevator access for each wave, and confirm elevator capacity against your heaviest loaded rack
- Access lists: Every person on the move crew usually has to be named in advance, with identification checked on arrival
- Certificates of insurance: Most facilities require them from every vendor before access is granted (see certificates of insurance for data center moves)
- Packaging rules: Many facilities prohibit cardboard and other packaging on the data hall floor, consistent with the limits on combustible materials in NFPA 75, so equipment is unpacked in a staging area
- Working hours and escorts: Some facilities restrict work to set hours or require facility staff to escort crews in the hall
Confirm each rule in writing during planning. Discovering any of them on move night costs the window.
How is equipment prepared and transported?
Your IT team protects the data; the move crew protects the hardware.
Before de-installation
- Your IT team makes a current copy of all data and verifies it can be restored
- Document rack positions, cable connections, and port maps
- Remove or secure loose components
- Apply asset tags and tracking labels
In transit
- Climate-controlled vehicles to protect sensitive electronics
- Air-ride suspension to minimize vibration damage
- GPS tracking for the full route
- Adequate insurance coverage based on replacement value
This physical work is the core of a colocation migration service.
What happens at installation and after?
Once equipment arrives at the colocation facility, the crew installs it and your IT team proves it works.
Installation
- Verify equipment condition against pre-move documentation
- Install equipment according to the planned rack layout
- Reconnect cabling following documented port maps
- Power up systems in the correct sequence
- Confirm power-on and link lights before handing over
Validation by your IT team, after each wave
- Network connectivity and performance verification
- Application functionality testing
- Monitoring system integration
- Restore validation
Documentation updates
- Update asset records with new locations
- Revise network diagrams and IP documentation
- Adjust disaster recovery procedures
- Update vendor contact information and escalation paths
What are the most common colocation migration pitfalls?
- Underestimating power requirements: Make sure the contract provides adequate power headroom at measured, not nameplate, load
- Neglecting network latency: Your IT team should test connectivity before moving latency-sensitive applications
- Late carrier circuits: Order them first, because they gate everything else
- Ignoring facility rules: Access lists, dock bookings, and packaging rules set the pace of move day
- Insufficient testing time: Build adequate validation windows into each wave
- Poor communication: Keep stakeholders informed throughout the migration
A well-planned colocation migration moves your infrastructure into a better building with little disruption to the business. Success depends on thorough preparation, careful execution, and attention to detail at every stage.