Access and Feeds

ECM: Steps for Successful Data Migration Projects

By Dick Weisinger

Here are some things to think about before beginning a data migration project:

  • Understand your data. Where is it located? How big is it now? What is its growth path?
  • What security is needed to protect the data? How many and which roles of users are needed? What levels of access?
  • How often is the data used and what type of I/O bandwidth is required to transmit it?
  • What is the relative importance of the data and how quickly does it need to be made available?
  • Is there so much data, do you want to try to take advantage of a tiered hierarchy of storage media?  If so, the data should be classified so that it can be distributed most cost effectively across different storage class devices.
  • Understand how much it costs to manage the current data set. Will this be consistent with the new system.  Is this the main factor in calculating ROI for the new system?
  • Is the migration is simple “move of the data”, or will it somehow “improve” the data?  eg., remove unneeded data replication, conversion of file formats, consolidation into a centralized system, addition of metadata, …?
  • What criteria will be used to judge the success of the migration? Service Level Agreements? Time and Budget? New environment with greater simplicity and stability? …?
Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Leave a Reply

Your email address will not be published. Required fields are marked *

*