Behavior:

• if the boundary events are mapped as part of the migration plan, then jobs (timer) and event subscriptions (message, signal) are updated wherever they reference the new process definition
• Timer due date and mesage names are not changed
• if boundary events are not mapped, entities are removed and the newly created, meaning that a timer on the target activity starts as if the target activity itself was just started