Migration overview

Pre-migration phase

The pre-migration phase 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, Script Builder, IRAPI)
• Data files and database tables
• Utilities and tools
• Pre-packaged speech files (EBS)
• Grammar files
• Custom external functions
• Recorded speech (prompts)
• Call Data Handler (CDH) data (flat files and database tables)
• User logins
• 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 vary 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.
• 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 Avaya or their ISV to assist with this process.

Migration phase

The migration phase includes data conversion and data transport activities. Data must be transported between platforms using a LAN connection. Upgrade procedures and activities for pre-migration and migration occur on the originating platform.

Post-migration phase

In the post-migration phase, verify that migrated components have reached the targeted platform successfully, without any errors. Update custom speech files and migrated Voice@Work and IRAPI applications.

If a Script Builder application requires updates, update the application on the originating platform and then move it to the Avaya IR platform. The Script Builder development tool is not supported on the Avaya IR platform.

Avaya supplied Enhance Basic Speech (EBS), IRAPI commands, DIPs, TAS scripts, and standard external functions are not migrated because they are a part of the base Avaya IR software.

� 2002 Avaya Inc. All Rights Reserved.