On the list of things guaranteed to give you a migraine, data migration is a close second to fingernails on a chalkboard. Even the best-laid plans always seem to have something go awry. Whether it is the unexpected data source discovered in the final hour, the laundry list of issues from user testing or the seemingly endless budget overruns and launch delays, everyone seems to have a data migration horror story to tell. While there is no magic pill or silver bullet to make data migration efforts flawless every time, there are a couple of ways to soothe the pain.

Data migration is an IT issue. Business users expect to have accurate, appropriately accessible data, but they don’t care about the details of how or where the data is stored. While there will be many business considerations to make throughout the data migration process, the planning and implementation of moving data from one system to another rests solely on IT’s shoulders. Business users must be engaged to identify the needs and use of data throughout the organization. The buy in of the business users will be critical because they will be the ones using the data once the migration is complete. However, just because the business users are engaged and consulted does not mean they are responsible for the success of the migration. The brass tacks of making the migration happen and ensuring the data is readily accessible is the responsibility of IT. The accountability for the success (or failure) of data migration is all in their hands. It is a huge responsibility not to be taken lightly.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access