NiFi 1 to NiFi 2 Migration

NiFi 2 is not a click-upgrade. It needs Java 21, it drops XML templates and the variable registry, it removes support for several scripting languages in scripted components, and it retires or renames a long list of processors and controller services. Teams that built flows over several years have a flow-by-flow job in front of them. We do that job.

The sequence

1. Get to the final 1.x release. The supported route to NiFi 2 runs through the last 1.x line. We upgrade there first, in staging and then production, and use its deprecation warnings to confirm the component census from the assessment.
2. Replace variables with parameters. Flows that read the variable registry move to parameter contexts while still on 1.x, where the change can be tested on the version you already trust.
3. Retire XML templates. Template-only flows are imported, cleaned up and versioned in a registry as JSON flow definitions, so every flow has a history before the upgrade.
4. Rewrite scripted components. Scripts in languages NiFi 2 no longer supports are rewritten in Groovy, as NiFi 2 Python processors, or as small Java processors, depending on what they do and who will maintain them.
5. Replace removed components. Each removed processor or controller service gets its replacement, configured and tested against the same data.
6. Build the NiFi 2 platform. Java 21, the new configuration and repository settings, TLS and authentication, built as a parallel staging cluster rather than an in-place change.
7. Test flow by flow. Functional tests on representative data, then volume tests at production rates, with back-pressure and provenance watched under load.
8. Cut over with rollback. Flows move to the NiFi 2 cluster in agreed groups inside your change windows, with the 1.x cluster held ready and the rollback steps rehearsed before the first group moves.

What stays in your hands

Runbooks, test evidence and the flow history in the registry belong to your team. If you want to run part of the migration yourselves, the plan is written so you can.

Billed hourly. Talk to an engineer.