IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere MQ Workflow
Preparing for migration from WebSphere MQ Workflow
Before migrating to IBM Integration Designer from WebSphere MQ Workflow, first ensure that you have properly prepared your environment.
The scope and completeness of mapping depends on how you adhere to the following guidelines for migration:
- Ensure that FDL program activities are associated to a user defined process execution server (UPES) if they are not pure staff activities.
- Ensure that staff assignments for WebSphere MQ Workflow program activities are compliant to TEL default staff verbs.
- Use short and simple names to improve the readability of migrated process models. If that FDL names may be illegal BPEL names. The Migration wizard automatically converts FDL names to valid BPEL names.
The Migration wizard will produce syntactically correct business process editor constructs even for WebSphere MQ Workflow constructs that cannot be migrated (PEA or PES program activities, some dynamic staff assignments, and so on), which need to be manually adapted to runnable business process editor artifacts.
The following table outlines the applied mapping rules:
| WebSphere MQ Workflow | IBM Integration Designer |
|---|---|
| Process | Process with execution mode: longRunning; Partner links for inbound and outbound interfaces of process |
| Source and Sink | Variables for process input and process output; Receive activity and reply activity |
| Program activity | Invoke activity |
| Process activity | Invoke activity |
| Empty activity | FMCINTERNALNOOP activity |
| Block | Scope with embedded BPEL activities |
| Exit condition of activity | While activity (enclosing the actual activity) |
| Start condition of activity | Join condition of activity |
| Staff assignment of activity | Human task activity |
| Input container and output container of activity | Variables used to specify the input/output of invoke activity |
| Control connector; Transition condition | Link; Transition condition |
| Data connector | Assign activity |
| Global data container | Variable |
You should initially try the migration process with small projects, if possible. The Migration wizard will simplify the conversion of your WebSphere MQ Workflow process models into business process editor process models, but you should be aware that the processes cannot be mapped one-to-one as you are creating a new programming model. The semantic scopes of the underlying process specification languages (FDL and BPEL) share an area of intersection, but they do not overlap in total. Otherwise, you could not expect any new benefits from business process editor. Web services represent a promising new technology that claim replacing deprecated solutions by new ones.
In general, you should always review and possibly modify the generated artifacts. Additional effort may be necessary to either make a successful migration possible or to complete the migration task.
: 
Migrating to IBM Integration Designer from WebSphere MQ Workflow