IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Versioning > BPEL processes > Migrating running process instances to a new version of the BPEL process > BPEL process model changes and runtime migration
Additional considerations for BPEL process instance migration
In addition to the changes that are allowed to the properties and the business logic, there are some additional considerations and limitations that apply to the migration of BPEL process instances.
For a new version of a process to be eligible as a migration target, both the original version and the new version of the process must be modeled in one of the following ways:
- In Integration Designer
- In IBM WebSphere Business Modeler Version 7.0.0.2 or later, and then exported to Integration Designer so that it can be enabled for process migration
In addition, if any of the following limitations apply, your process migration specification will be rejected, and you cannot deploy it to Process Server.
- Compensation logic is not supported in either the source or the target process versions.
- SQL snippets are not supported in either the source or the target process versions.
- Correlation sets cannot be added, removed, or modified.
- Custom properties cannot be added, removed, or modified.
- Administration tasks for processes and activities cannot be added, removed, or modified.
- Variables cannot be removed or modified.
- Partner links cannot be modified.
- Changes to data map activities are not detected. This means that a process instance will be migrated, even if the current position of the process navigation is after the modified data map activity.
- Activities can be part of a construct, for example, a loop construct, fault handler, or a case, and this construct is not contained in a sequence or flow activity. Activities cannot be added to or removed from the construct.