Configuration Product Data Migration

Inside Consulting : Consulting & Training Overview l Configuration Management Training l Data Management Training l CM/DM Coachi ng | Requirements Analysis l Configuration Management Plans l Implementation l Product Training l Data Migration l System Integration l Process Optimization l Advanced CM & DM Training l Customer Support l Software Maintenance & Upgrades

A Proven Methodology for Legacy Product Configuration Data Migration & Data Mapping

CMstat uses a proven product data migration methodology to identify, format, and migrate legacy data into EPOCH CM and EPOCH DM software products. Given a solid set of requirements, a fixed price will normally be quoted for the migration service. The process is broken down into two phases: Data Mapping and Data Migration.

Data Mapping

The Data Mapping Phase is normally accomplished in five to ten working days, depending on the number of databases and the complexity of the data. During the mapping, all data elements to be moved from legacy systems are identified and mapped into actual EPOCH CM or EPOCH DM fields.

The result is a data map and format into which the legacy data will be extracted, verified, and brought into the production database. This neutral format contains the data structure and relationships required by the PDMPlus or EPOCH database. Any additional rules for data movement are also defined and documented during this phase.

Data Migration

Once Data Mapping is complete and the extracted data delivered to CMstat, the actual Data Migration Process begins, which involves test migrations and data analysis to ensure data integrity and location in the database. The Data Migration Process may be completed in two to four weeks, depending on the condition of customer data, the number of source databases, and the availability of customer resources.

Once the test data migration is validated for data quality and accepted by both parties, the final migration is run, and the production database is delivered to the customer.