Methods of Conversion

Direct conversion:

• one is turned off and the other is turned on
• requries to be confident that the new system will work as you cant go back to the older system - no fall back option
• being aware of the limitations and the functions of the system
• participants must be full trained in the operation of the new system before the conversion takes place.

Parallel Conversion:

• operating both the old and new system together for a period of time.
• allows any major problems with the new system to be ecountered and corrected without the loss of data.
• users of the sytem have time to familiarise with the new system.
• old system remains as a backup for the new system
• more work load for handling both the system
• once the new system is fully functinal and tested the old system can be ceased.

Phased Conversion:

• gradual introduction of the new system while the old system is progressively discarded.
• often used becauser the system as a whole is still under-development
• when agile methods are used phased conversion is appropriate.
• sub-systems are released
• for large organisations the conversion process makes things more manageable
• parts of the system are introduced systematically across the organisation, each part replacing a component of the old system.

Pilot Conversion:

• new system is installed for a small number of users
• users learn, use and evaluate the new system
• once the system performance is deemed satisfactory then it will be installed to use by all.
• usefull for a large number of systems
• allows a base of users to get use to and learn the system
• users can assist in training others for the final implementation of the system
• can be used as the final acceptance testing of the product
• developers and customers ensure that the system meets requirements in an operational environment,
• compatibiliy issues