Colocation Migration: The Ultimate Technical Checklist
Let’s be honest: few projects induce as much anxiety for Sysadmins and IT Managers as a physical server migration. You are unplugging the beating heart of your organization's infrastructure, putting it in a truck, and praying it boots up correctly on the other side. A successful move to a data center isn't about brute force; it’s about meticulous planning, obsessive documentation, and anticipating the inevitable curveballs.
Whether you are migrating a single rack or an entire cage, winging this technical migration is not an option. To help you avoid a disaster during your physical move, we have compiled the ultimate colocation migration checklist.
Phase 1: Pre-Migration Auditing & Documentation
The success of your migration is determined weeks before you touch a single power cable. You cannot successfully move an environment you don't fully understand.
- Comprehensive Hardware Inventory: Document every physical asset. Record serial numbers, MAC addresses, warranty statuses, and physical dimensions (U-space).
- Application & Dependency Mapping: Servers do not operate in a vacuum. Map out your dependency chains. If Server A hosts the database that Server B relies on to boot your core application, you need to know this for your power-on sequence.
- IP Mapping & Firewall Rules: Audit your current IP schemas. Are you retaining your current IP blocks, or is the new facility providing them? Document all NATs, VPN tunnels, and firewall rules that need to be updated to reflect new public IPs.
- Review Redundancy & Backups: Execute a full, verified backup of all critical systems. Do not migrate hardware without an off-site, air-gapped backup. Verify your disaster recovery (DR) protocols are operational in case hardware is damaged in transit.
Pro Tip: Freeze all non-critical updates and changes to the environment at least two weeks before the migration. You want a stable, predictable baseline.
Phase 2: Network Cutover Strategy
The physical move is only half the battle; keeping your traffic flowing seamlessly is the other. Your network cutover requires precision timing.
- DNS TTL Reduction: At least 48 to 72 hours before the migration, lower the Time-To-Live (TTL) settings on your DNS records to 300 seconds (5 minutes). This ensures that when you update your A records to point to the new data center IPs, the changes propagate across the internet almost instantly, minimizing downtime.
- BGP & Routing Configuration: If you are bringing your own IP space (BYOIP) and ASN, coordinate with your new data center to establish BGP sessions in advance. Ensure route advertisements are configured and ready to be toggled on.
- Configure Redundant Uplinks: Pre-configure your switches and firewalls for the new environment. Test your cross-connects and redundant uplinks (e.g., LACP, VRRP/HSRP) virtually if possible, or immediately upon racking.
- Establish Out-of-Band (OOB) Management: Ensure your , iDRAC, or iLO interfaces are configured for the new OOB management network. If the primary network fails, this is your lifeline.
Phase 3: Hardware Prep & Transport
Proper server colocation preparation is the difference between a smooth racking process and hours of sweating over bent metal and missing screws.
- Obsessive Labeling: Label everything. Label both ends of every power and network cable. Label the front and back of every server with its hostname, target rack, and target U-space.
- Verify Rail Kits & Power Drops: Do not assume your old rails will fit the new racks. Verify rack depth, threading (square hole vs. threaded), and rail compatibility. Confirm that your Power Distribution Units (PDUs) match the power drops (e.g., L6-30P, C13/C19 receptacles) provided by the facility.
- Pre-Rack Cabling (If Possible): If you have access to the new facility beforehand, run your top-of-rack (ToR) switch cabling and power cords. Having the copper and fiber pre-dressed makes the actual server installation infinitely faster.
- Safe Hardware Transport: For heavy storage arrays, remove the hard drives, label them sequentially by bay, and transport them in anti-static, shock-proof cases. Standard moving companies do not understand the fragility of enterprise hardware. Hire specialized IT movers who use air-ride trucks, climate-controlled cabins, and proper ESD (electrostatic discharge) packaging.
Phase 4: Execution & The Power-On Sequence
The truck has arrived at the new facility. Now it's time for the physical data center rack setup.
- Rack and Stack: Follow your pre-planned elevation diagrams strictly. Install heavy UPS units and battery backups at the bottom of the rack, followed by storage arrays, servers, and finally switches at the top.
- Cable Management: Route power cables on one side of the rack and data cables on the other to prevent electromagnetic interference and maintain clear airflow.
- The Power-On Sequence: Boot your infrastructure methodically based on your dependency map: Core Networking, Storage Area Networks (SANs), Hypervisors, Core Infrastructure Servers, Databases, and finally Application/Web Servers.
- Validation Testing: Verify OOB management access, test external connectivity, and have application owners sign off on functionality before declaring the migration complete. Don't forget to restore your DNS TTLs to their normal values once stability is confirmed.
Make Your Next Move with Gander Web
A colocation migration is demanding, but choosing the right facility partner significantly reduces the friction. At Gander Web, we don't just provide space and power; we provide a secure, high-performance foundation for your infrastructure.
- Uncompromising Security: Strict ISO and SOC compliance, multi-factor biometric access controls, and 24/7 on-site security personnel.
- Expert "Remote Hands" Support: Certified, 24/7/365 technicians acting as an extension of your IT team for hard resets, cable swapping, and hardware inspections.
- Resilient Infrastructure: Fully redundant N+1 power and cooling systems, backed by a 100% uptime .