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 > Prepare to migrate > High-level tasks

Development migration phase

Before beginning a migration project, you should understand the tasks involved when migrating your development environment.

When your team has addressed the issues identified by the Upgrade Readiness Check tool during the analysis phase, you can start to migrate the development environment as described in the following overview.

See Migrating the development environment for detailed instructions.

  1. Install the new version of IBM Process Center, following the appropriate installation instructions for the Standard or Advanced edition of IBM BPM.

    Choose the custom installation path when installing for a planned migration. The custom installation path provides the configuration options necessary for a migration.

  2. Start the server for IBM Process Center V8.0.1, which includes the Process Center Server and Performance Data Warehouse, and verify that the Process Center Console can be accessed.
  3. Download and extract IBM Process Designer from the Process Center Console.
  4. Export process assets from the existing Teamworks 6 installation. Export existing projects with all dependencies so that each individual Teamworks 6 project can be imported into a separate process application in IBM BPM V8.0.1.
  5. Import the process assets into the new version of IBM Process Center.
  6. Refactor the imported process assets into process applications and toolkits by moving assets. You should ensure that all assets required to implement a particular application remain in a single process application. Process assets that were organized for re-use across applications in Teamworks 6 can be moved to toolkits in IBM BPM V8.0.1.

  7. Perform the regression test suite to identify issues.
  8. Fix and test issues that appear in the library in the new version of Process Designer. These might include issues that were identified by the Upgrade Readiness Check tool, and were planned to be addressed after migrating the process assets.

: High-level tasks