Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

Data Migration Project Planner from Data Migration Pro.com by Mind Map: Data Migration Project Planner
from Data Migration Pro.com
5.0 stars - 1 reviews range from 0 to 5

Data Migration Project Planner from Data Migration Pro.com

Copyright Notice

Please note this checklist is copyrighted by Data Migration Pro. You can use it on your own data migration project or learning but you must not sell, profit or distribute. Copyright 2016 | Data Migration Pro

Phase 2: Project Initiation

Have you created a stakeholder communication plan and stakeholder register?

Have you tweaked and published your project policies?

Have you created a high-level first-cut project plan?

Have you set up your project collaboration platform?

Have you created your standard project documents?

Have you defined and formalised your 3rd Party supplier agreements and requirements?

Have you scheduled your next phase tasks adequately?

Have you resolved any security issues and gained approved access to the legacy datasets?

Have you defined the hardware and software requirements for the later phases?

Phase 1: Pre-Migration Planning

Have you assessed the viability of your migration with a pre-migration impact assessment?

Have you based project estimates on guesswork or a more accurate assessment?

Have you made the business and IT communities aware of their involvement?

Have you formally agreed the security restrictions for your project?

Have you identified your key data migration project resources and when they are required?

Have you determined the optimal project delivery structure?

Do you have a well defined set of job descriptions so each member will understand their roles?

Have you created a structured task workflow so each member will understand what tasks are expected and in which sequence?

Have you created the appropriate training documentation and designed a training plan?

Do you have a configuration management policy and software in place?

Have you planned for a secure, collaborative working environment to be in place?

Have you created an agreed set of data migration policy documents?

Phase 3: Landscape Analysis

Have you created a detailed data dictionary?

Have you created a high-level source to target mapping specification?

Have you determined high-level volumetrics and created a high-level scoping report?

Has the risk management process been shared with the team and have they updated the risk register?

Have you created a data quality management process and impact report?

Have you created and shared a first-cut system retirement strategy?

Have you created conceptual/logical/physical and common models?

Have you refined your project estimates?

Phase 4: Solution Design

Have you created a detailed mapping design specification?

Have you created an interface design specification?

Have you created a data quality management specification?

Have you defined your production hardware requirements?

Have you agreed the service level agreements for the migration?

Phase 5: Build & Test

Has your build team documented the migration logic?

Have you tested the migration with a mirror of the live environment?

Have you developed an independent migration validation engine?

Have you defined your reporting strategy and associated technology?

Have you defined an ongoing data quality monitoring solution?

Have you created a migration fallback policy?

Have you confirmed your legacy decommission strategy?

Have you completed any relevant execution training?

Have you defined the data migration execution strategy?

Have you created a gap-analysis process for measuring actual vs current progress?

Phase 6: Execute & Validate

Have you kept an accurate log of SLA progress?

Have you independently validated the migration?

Phase 7: Decommission & Monitor

Have you completed your system retirement validation?

Have you handed over ownership of the data quality monitoring environment?