Typical path
- analyze the current 1.x flow
- check whether a bridge upgrade is required first
- apply safe and assisted rewrites where the rule pack makes them explicit
- review blocked and manual-change findings
- validate against the target 2.x runtime
Common 1.x to 2.x issues
- bridge requirement before NiFi 2.0.x
- Variable Registry expression usage
- renamed cache services
- deprecated processors that map to newer components but still need review
- secret and parameter rehydration in the target environment
A good first demo
Start with the Orders Platform `1.27 -> 2.0` story. It shows the real mixed-result case: one blocked finding, two safe rewrites, one assisted rewrite, and one manual-change finding in a single flow.
./demo/orders-platform-1.27-to-2.0.sh
./demo/bridge-upgrade-1.21-to-2.0.sh