Free download
Data Centre Migration Checklist
A data centre migration fails on the things nobody wrote down: circuits ordered too late, cabinets that fit the space but not the lift, and engineers who are not on the access list. This checklist is the sequence that catches those, 48 checks across 7 stages.
It is vendor-neutral and useful whether or not you ever work with us. Enter your email and we will send it as a PDF.
Download
Get your copy
What is inside
A practical, vendor-neutral sequence for moving equipment between facilities without discovering the gaps on move night.
1. Before you commit to a date
Most failed migrations were lost here, weeks before anyone touched a rack. The date should be the output of this section, not the input.
8 checks
2. The receiving site
Verify the destination against measurements rather than against the sales drawing.
7 checks
3. Access and permissions
Access is administrative, it is slow, and it is invisible until it blocks you at the door.
6 checks
4. Preparing the equipment
Everything that can be done before the window should be done before the window.
7 checks
5. The move window
The window is for executing a plan, not for making decisions. Every decision made here is one that was missed earlier.
7 checks
6. Verification before you call it done
Equipment powering on is not a migration completed. Someone has to confirm each service actually works.
7 checks
7. Closing the old site
Unclosed contracts and unwiped equipment both keep costing you after the move is finished.
6 checks
Why these three
The parts that sink migrations
Most of a migration is ordinary project work. Three things account for most of the failures, and all three are decided weeks before the move.
The first is circuit lead times. Cross-connects and carrier services are ordered from third parties on their schedule, not yours, and a date set before those are confirmed is a guess. The checklist puts them in the first two stages for that reason.
The second is access. Every person who needs to be in either building has to be approved, listed and, in many facilities, escorted. Approval and actually being on the list at the security desk are different things, and the gap between them is discovered at the door.
The third is verification. Equipment powering on is not a migration completed. Someone has to confirm each service works, test that redundant paths really are redundant, and check the monitoring is reporting from the new site.
Questions about the checklist
Is it really free?
Yes. It costs an email address, and confirming that address also subscribes you to our short weekly brief. You can unsubscribe from the brief immediately and keep the checklist.
Why do I have to confirm my email?
So that nobody can have a file emailed to an address that is not theirs, and so our subscriber list only contains people who asked to be on it. The download link arrives the moment you confirm.
Do I need to be a DataOptix customer?
No. The checklist is vendor-neutral and most of it is work your own team will do. The only section that mentions us at all is the closing note about where an engineering partner fits.
Will you call me?
No. Downloading the checklist puts you on the weekly brief, not on a call list. If you want to talk to us, the contact form is the fastest route and a coordinator replies within 2 business hours.
Can I share it with my team?
Please do. Share the PDF itself rather than your download link, because the link is tied to your confirmation and stops working after 30 days.
Migrating, and short of hands in the destination city?
Tell us the sites, the window and the scope. A coordinator replies within 2 business hours.