How Nintex Assign to-do task maps to Power Automate
A Nintex to-do task is more structured than a plain notification. It usually carries assignee information, reminder behavior, task metadata, and sometimes a custom content type or task form. That is why the mapping is closer to a human approval step than to an email.
Why this is not just 'send an email'
To-do task steps represent assigned work, not just notification. The workflow often expects a person to act, complete, delegate, or resolve something before the process continues.
That is why the right automatic destination is usually Start and wait for an approval rather than a static placeholder email.
What the current mapping preserves
The best-effort conversion path pulls forward the assignee, title, description, and review-type intent when those are visible in the source export. That gives the target flow a human-task shape that users can refine after import.
It is a pragmatic mapping, not a claim that every custom Nintex task form field becomes a first-class Power Automate form automatically.
- Assignee / approver intent
- Task title and description
- Review-style human step in the destination flow
When you should still review the result closely
Review after import if the source task depends on a custom content type, custom task-form fields, or specialized escalation rules. In those cases the human-task shape may be correct while the business-specific form experience still needs refinement.
This is a much better outcome than leaving the task entirely unsupported, but it is still a best-effort task mapping.