Migration
Migrating Into a Data Centre: A Practical Guide
8 min read
A successful data centre migration requires accurate discovery, completed connectivity, tested racks, controlled transport, rollback plans and post-move validation.
Discover and document the current environment
Begin with a complete inventory of servers, storage, network devices, applications, dependencies, warranties and owners. Record rack units, depth, weight, power draw, plug type, IP addresses, cable connections and shutdown procedures. Identify unknown or unsupported equipment before the move. Application discovery is equally important: a server that appears non-critical may provide DNS, authentication, licensing or monitoring for many other systems. Use the discovery phase to remove obsolete equipment and decide whether some workloads should move to cloud or be replaced rather than physically relocated.
Design and prepare the target site
Confirm cabinet dimensions, power feeds, rack PDUs, cooling, network ports and equipment weight limits. Complete carrier circuits, cross connects, internet services and cloud connections well before migration day. Label rack positions and cables in advance, and prepare a target rack elevation. Verify access cards, loading arrangements, parking, trolleys, build rooms and after-hours contacts. Providers such as NEXTDC and Equinix have defined onboarding and access procedures, but each site is different. A technical site visit can prevent last-minute surprises.
Choose a migration method
A physical “lift and shift” shuts down equipment, transports it and installs it at the new site. This can be direct but creates a defined outage and transport risk. A staged migration builds new infrastructure at the target site and moves applications gradually, reducing downtime but increasing cost and complexity. Replication and temporary network links can support phased cutovers. Select the method based on application tolerance, hardware age, budget and rollback options. Do not move fragile legacy equipment without considering whether it will restart successfully.
Plan the migration event
Create a detailed runbook with tasks, owners, timings, dependencies, approvals and decision points. Include backups, data replication, change freezes, customer communications and vendor support. Use professional transport with suitable packaging, insurance and chain-of-custody controls. Photograph equipment and cabling before removal. Define the latest time at which the team can roll back, and make the rollback technically possible. Confirm that DNS, certificates, firewall rules, monitoring and remote access are ready before applications are declared available.
Validate and close the project
After installation, check power-feed balance, device health, network paths, application transactions, backups, alerts and performance. Test failover rather than only normal operation. Ask business users to validate critical workflows. Monitor closely during the first days and keep the old environment available until agreed acceptance criteria are met. Update diagrams, asset registers, support procedures and disaster recovery plans. Finally, securely erase or dispose of retired equipment and close unused circuits. A migration is complete only when the new environment is operationally supported, not when the last server is mounted.
Frequently asked questions
Not sure how this applies to your business?
The free assessment turns answers like these into realistic pricing and a provider shortlist for your specific requirements.
Start free assessment