Data center relocation checklist: planning and acceptance
A data center move affects equipment, application data and the people who use the services. This checklist helps an IT manager prepare a move with the relevant suppliers. Use the questions to create a project-specific plan, assigning an owner and a recorded result to each check. Gateflow is an IT company based in Frankfurt.
Updated
Define the service that must work after the move
Begin with the business tasks users must be able to complete at the destination. Name the application owner who can confirm those tasks and the person who can approve an interruption. NIST contingency planning guidance uses business impact and recovery priorities to inform the recovery plan. For a planned move, record the acceptable interruption and the data recovery point needed by each affected service.
- List the applications, hosts and storage included in the move.
- Name the business owner and technical owner for each service.
- Agree the migration window and the conditions that would stop the move.
Map equipment and dependent applications
Record serial numbers and rack positions, then map power connections and network ports. Application owners should identify dependencies such as identity services, databases and scheduled imports. Check which licenses or access rules depend on a device identifier, IP address or location. A service may start successfully while a nightly transfer remains broken. Include those less frequent tasks in the inventory and give each dependency an owner who can verify the connection at the destination.
- Label both ends of cables and retain an agreed connection record.
- Confirm destination space, power and network provisioning with the facility.
- Verify site access, transport arrangements and supplier attendance before booking the move.
Prove a recovery path before dismantling equipment
Agree which backups and configuration records are needed if the transfer or startup fails. Test a restoration into an appropriate environment and have the application owner check the recovered data. Record the tested recovery point and the time required for each recovery step. Note any access or license dependencies. NIST describes recovery testing and exercises as part of contingency preparation. A completed backup job provides different evidence from a successful restore of the application.
Decide who can authorize a return to the previous environment. If the original equipment is being physically moved, describe where and how that return could happen. Include the handling of records created after the last backup.
Plan and rehearse the cutover
The move plan should name the person performing each action and the evidence required before the next action starts. Include stopping writes, confirming the final data copy and shutting down dependent services in the agreed order. Separate transport tasks from application startup. Walk through the plan with the people who will execute the move; rehearse recoverable technical steps where the environment allows. Record supplier phone numbers and an alternative contact method available during a network interruption.
- Set the latest decision time for continuing or starting recovery.
- Name the person who announces progress and records decisions.
- Confirm that the final plan and necessary credentials remain accessible during the move.
Check user tasks before accepting the destination
Use the same business tasks agreed before the move. An authorized user should sign in, retrieve an expected record and complete the selected transaction where applicable. Compare transferred data using checks suited to the system, such as record counts plus selected field values. Test required integrations and confirm backup and monitoring operation. Record a failed check with an owner and a decision about its effect on acceptance. The business owner approves the service result; a powered-on server alone does not establish readiness.
Hand over the operating record and remaining work
Update the equipment inventory and operating instructions with the destination configuration. Assign unresolved issues and arrange a follow-up check for tasks that run weekly or monthly. Agree when the old environment can be decommissioned, taking retained records and the recovery plan into account. The receiving operations team should confirm access and understand which supplier handles each remaining dependency.
Gateflow supports data center installations and moves with an agreed equipment scope and on-site checks. For a move involving several teams, technical migration leadership can be discussed as a separate responsibility. A useful inquiry includes the inventory, destination requirements and proposed window.