Knowing what to know before moving into a colocation facility starts with understanding how power, connectivity, equipment logistics, and migration planning will affect your operations. Before scheduling a move, IT and facilities leaders need to confirm that the destination can support their infrastructure and that every part of the transition has a clear owner.
A successful colocation migration requires more than transporting servers and connecting cables. The work begins with validating facility requirements, documenting application dependencies, and establishing a cutover plan that protects business operations.
Confirm the Facility Can Support Your Equipment
A cabinet with enough available rack units does not necessarily have the capacity your deployment needs. Power availability, cooling limits, equipment depth, and weight restrictions can determine whether your planned configuration will work.
Request a technical review of your equipment list and proposed rack layout before committing to an installation date.
Check Rack Dimensions and Physical Access
Document each device’s dimensions, weight, mounting requirements, and airflow direction. Include switches, storage systems, patch panels, power distribution units, and cable management hardware in your rack elevation.
Verify these details with the facility:
- Cabinet width, depth, and usable mounting space.
- Rail compatibility and clearance for power cords.
- Cabinet and floor load limits.
- Loading dock, doorway, and freight elevator dimensions.
- Access to lifts and other equipment-handling tools.
- Space for technicians to service installed hardware.
If you plan to transport populated racks, confirm that the cabinets and equipment are approved for that transport method. Do not assume an installed configuration can safely travel intact.
Validate Cooling and Airflow Requirements
Ask the provider to approve the expected heat load per rack and explain its containment requirements. Check airflow direction on network equipment carefully, particularly when switches mount at the rear of a cabinet.
Provider installation rules can affect your materials list. For example, Equinix’s customer installation guidelines address equipment airflow orientation, blanking panels, and cable placement that avoids obstructing ventilation. Obtain the equivalent requirements for your destination before finalizing the rack design.
Size Power for Normal Operations and Failover
Power planning should account for measured consumption, expected peak demand, and planned additions. Manufacturer specifications help establish equipment requirements, but measured operating data provides useful context for sizing the deployment.
Confirm the facility’s usable circuit capacity, voltage, receptacle types, and approved rack power distribution units. Ask the provider to validate the design against its electrical and operating requirements.
Verify the A and B Power Design
For equipment with redundant power supplies, map each connection to its intended A or B feed. Two power cords do not establish independent power paths if both ultimately connect to the same source.
The surviving feed must support the intended load when the other feed becomes unavailable. Validate capacity at the circuit, PDU, outlet-bank, and equipment levels rather than relying on a cabinet-level total.
Identify single-corded devices separately. Discuss approved transfer equipment or other availability measures with the provider before installation.
Understand Power Billing
Ask whether charges reflect reserved capacity, metered consumption, or another arrangement. Clarify how redundant feeds are priced, how overages work, and what additional capacity will cost.
Also verify whether expansion requires new circuits, different PDUs, or a cabinet relocation. Available rack space has limited value when usable power is already exhausted.
Order Connectivity Before Scheduling the Cutover
Treat carrier circuits and cross-connects as prerequisites for the move. Establish separate milestones for ordering, installation, activation, and testing.
Confirm the exact handoff location and identify who handles each connection between the carrier, facility, and your equipment. A completed carrier order does not necessarily mean your server rack has a tested connection.
Document Every Network Handoff
Your connectivity plan should specify:
- Carrier services, bandwidth commitments, and circuit identifiers.
- Cross-connect endpoints and required authorization documents.
- Fiber type, connector type, optics, and patching responsibilities.
- IP addressing, routing, firewall, and VPN changes.
- DNS updates and external IP allowlist dependencies.
- Acceptance tests and escalation contacts.
When redundant connectivity is required, request confirmation of physical path diversity. Separate service contracts alone do not demonstrate separate building entrances or cable routes.
Test connectivity before transporting production equipment whenever possible. Temporary equipment at the destination can help verify routing and access while the existing environment remains operational.
Review Costs, Service Commitments, and Responsibilities
Evaluate the complete operating cost of the colocation deployment. Cabinet pricing alone will not capture installation work, connectivity, on-site support, and migration expenses.
Request an itemized estimate covering initial setup and recurring charges.
Account for Costs Beyond Rack Space
Budget discussions should include:
- Power provisioning and ongoing power charges.
- Carrier installation and cross-connect fees.
- Remote hands and smart hands minimum charges.
- After-hours work and emergency support.
- Freight receiving, storage, and unpacking.
- Cabling, optics, rack hardware, and spare parts.
- Overlapping services during the migration.
- Equipment removal and restoration of vacated space.
Ask what is included in the service-level agreement and how incidents are measured and escalated. Have procurement and legal teams review the actual commitments, exclusions, and remedies.
Assign Ownership Before Work Begins
Create a responsibility matrix covering the provider, carriers, internal IT, facilities staff, movers, and deployment technicians.
Name an owner for each task, including rack installation, cross-connect ordering, cable testing, device configuration, application validation, and final acceptance. Shared involvement should still lead to one accountable owner.
Build the Migration Plan Around Application Dependencies
Moving equipment in a convenient physical order can create an inconvenient business outage. Plan the shutdown and restoration sequence around the services each application needs.
Identify dependencies such as authentication, DNS, storage, databases, licensing, backup infrastructure, and external integrations. Include systems that teams rarely touch but still depend on.
Create an Executable Cutover Runbook
A useful data center migration runbook gives technicians enough detail to act without improvising.
Include the following:
- Equipment shutdown and startup sequences.
- Source and destination rack positions.
- Port-to-port cable maps and power connections.
- Named task owners and escalation contacts.
- Expected task durations and decision checkpoints.
- Application validation steps.
- Stop conditions and recovery procedures.
Distinguish infrastructure checks from business acceptance. A server responding to a ping does not prove that employees can authenticate, applications can process transactions, or integrations are working.
Make the Recovery Plan Practical
Verify backups and test restoration before the move. Protect configuration exports and ensure recovery documentation remains accessible while production systems are offline.
A physical relocation can make rollback difficult once equipment leaves the original site. Decide whether recovery means restoring at the destination, using standby infrastructure, or returning hardware to the source.
Set the decision deadline accordingly. A plan that requires several hours of transportation cannot support a recovery window measured in minutes.
Coordinate Delivery, Access, and Equipment Handling
Confirm receiving procedures before booking transportation. Facilities may require delivery appointments, approved contractor lists, shipment references, or specific unloading arrangements.
Check when technicians can enter the site and whether access arrangements cover the full maintenance window.
Prepare Equipment for a Traceable Move
Record serial numbers, asset identifiers, rack positions, and condition before packing. Photograph existing connections where permitted and label both ends of every cable that will be reused.
Use packaging and handling methods appropriate for the equipment. Assign custody at pickup, arrival, unpacking, and installation so missing or damaged items can be identified promptly.
Keep rails, brackets, power cords, and installation accessories linked to their devices. A missing mounting kit can delay an otherwise ready deployment.
Finalize Rack Installation and Cabling Standards
Approve rack elevations and cable schedules before technicians arrive. Specify device positions, power assignments, cable lengths, labeling conventions, and patch-panel locations.
A documented rack and stack plan helps the installation team work efficiently and gives remote engineers a reliable reference during troubleshooting.
Leave the Installation Serviceable
Route cables so technicians can replace equipment without disturbing unrelated connections. Respect manufacturer requirements for bend radius, cable support, and access clearance.
Inspect and test cabling before accepting the installation. Record results against the relevant ports or cable identifiers, and update the drawings when field conditions require an approved change.
Arrange On-Site Support and Monitoring Before Handover
Confirm who will physically respond after the migration team leaves. Remote hands and smart hands service descriptions vary, so establish the tasks, skills, access permissions, and response expectations you actually need.
Specify whether support includes visual inspections, cable tracing, hardware replacement, console access, or assistance with troubleshooting. Provide clear authorization procedures for disruptive actions such as power cycling.
Prepare secure out-of-band management access and test it before handover. Where practical, make sure it remains usable when the primary production connection fails.
Connect the relocated environment to your monitoring systems or NOC monitoring service. Test alert delivery, escalation contacts, and coverage for power, temperature, network interfaces, hardware health, and critical applications.
Use a Readiness Review to Authorize the Move
Hold a final go/no-go review with IT, facilities, business owners, and deployment partners. Base the decision on completed checks and documented exceptions.
Before releasing equipment for transport, confirm that:
- Destination racks, power, cooling, and access are ready.
- Required connectivity has passed testing.
- Backups and recovery procedures have been verified.
- Technicians, transportation, and support contacts are scheduled.
- Installation materials and approved documentation are available.
- Business owners understand the outage window.
- Acceptance criteria and escalation authority are agreed upon.
Keep the original environment available for the planned overlap period. Decommission remaining infrastructure only after acceptance and after confirming that no production dependencies remain.
Moving into a colocation facility becomes more manageable when requirements are verified before move day and every handoff is documented. Careful preparation helps protect uptime, control installation costs, and give your team a supportable environment from the start.
DeployNation provides nationwide IT deployment and field services, including rack and stack, remote hands and smart hands, structured cabling, NOC monitoring, and IT relocation and decommissioning. Bring your destination requirements, equipment inventory, and target migration window to the planning discussion so the on-site work can align with your technical and business priorities.