You are here

Conduct Conversion

21 September, 2015 - 11:32

After all previous design steps have been completed and signed off, the organization carefully converts to the new system. Conversion includes converting data, converting processes (i.e., the programs), and completing documentation. Controls must be in place to ensure accurate, complete, and authorized conversion of data and programs.

As existing data are mapped into the new system, exception-reporting situations must be devised to ensure that data are converted accurately. Users must suggest control totals that can be used to test completeness and accuracy of data conversion. For example, the total number of inventory items, the total on-hand quantity for all inventory items, or a hash total (described in Chapter 9) of inventory item numbers might be used as totals.


Boston Scientific (see Figure 7.3) implemented SAP over the course of two years at each of its worldwide divisions and locations (i.e., a modular approach). But since SAP was implemented using the direct approach at each of those locations, the data conversion was tested at least seven times, until there were no errors! The company believes that this testing was the key to the successful implementations. 1


Both manual and computer-based processes must be converted. Conversion to new computer programs must be undertaken using program change controls (described in Chapter 8) to ensure that only authorized, tested, and approved versions of programs are promoted to production status.

The systems development project team now writes the project completion report, the final step in the implementation process. This report includes a summary of conversion activities and information with which to operate and maintain the new system.