Experimental parent/child solution package for oversized workflows
The experimental parent/child solution package is designed for workflows that are too large or too deeply nested to export as a single Power Automate cloud flow. It is a remediation accelerator: it generates a solution-aware parent flow, child-flow segments, context handoff, and quality checks, while keeping human validation visible.
When the experimental package appears
Flow Migrator shows the experimental solution option when the analysis or export path detects a hard Power Automate limit risk. Common triggers include generated action count above the single-flow limit, source or generated nesting beyond the safe threshold, too many variables, too many switch cases, or expressions and URLs that need review.
Normal export is still the preferred path for workflows that fit into one cloud flow. The experimental package is for workflows where forcing everything into one flow would create an import failure or an unmaintainable result.
- Use normal export for standard-sized workflows.
- Use the experimental package for workflows that exceed hard single-flow limits.
- Use the refactor plan when the team needs an architecture workplan before generating a package.
What it generates
The package is generated as a Power Platform solution, not a legacy My flows import package. That matters because parent and child cloud flows need to live in a solution so the parent can call the child flows and the environment can manage connection references.
The output includes a parent flow, generated child flows, connection-reference metadata, import guidance, a refactor plan, and a MigrationContext JSON handoff pattern so child flows can receive and return shared state.
- Parent flow orchestration.
- Base child-flow segments for action-count reduction.
- Additional nested-section child flows when deep branches need extraction.
- Context JSON input and response pattern.
- Visible TODO or review notes where human validation is required.
What the quality check does before download
Before the ZIP is returned, Flow Migrator audits the generated solution for common import and save failures. The goal is to block known-bad output before a user spends time importing it into Power Platform.
The quality check is intentionally strict. If a hard platform issue remains, Flow Migrator should fail the package generation and explain the blocker instead of giving the user a solution that cannot be saved.
- Checks action count per generated flow.
- Checks generated nesting depth.
- Checks invalid runAfter references and missing action references.
- Checks overlong action descriptions.
- Checks whether key source action families disappeared without generated actions or review steps.
What still requires human validation
Experimental output is not a production guarantee. The generated solution is meant to get architects and makers past the first structural limit problem, not replace UAT, connector testing, or business-owner review.
Pay special attention to connector references, SharePoint file dependencies, approval outcome branches, HTTP calls, document-generation steps, external systems, and any TODO notes left by the converter.
How to explain it to a customer
A clear way to position the feature is: Flow Migrator can identify when a Nintex workflow is too large for a single Power Automate flow and can generate an experimental parent/child solution package to accelerate the refactor. The output still needs review, but the team is starting from a structured solution instead of a blank rebuild.
That distinction matters in enterprise pilots. It avoids promising one-click modernization while still showing real automation value for workflows that would otherwise be blocked by platform limits.