Overview of pre-migration phase
The pre-migration phase for migrating from a CONVERSANT platform to an Avaya IR platform includes the use of the evaluation tool (scanit), resulting in a log of the evaluation results and a plan of action for each possible result. The evaluation does the following:
- Scans the customer's data, including the following:
- Core Applications (Voice@Work, IVR Designer, Script Builder, IRAPI)
- Utilities and tools
- Custom external functions
- Recorded speech (prompts)
- Host screen files
- Identifies any features or commands on the pre-migration platform that are not supported on the Avaya IR platform and logs the results.
- Includes a plan of action for each item identified by the evaluation tool. The plan of action for unsupported features or commands varies based on the items identified by the evaluation tool.
These activities prepare the customer data for the migration to the targeted platform. For example:
- If speech files are found, they must be converted using the do_speech utility.
- If an application has unsupported features, (for example, Brook Trout external functions), manual intervention is required.
Unsupported features or commands identified by the scanit tool can be addressed by:
- Manual changes made to the application
- Execution of a process to update the application
- Exclusion of the application from the data to be migrated to the Avaya IR platform.
After reviewing the action plans, the customer may update the applications to change or remove the unsupported features or may contact their ISV to assist with this process.
If a Script Builder application requires updates, update the application on the CONVERSANT platform and then move it to the Avaya IR platform. You cannot update Script Builder applications on the Avaya IR platform because the Script Builder development tool is not supported on the Avaya IR platform.
