Analyze

Find out whether the upgrade path is safe before you change anything.

analyze is the first command most teams should run. It reads the source flow, compares it with the target NiFi version, and writes reports that explain what is blocked, what needs manual work, and what can be rewritten safely.

Back to site Supporting source

What you give it

  • a source flow artifact
  • the current NiFi version
  • the target NiFi version
  • one or more rule packs for that version path

What you get back

  • a JSON report for CI and automation
  • a Markdown report for humans
  • clear counts for blocked, manual-change, manual-inspection, auto-fix, and info findings
  • component names, paths, and evidence for each finding
nifi-flow-upgrade analyze \
  --source ./flow.json.gz \
  --source-format flow-json-gz \
  --source-version 1.27.0 \
  --target-version 2.0.0 \
  --rule-pack ./examples/rulepacks/nifi-1.27-to-2.0.official.yaml \
  --output-dir ./out

How to read the result

A blocked finding means the upgrade path is not safe as-is. Manual-change means the migration is understood but still needs a person. Auto-fix means the tool found a deterministic rewrite candidate, but nothing has been changed yet.