Restricted access
 
 

May 22, 2009

A Checklist for Data Migration Project. Phase 3: Landscape Analysis

Filed under: Data Migration — Olga Belokurskaya @ 7:47 am

Actually, this phase is more a kind of a sequel of the previous one, so it would be better called Phase 2.2. You know, now I understand why so many enterprise data migration initiatives go wrong, you need to bear in mind soooo many things. The process demands constant interaction of all the people involved… Okay, let’s continue checking the data migration to-do list.

  • Have you determined high-level volumetrics and created a high-level scoping report?
    Ensure that you fully assess the scope and volume of data to be migrated.Focus on pruning historical and redundant data. Create a final scoping report detailing what will be in scope for the migration and get the business to sign this off.
  • Has the risk management process been shared with the team and have they updated the risk register?
    Create a simple online form where anyone can add risks during their analysis, you can also filter them out later but for now we need to gather as many as possible and see where any major issues are coming from.
  • Have you created a data quality management process and impact report?
    If you’ve been following our online coaching calls you will know that without a robust data quality rules management process your project will almost certainly fail or experience delays. Understand the concept of data quality rules discovery, management and resolution so you deliver a migration that is fit for purpose. The data quality process is not a one-stop effort, it will continue throughout the project but at this phase we are concerned with discovering the impact of the data so decisions can be made that could affect project timescales, deliverables, budget, resourcing etc.
  • Have you created and shared a first-cut system retirement strategy?
    Now is the time to begin warming up the business to the fact that their beloved systems will be decommissioned post-migration. Ensure that they are briefed on the aims of the project and start the process of discovering what is required to terminate the legacy systems. Better to approach this now than to leave it until later in the project when politics may prevent progress.
  • Have you created conceptual/logical/physical and common models?
    These models are incredibly important for communicating and defining the structure of the legacy and target environments.
  • Have you refined your project estimates?
    Most projects start with some vague notion of how long each phase will take. Use your landscape analysis phase to determine the likely timescales based on data quality, complexity, resources available, technology constraints and a host of other factors that will help you determine how to estimate the project timelines.

No Comments »

No comments yet.

RSS feed for comments on this post. TrackBack URL

Leave a comment