Customer Success

Data Migration


A successful conversion is an important milestone in the implementation of Quantum. The approach we take to conversion is both efficient and cost effective. Component Control has performed literally hundreds of conversions, from the simple to the complex. We’ve seen them all. We have extensive experience with what works and what does not. This document offers an approach based on what works.

This document is intended to help get you understand the approach and to help customers develop conversion strategies. The strategy should address what data will be extracted from the legacy system, who will do the extract, how will the extract be reformatted to meet the Quantum requirements, how much history will be retained, and what to do with basic integrity issues. After the conversion strategy is in place, the conversion activities can begin.

Please contact our Data Services department for conversion mapping requirements. Component Control can help with the extract effort if required. This normally requires additional budget, but is often very efficient because of our consultants’ extensive experience with conversions. Component Control can also recommend 3rd party consultants to assist in the extract if required. This Guide contains a list of all possible extract tables. It is unlikely that all will be required.

This document will be updated periodically. Contact your Component Control representative to ensure you are working with the latest version.

Note: Customers that are coming from Quick Quote, Quick List, or Pentagon need not read this document. Contact Component Control to obtain the specific requirements for your conversion.

The Conversion Process

Step 1 - Customer Extracts and Formatting the data.

Extracting and Formatting can be two very different activities. If the source of the data is a relation database, or if data access tools are available, the extract can be a very simple activity. The extract needs to be a fixed length ASCII file. A determination of how much history to extract should be made at this point. It’s a good idea to avoid data that does not have the proper integrity (old data can be prone to this). Also, data volumes should be considered. Don’t extract a few gigabytes of data unless there is a great amount of value in having that data, otherwise it could cause an impact in the performance of the Quantum application (reports, inquires could take longer to run).

Formatting the data to match Quantum Control requirements is the customer’s responsibility. This usually requires a technical resource that is familiar with the source data model and the content of the data records.

Some Customers elect to convert just the ‘basics’. This would be the Part Master, Customer, and Stock Lines records. Sometimes the history is such poor quality that keeping it is actually a liability. Furthermore, if the legacy system can be kept around for reference, then history can be researched there. This approach works best for companies that want a fast track approach to implementation.

Step 2 - Extract is evaluated by Component Control.

The extract is sent to Component Control for evaluation. You can send a sample or the entire dataset. Sample datasets need to be complete, representing all tables that will be converted. We will make an initial determination as to whether the extract complies with the required formats. Obviously, we are not experts on our customer’s source databases, and if there is a problem in the formats, it will have to be fixed on the customer’s side. If the extract complies we accept it, if it does not we will require the customer to correct it and the conversion process goes back to Step 1.

We evaluate basic data content and data relationships. Stock Lines need links to Parts Master records; PO Detail records need links to PO Header records, etc.

It is not unusual for several extracts to be required before there is an agreement that the extract is suitable to move forward with.

Component Control can help with the extract effort if required. This normally requires additional budget, but is often very efficient because of our consultants’ extensive experience with conversions. Component Control can also recommend 3rd party consultants to assist with the extract if that is required.

Step 3 - Quantum Conversion is performed.

Once Component Control accepts the extract, we use our Conversion Tool kit to convert the extracted dataset into a Quantum database. This process includes building missing links and building associated Quantum look up tables that are not part of the extract.

During this process we review the customer’s data, looking for anomalies that could not be detected in Step 2. In Step 2 we validate just the format and basic content, in this step we validate data integrity as well.

We are in close touch with our customers during this step. Data integrity problems can be resolved in a variety of ways. Sometimes the Customer must manage the problem; often times we can use utilities to assist.

A simple example: If the Part Number found in Quote history is not found in the Parts Master, that is an integrity problem. We can either add the Part to the Parts Master or delete the Quote history. Not a hard thing to manage, but a choice has to be made.

Data integrity problems that cannot be fixed in this step must be fixed in Step 1. In this case another extract is required.

Step 4 - Converted database is validated by the Customer.

When the Quantum database is finally built, we deliver and install it onto the customer’s server. The customer needs to review their data and confirm that the conversion is successful. It is up to the customer to tell their technical person doing the extract, and us, if there are problems with the data. As stated earlier, we are not familiar with our customer’s data or database structures.

A good way to do this is with a side-by-side comparison. Bring up similar data in Quantum Control and in the Legacy system and compare Parts data, Purchase Order data, Stock Line data, etc.

You should also do “mock” transaction in each and every module to ensure the converted data can be used in a real world environment. This would include adding parts and stock lines, adjusting parts and stock that were converted, creating Sales Orders and Purchase Orders, evaluating open orders to ensure a PO can be received, receiving your cores from open exchanges, etc.

It is a good idea to run Quantum reports and queries to ensure that data is not ‘missing’.

If there are any problems at this point we either go back to Step 3 (Component Control needs to fix it), or Step 1 (Customer needs to fix it).

Once it is agreed that the conversion is ready, the ‘Go Live’ conversion can be scheduled.

Usually, Quantum training is provided by this point so users are qualified to evaluate the conversion.

Step 5 - The ‘Go Live’ conversion is scheduled.

From a format standpoint it is very important that the ‘Go Live’ conversion is identical to the previous conversion. If problems arise in the ‘Go Live’ conversion, they can be very costly and disruptive to the implementation effort. In our experience most ‘Go Live’ conversion problems stem from formats that were changed since the last conversion, or data integrity problems that existed in the previous conversion but were not discovered.

The lesson here is - don’t change the format and check the conversion data thoroughly (step 4).