Colocation Migration Checklist: How to Move Your Servers to a Data Center

Planning Your Colocation Migration

Moving servers to a colocation facility is a major project. Use this checklist for a smooth migration with minimal downtime.

Phase 1: Pre-Migration Planning (4-8 Weeks Before)

• Inventory all equipment - Document every server, switch, firewall, and cable
• Determine space requirements - Calculate total rack units (U) needed
• Calculate power needs - Measure actual power draw in watts/amps
• Plan network architecture - Design IP addressing, VLANs, and firewall rules
• Order circuits - Internet circuits can take 30-60 days to provision
• Sign contracts - Finalize colocation agreement and SLA terms

Phase 2: Pre-Migration Setup (2-4 Weeks Before)

• Full backups - Complete verified backups of all systems
• Document configurations - Export all network configs, firewall rules, DNS records
• Set up remote management - Configure IPMI/iDRAC/iLO on all servers
• Lower DNS TTL - Reduce TTL values 48 hours before migration
• Create migration schedule - Plan the exact order of system moves
• Communicate maintenance window - Notify customers/users

Phase 3: Physical Migration (Migration Day)

• Shut down servers gracefully - Proper shutdown, not hard power off
• Label everything - Every cable, server, and port
• Transport safely - Padded cases, anti-static bags, climate-controlled transport
• Rack and cable - Install per your rack layout plan
• Verify power - Connect A+B feeds, verify UPS protection
• Power on sequentially - Networking first, then storage, then compute

Phase 4: Post-Migration Verification

• Verify all systems boot - Check via console or remote management
• Test network connectivity - Ping tests, traceroutes, bandwidth tests
• Verify applications - Test every application and service
• Update DNS - Point records to new IP addresses
• Monitor for 48 hours - Watch for thermal, network, or application issues

Common Mistakes to Avoid

• Not testing backups - Verify restores BEFORE the move
• Forgetting DNS TTL - Lower TTLs days before, not during migration
• Skipping remote management - You WILL need remote console access
• Moving everything at once - Migrate in phases to reduce risk
• No rollback plan - Plan for what happens if migration fails