Data Migration
The “Big Bang” approach can be adopted for migrating the first set of records to a new Management System.
All transactional data is migrated in one go, static information can be migrated before the final migration to shorten the migration period. Of course, depending on volumes a staged approach may be required.
A migration database, separate from the legacy and new databases, may be used to map and cleanse the incoming data.
- Data is obtained from a variety of sources.
- The migration database is set up with one to one tables for each of the application modules that will be updated in the new Management System. E.g. Customer, Contract, Vehicle, etc.
- Cleansing and code mapping takes place during the loading of the migration database.
- Data is audited.
Cleansed data is transformed into flat files and transferred to the new Management System server.
The migrated data on the new Management System is then audited to ensure that all data has been successfully and correctly migrated.
Example
A company requires a data transfer from a Legacy Fleet Management System to a New Fleet Management System.
Due to the size, quantity and nature of the data, the “Big Bang” approach is decided upon.
Process
- A migration database is set up with tables for each New Fleet Management System application that data is being migrated to.
Required data is mapped from the source data, extracted, cleansed and transformed before being inserted into the migration database. - Flat files are generated from the migration database and these files are uploaded to the New Fleet Management System using the new system’s loaders where possible.
- The i-Con integration tool is used to build the Migration Database and for creating the text file output required by the New Fleet Management System.
Using the i-Con integration tool the migration process is broken into 3 phases:
1. Build Phase
The i-Con integration tool is configured according to the design templates. All data requirements and mapping are detailed, this includes the validations for data cleansing.
2. Test Phase
This comprises an end-to-end test of the migration process. The New Fleet Management System input files are processed by the loaders and the new database is built.
3. Audit Phase
Reports are generated in the New Fleet Management System to audit the migration process. The company validates the conversion process and signs off when the migration is correct and complete.
