Recommended migration workflow

Cloudera recommends dividing the process into manageable phases and validating the results at each step. Below is the suggested migration workflow to ensure a smooth and successful transition.

Stage 1 migration

Template migration
1. Migrate templates for Stage 1.
2. Validate the results.
3. Address any issues and manual change requests.
Variable migration
1. Migrate variables to parameter contexts for Stage 1.
2. Validate the results.
3. Address any issues and manual change requests.
Component migration
1. Migrate components in smaller batches by specifying Process Group IDs for Stage 1.
2. Validate the results for each batch.
3. Address any issues and manual change requests.
4. Repeat iteratively until no further changes are required.
Management-level component migration
1. Perform component migration without specifying a Process Group ID to ensure management-level components such as Controller Services are migrated.
2. Validate the changes.
3. Address any issues and manual change requests.
Final validation
1. When all Stage 1 steps are complete, validate the entire flow in a NiFi 1 instance for final validation.
2. After this point, the flow will no longer be compatible with the source version.

Stage 2 migration: Target version compatibility

Run the migration commands without specifying the Stage argument to process both stages in sequence and address any remaining compatibility issues with NiFi 2.

note

This runs both Stage 1 and Stage 2, but if previous recommendations were followed, Stage 1 has no impact on the flow. While Stage 1 commands should no longer modify the flow, some Stage 2 commands depend on Stage 1 outputs as input (for example for template migration).
Follow the same steps as in Stage 1: Migrate templates → Migrate variables → Migrate components, while validating the results and addressing manual adjustment needs.
Stage 2 migration is not iterative in a sense that the output of Stage 2 cannot be reintroduced into the migration process. To ensure a seamless workflow, fully complete Stage 1 before starting Stage 2, and run Stage 2 only once. The final output will reflect all transformations applied by the Migration Tool. Resolving manual change requests will not trigger further migration events. Any modifications beyond this point are considered business logic adjustments and fall outside the tool’s scope.

For detailed instructions and examples of the end-to-end migration process, see Migrating a data flow.