IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from Teamworks 6 > Migrating from Teamworks 6 to IBM BPM V8.0.1

Typical scenarios

Review the following scenarios that may occur when migrating from Teamworks 6, along with the recommended strategies for success.

Situation Strategy
The process assets were developed on a much earlier version of Teamworks, use constructs that were deprecated in Teamworks 6 and are no longer supported in IBM BPM V8.0.1. Run the Upgrade Readiness Check tool to identify unsupported features used in the process assets. Then either address them in the analysis phase, or plan to address them after migrating the process assets in the development migration phase.
Process developers have extensively customized Coaches and the Teamworks 6 Process Portal using JSP, XSL, CSS, and Javascript. Change management has been loose, so a complete inventory of changes is not readily available. Compare the current system against an unmodified installation of the old version of Teamworks 6 in order to inventory all customizations and changes to the standard Teamworks installation. Use this inventory to plan corresponding changes in the new version of IBM BPM V8.0.1.
Process developers have used internal APIs in Javascript code to accomplish creative effects. Luckily, these APIs have not changed significantly in previous versions, but moving to IBM BPM V8.0.1 may break the code. The developers want to start migrating the code before the main migration effort. Use the Upgrade Readiness Check tool to inventory all unsupported API calls in the current implementation. Use this information to port the code to the new JavaScript API.
The IT department wants to automate the migration process as much as possible so that migrating the production server requires no manual intervention. Validate changes on a clean installation of the new version of IBM BPM, then create a script to duplicate those changes. Use the script to make changes during the production migration.
A crucial process has millions of instances that have completed. The completed instances cannot be deleted because they are used in reporting. The production environment can be down for only 48 hours, over a weekend, during which time all the instances must be migrated. The upgrade command-line tool will be able to migrate this volume of instances within the specified time window.

: Migrating from Teamworks 6 to IBM BPM V8.0.1