Move from
Nintex to Power Automate with less guesswork.
Upload a Nintex export (.nwf, .wf, or a Nintex Automation Cloud export ZIP) and get a report that shows what converts cleanly, what needs manual work, and whether a package can be generated.

See the workflow in action.
Upload → Analyze → Configure → Export. The Configure steps cover the few values needed before export.

See the rebuild work before you start.
Upload a Nintex export, review the coverage report, and get a Power Automate draft structure. When export is supported, you can also download a package.
- Upload your Nintex export
- Analyze supported, partial, and unsupported steps
- Complete the short guided configuration
- Export when supported (Pro)
*Export availability depends on workflow patterns and connector support.
Outputs you can use right away.
A report for planning, a draft structure for rebuilding, and export files when supported.
- Supported, partial, or unsupported for each action
- Why a step is blocked and what to use instead
- A faster way to size the work
- Scopes, branching, and key steps laid out for you
- Makes team review easier
- Keeps the manual work obvious
- ZIP package for import
- Less copy-and-rebuild work
- You still get coverage and structure when export is not available
*Export availability depends on workflow patterns and connector support.
A short workflow.
Upload, analyze, configure, and export. The order stays the same every time, which makes reviews easier.
- Nintex export
- Target Power Automate environment access
- Connector mapping (as needed)
- Coverage report
- Structured draft plan
- Exportable package when supported (Pro)
The goal is simple: give you something concrete to estimate and rebuild from.
Made for the people doing the migration.
Useful for admins, consultants, and project teams.
- Coverage reports you can use for planning
- Draft structure that helps builders start faster
- Fewer surprises when work moves between teams
- Spot dependencies and heavier workflows early
- See likely Power Automate equivalents with notes
- Spend rebuild time only on the steps that need it
- Faster discovery across a portfolio
- Reports clients can review and sign off on
- A process you can reuse across tenants
Start simple. Upgrade when needed.
Run a free workflow analysis. Upgrade to Pro when you need ZIP downloads, saved run history, and more detailed blocker notes.
- Workflow analysis (grouped by connector, supported/partial/unsupported).
- Trigger detection + flow outline.
- Best‑effort target extraction (site/list, recipients, etc.).
- Uploaded files are processed to generate your report and are not retained after processing on the Free tier.
- Generate an importable Power Automate ZIP when the workflow is supported.
- More detailed blocker notes and suggested fixes for partial actions.
- Saved run history + uploaded exports retained up to 6 months by default.
- Early access to new features and coverage updates.
Common questions.
Short answers to the questions admins and migration teams ask most.
What does the analysis include?
Is this fully automatic?
When do I need Pro?
Which Nintex formats are supported?
What if my workflow is unsupported or partial?
Do you retain my uploads?
Can you help estimate migration scope and effort?
Can we pay via invoice/PO or need admin provisioning?
Start with a workflow analysis.
Start with analysis so you can see the work before you commit. If something is unsupported, you still know exactly where the manual rebuild is.

