NiFi Flow Estate Assessment

A written plan your own engineers can execute.

What the assessment covers

The honest answer to "how long will the NiFi 2 upgrade take" depends on things nobody has written down: how many flows are still live, which components they use, and what the scripted processors actually do. The assessment writes those things down.

What we read

  • Flow inventory. Every process group, its owner if there is one, its sources and sinks, and whether anything downstream still depends on it.
  • Component census. Every processor, controller service and reporting task in use, by type and version, matched against what NiFi 2 removed, renamed or replaced.
  • Custom NARs. What each one does, which NiFi APIs it compiles against, and whether its source and build are still available.
  • Scripted components. Every ExecuteScript, InvokeScriptedProcessor and scripted record reader or writer, the language it uses, and what the script really does.
  • Templates and versioning. Which flows live only as XML templates or as hand-edited canvas, and which are already versioned in a registry.
  • Variables and parameters. Where flows still use the variable registry, which NiFi 2 removed in favour of parameter contexts.
  • Platform readiness. Java version, operating system, cluster size, ZooKeeper, repository layout and disk, TLS and authentication.
  • Health. Throughput, back-pressure history, queue depth, provenance repository size and retention, and the bulletins your team has learned to ignore.

What you get

A written findings document and a sequenced remediation or migration plan. Each flow gets a call: carry it forward as is, rework it, consolidate it, or retire it. Effort is given as ranges in engineer-weeks, so you can staff it with us, with your own team, or with both.

What it is not

It is not a sales document for a migration. Some flows are really scheduled batch jobs or commodity SaaS extracts and belong elsewhere. If that is the finding, the document says so, rather than carrying a flow into NiFi 2 only to move it again next year.

Billed hourly, like everything we do. Start with a conversation.

Tell us which NiFi version you run, roughly how many flows, and what is hurting. The first conversation is with the engineer who would do the work.
Talk to a NiFi engineer