Data Center Migration Checklist

Use this Data Center Migration Checklist to plan and execute migration tasks, ensuring a comprehensive and efficient transition with minimal disruptions.

Download as free PDF

Library
IT & Data Center
Data Center Migration Checklist

30-45 Days Prior

21-30 Days Prior

14 Days Prior

7 Days Prior

The Day Of The Move

Post-Migration

Is this sample what you are looking for?
Sign up to use & customise this template, or create your own custom checklist:

Checklist by GoAudits.com – Please note that this checklist is intended as an example. We do not guarantee compliance with the laws applicable to your territory or industry. You should seek professional advice to determine how this checklist should be adapted to your workplace or jurisdiction.

Easy inspection app for your digital checklists

Conduct inspections anytime, anywhere - even offline
Capture photos as proof of compliance or areas needing attention
Instantly generate and share detailed reports after the inspections
Assign & track follow-up tasks, view historical trends on a centralized dashboard

Data Center Migration Checklist

Use this Data Center Migration Checklist to plan and execute migration tasks, ensuring a comprehensive and efficient transition with minimal disruptions.

1. Has a migration project manager been established, preferably one with experience in migrations and not overly vested in any one department?

2. Have team leads for departments involved in the migration been determined? Are they decision-makers who will sign off on the migration plan?

3. Have weekly prep meetings with department leaders involved in the migration begun?

4. Has the infrastructure strategy for the next 3-5 years been evaluated, considering scalability?

5. Have point-to-point circuits been ordered? (Note: This can sometimes take up to 60 days.)

1. Has an infrastructure inventory been initiated, detailing every cabinet, every U, and equipment interdependencies?

2. Have owners of every affected application and process been recorded in a database?

3. Have any hard-wired IP addresses or domain names been identified, and has a plan been determined for addressing them at the time of migration?

4. Has documentation, such as port maps and rack elevations, been reviewed to ensure accuracy? a. Have unique identifiers been assigned to every item? b. Has all equipment been labeled with unique identifiers on both the front and back?

5. Has downtime that is acceptable, with go/no-go gates for deployment, been defined?

6. Have the dimensions of the current facility’s doors and exits been measured to ensure the equipment will fit through? (Note: The facility may have changed since older equipment was moved in.)

7. Has a decision been made regarding whether movers will be needed, and if so, how many?

8. Have spare hard drives been ordered for possible failures due to the move?

9. Has the disaster recovery plan been tested, and is there a contingency plan in place for hardware failures?

1. Has a game plan for migration day been developed, outlining specifically who will do what for a more efficient move?

2. Have key processes and applications been tested to establish baselines?

3. Have all changes in the environment been locked down to ensure stability during migration?

4. Has the compatibility of power receptacles at the new site been checked, ensuring the availability of what is needed for the equipment?

5. Has the labeling and current design of the cabling been reviewed, and a plan established for cabling at the new site?

6. Has the current network and application security been reviewed according to compliance requirements?

1. Has the migration team been registered with data center security, including any vendors or third parties?

2. Has equipment been tested for powering down and powering up to check for possible issues, and new gear ordered if necessary?

1. Have the following been packed: • Power cables • Your testing plan • In-cabinet patch cables • SFP cables

1. Have all processes and applications been tested against baseline tests?

2. Has documentation, such as port maps and rack elevations, been validated, ensuring everything is updated?

3. Has the migration process been evaluated, noting what went well and what didn’t? Have changes been made to any plans or documentation as needed?