From an end user perspective the data migration strategy applied for each application aims to achieve the following:
- Data integrity following data migration. The agreed application data must not be corrupt or incompatible following the data migration exercise.
- The opportunity to iteratively identify and cleanse data that is corrupt on the existing application(s). The aim is to give the users one or more ‘iterative’ opportunities to identify corrupt data, and then rectify it in the existing applications, or automatically cleanse the data within the bespoke data migration functionality.
- The option of data weeding within the data migration mechanism. This involves the identification of migration candidates, such that obsolete data (i.e. non-candidate data) is not migrated into the target database.
- The ability to inspect, but not maintain, data that has been archived either before or during the live data migration run. This feature is particularly important where users will no longer have access to their ‘source’ application(s) and data following migration.