Data Center Migration RAID Log
This is a practical guide to building a raid log for a data center migration project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of relocating or consolidating data-center infrastructure.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On a data center migration project it plays the same role, tuned to this kind of work.
Why it matters for a Data Center Migration project
Data Center Migration projects live or die on relocating or consolidating data-center infrastructure. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how data center migration projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Data Center Migration-specific considerations
Tailor the raid log to the risks that most often derail data center migration projects:
- Application dependency mapping
- Migration-window downtime
- Hardware and network cutover risk
Example
On a real data center migration project, the raid log would be shaped by relocating or consolidating data-center infrastructure. In particular, it should explicitly account for the project’s biggest risks — application dependency mapping, migration-window downtime, hardware and network cutover risk — rather than treating them as afterthoughts.