How large workflows, child flows, and nesting are scored

Large workflow scoring

The action estimate is calculated from the detected source structure plus generated helper actions such as variable initializers. Analyzer-only branch and case rows are removed from the emitted-action estimate so the number is closer to the cloud-flow package that would be generated.

When the estimate approaches the 500-action platform limit, Flow Migrator recommends treating the workflow as a refactor candidate even if the individual source actions are mostly supported.

• 350+ estimated actions: review the workflow shape.
• 450+ estimated actions: high risk; consider splitting or moving repeated logic into child flows.
• 500+ estimated actions: blocker-level risk for a single cloud flow.

Nesting and branch-depth scoring

Source nesting depth is measured from the original workflow hierarchy. The generated flow may be flatter than the source, but deep source nesting is still a sign that the workflow may exceed Power Automate limits or become difficult to maintain.

Deep nesting is common in workflows that combine state machines, nested conditions, parallel branches, switch cases, and task outcome handling.

Child workflow dependency scoring

For Nintex Start workflow actions, Flow Migrator reads the target workflow name where available and groups repeated calls by child workflow target. This makes shared reusable workflows visible during analysis.

A portfolio with many parent workflows calling the same child workflow should usually convert that child once and wire the parent flows to it, rather than duplicating the same logic into every parent.

• The limit panel shows total child workflow calls.
• The details show unique child workflow targets and the steps that call them.
• Packaging guidance recommends parent/child solution grouping when dependencies are present.