Migrate a process with evidence

Inventory the behaviors you rely on

For Camunda, Activiti or Flowable, list model extensions, timers, task assignments, message correlation, worker delivery semantics and incident recovery. XML portability does not guarantee runtime equivalence.

Priostack speaks HTTPS and JSON under /api/v1 only: no gRPC, no Zeebe gateway and no Camunda 7 engine REST. Workers keep their job logic and replace their transport. There is no hosted message correlation and no REST resume of an incident, so a process that relies on either needs a redesign.

Separate model changes from client changes

Map the process model first, then adapt the worker API. Preserve business identifiers and decide how external idempotency records survive a switch. Do not cast every engine identifier to a number: preserve the representation the target API returns.

Replay representative cases

1. Deploy one representative process to a test account.
2. Replay normal, boundary, timeout and failure cases.
3. Compare emitted jobs, decision outputs and process outcomes.
4. Rehearse failure: an INCIDENT instance is replaced by a new instance after the cause is fixed.
5. Plan versions: redeploying creates the next version and running instances keep theirs. There is no rollback endpoint.