Steps in a General Approach to Data Migration
This Page describes a series of Steps in a General Approach to Data Migration
between Source Systems and Target Systems.
It covers Extract, Transformation and Load.
Here's a Simple Approach to Migration.
There are no technical risks in Data Migration because it is a well-established
However, it is important to get User involvement right from the start, and
to get User sign-off at the end when all the Data has been successfully migrated.
Create the Business Data Model for the Consolidated Database
If the final target is an ERP, such as SAP, then create the Data Model for the Target ERP Database
For SAP, J.D.Edwards, Peoplesoft and Siebel, a Modelling Tool called
Saphir, from Silwood Technology
can be very useful here.
Define the Data Mapping between Source and Target Data Items.
Optionally, create a CRUD Matrix to identify the interactions between Data and Functions.
Define Acceptance Tests for data in the Integrated Database.
Executing the Data Migration Process.
- Optionally, choose a Data Migration Tool.
- Create Extract Files for each Data Source in turn.
- Resolve any Errors with the Users.
- Create Extract and perform Data Clean-Up.
- Complete the Migration, (Extract, Transform and Load) for each Data Source.
- Run Acceptance Tests on the Integrated Target Database,(esp. Referential Integrity).
There are not many books on Database Migration, but here are two :-
- Migrating Legacy Systems, by Brodie and Stonebraker
Stonebraker is well-respected as the Architect of Ingres, but I didn't like this book very much.
Amazon.com, but the only reviewer gave it 4 stars.
- 90 Days to the Data Mart, by Alan Simon.
This,of course,is devoted to Data Marts, but covers some common ground.
Amazon.com, but the only reviewer gave this one 5 Stars.