Use variable optimization in Optional settings
Large Nintex workflows often initialize many small variables for form fields, routing data, names, emails, IDs, status values, and other related context. Variable optimization reduces that setup noise by grouping safe read-only values into a single object variable while keeping unsafe or changing variables separate.
What the optimization does
When the option is enabled, Flow Migrator looks for safe scalar variables that are initialized once and then only read later. Instead of emitting one Initialize variable action for each value, it creates a single object variable named MigratedVariables and rewrites downstream references to read the matching object property.
The purpose is to reduce setup-action count, reduce generated variable count, and make the top of the migrated flow easier to read without changing the business process.
Before: variables('LeadSource')
After: variables('MigratedVariables')?['LeadSource']When to use it
Use the optimized mode for large workflows, workflows with many form or start-data variables, and workflows that are close to Power Automate action or variable limits. It is especially useful when the variables are data holders used by emails, approvals, conditions, SharePoint updates, or later expressions.
The setting is also helpful during enterprise remediation because it can remove repetitive initialization noise before the team decides whether a parent/child refactor is still required.
- Many variables are initialized with static text, numbers, booleans, or blank defaults.
- The variables are read later but not set, appended, incremented, or decremented.
- The workflow owner wants a shorter, cleaner generated flow.
- The limit-risk panel shows variable count or setup-action count pressure.
When to preserve original variables
Choose Preserve original variable actions when visual fidelity is more important than action-count reduction, or when the team wants the migrated flow to resemble the Nintex source as closely as possible for side-by-side validation.
Flow Migrator already avoids consolidating variables that appear unsafe, but the preserve option is useful for conservative UAT, troubleshooting, or customer handoff when each source variable should remain visible as its own action.
- Variables that are set later or repeatedly updated.
- Counter variables, append-to-string variables, and append-to-array variables.
- Variables used inside loops or parallel branches where mutation order matters.
- Connector output variables or variables that already hold arrays or objects.
- Workflows where business users expect each original variable to be visible in the designer.
How to validate after import
- Open the imported flow and find the Initialize variable action named MigratedVariables.
- Confirm the object contains the expected keys and default values for the source variables that were consolidated.
- Spot-check emails, approval details, SharePoint Update item actions, and conditions that reference those values.
- If an expression should remain easier for a business user to edit, rerun the export with Preserve original variable actions.
- For parent/child experimental packages, confirm important values are still passed through the generated MigrationContext object where child flows need them.
What it does not change
Variable optimization is not a business-logic rewrite. It does not remove real workflow actions, convert unsupported actions, change email recipients, or make a workflow production-ready without UAT.
It also should not be used to hide missing content. If an email, approval, or SharePoint update depends on a variable, the converted field still needs to resolve to the correct runtime value after import.