Refactor solution package for oversized workflows
The refactor solution package is designed for workflows that are too large or too deeply nested to export as a single Power Automate cloud flow. It creates a solution-aware parent flow, ordered child flows, context handoff, and quality checks while keeping human validation visible.
When the refactor package appears
Flow Migrator recommends the refactor solution option when analysis or export detects hard Power Automate limit risk. Common triggers include generated action count above the single-flow limit, generated nesting beyond the safe threshold, too many variables, too many switch cases, or expressions and URLs that need review.
Normal export is still preferred for workflows that fit into one cloud flow. The refactor package is for workflows where forcing everything into one flow would create an import failure, a save failure, or an unmaintainable result.
- Use normal export for standard-sized workflows.
- Use the refactor package for workflows that exceed hard single-flow limits.
- Complete Required and Optional settings before generating the package.
- Treat the output as a structured UAT artifact, not an automatic production cutover.
What it generates
The package is generated as a Power Platform solution, not a legacy My flows import package. 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, ordered child flows, connection-reference metadata, import guidance, and a MigrationContext handoff pattern so child flows can receive and return shared state. Flow names are prefixed in review order, such as 00.00 Parent, 01.00 Child, and 01.01 Child.
- Parent flow orchestration.
- Child-flow segments for action-count and nesting remediation.
- SourceItem input for the original trigger record.
- MigrationContext 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 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 context handoff between parent and child flows.
- Checks whether important source action families disappeared without generated actions or review steps.
What still requires human validation
Refactor output is not a production guarantee. The generated solution is meant to get architects and makers past the 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.