See how Flexi tasks, to-do tasks, child workflow calls, and reusable workflow dependencies are handled in conversion.
Task-centric and child-workflow-heavy migrations often look more complex than they really are. This section explains how approval patterns are recognized, how child workflow targets are shown, and where manual review still matters.
Articles in this category
Browse all guides in Approvals & tasks.
How to track child workflow dependencies in Analyze
Understand child workflow call counts, unique reusable child workflows, and why Start workflow rows now show their target names.
How Flexi tasks map to Power Automate
Multi-outcome Nintex approval patterns can often be recognized as one approval pattern repeated across branches rather than many unrelated partials.
How Nintex Assign to-do task maps to Power Automate
To-do tasks are best mapped into approval-style human review steps, but custom Nintex task forms still deserve post-import review.
When child workflows stay partial
Calling another workflow is often recognizable, but wiring a real child flow still depends on your target architecture and tenant strategy.