IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from Teamworks 6 > Upgrade Readiness Check > Upgrade Readiness Check Overview
Migration phases
Migrating from Teamworks to IBM BPM includes several major phases: analysis, planning, development migration, and runtime migration.
The following steps describe how each phase should progress:
- Analysis (days/weeks): Run the Upgrade Readiness Check
tool to identify potential issues with your Teamworks process assets
relative to IBM BPM.
Fix and test the issues that can be addressed in Teamworks. Repeat
these steps until you find no more issues or until all remaining issues
are to be resolved in the development migration phase.
The term process assets refers to all items created in Teamworks to define, implement, and analyze your processes, such as Business Process Definitions (BPDs), Coaches, services, participant groups, and reports.
- Plan (days/weeks): Concurrently with the analysis phase, plan the rest of the migration project, including the following steps:
- Implementing changes to Teamworks process assets
- Install IBM BPM
- Migrating data to IBM BPM
- Development migration (weeks): Install IBM Process Center and import your process assets. Fix any issues you encounter and test
the fixes.
You must migrate all your process assets at the same time. You cannot migrate process assets incrementally.
- Runtime migration (days): For each runtime environment, follow these steps:
- Install IBM Process Server.
- Migrate all runtime data.
- Test and fix processes in the new environment.
- Decommission the Teamworks installation.
Even if you are not ready to migrate to IBM BPM right now, you can prepare for a future migration by running the Upgrade Readiness Check tool periodically and addressing any reported issues.
