Workflow migration
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.
Coverage reportSupported / partial / unsupported
Draft structureScopes, branches, key steps
ZIP export (Pro)When supported, importable package
SupportsNintex Automation Cloud · Nintex for SharePoint (.nwf/.wf, including on‑prem exports) · Power Automate
Product walkthrough
See the workflow in action.
Upload → Analyze → Configure → Export. The Configure steps cover the few values needed before export.
Real app walkthrough
Overview
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.
What you get
Files you can use to scope the job
Coverage first
supported / partial / unsupported
Structured draft
scope, branching, key steps
4-step guided flow
upload → analyze → configure → export
UploadAnalyzeConfigureExport
What you get
Outputs you can use right away.
A report for planning, a draft structure for rebuilding, and export files when supported.
Action-level coverage
Know where the work is
Structure-first draft
Start from structure, not a blank page
Less rebuilding
Less manual work
Report
Coverage report
See, step by step, what maps cleanly, what needs work, and what does not.
- Supported, partial, or unsupported for each action
- Why a step is blocked and what to use instead
- A faster way to size the work
Draft
Draft structure
Get a usable starting structure instead of rebuilding the whole flow by hand.
- Scopes, branching, and key steps laid out for you
- Makes team review easier
- Keeps the manual work obvious
Export (Pro)
ZIP export
For supported workflows, download a Power Automate package you can import.
- 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.
Process
A short workflow.
Upload, analyze, configure, and export. The order stays the same every time, which makes reviews easier.
Upload
Analyze
Configure
Export
Go from a Nintex export to a report your team can actually use.
01
Upload
Start with the workflow export.
Upload a Nintex export (.nwf, .wf, or a Nintex Automation Cloud export ZIP) to begin the guided migration wizard.
02
Analyze
See coverage before you commit.
Review supported, partial, and unsupported actions so effort, blockers, and risk are visible immediately.
03
Configure
Complete the guided configuration.
Map the required trigger and SharePoint settings, plus any optional recipient changes needed for export.
04
Export
Generate the Power Automate package.
Download the package when supported, then import it into Power Automate and validate any flagged steps before production use.
Inputs
- Nintex export
- Target Power Automate environment access
- Connector mapping (as needed)
Outputs
- Coverage report
- Structured draft plan
- Exportable package when supported (Pro)
Built to cut down on rechecking and copy work.
The goal is simple: give you something concrete to estimate and rebuild from.
Who it's for
Made for the people doing the migration.
Useful for admins, consultants, and project teams.
Power Platform Admins
Keep migrations consistent across environments and connector choices.
- Coverage reports you can use for planning
- Draft structure that helps builders start faster
- Fewer surprises when work moves between teams
SharePoint Admins
See where the workflow depends on SharePoint and what will need manual work.
- Spot dependencies and heavier workflows early
- See likely Power Automate equivalents with notes
- Spend rebuild time only on the steps that need it
Consultants / MSPs
Get to scope faster and hand clients something concrete.
- Faster discovery across a portfolio
- Reports clients can review and sign off on
- A process you can reuse across tenants
Also useful for
Security & ComplianceCenter of ExcellenceIT LeadershipDelivery / PMO
Useful when you have a lot of workflows.
The outputs are easy to review with other teams and specific enough for builders to use.
Pricing
Analyze free. Pay when you need export output.
Run a free workflow analysis first. When you are ready to generate packages, buy a single export or a migration pack.
Free analysis
Upload a workflow and see supported, partial, and unsupported steps before you spend anything.
$0
Analysis
Workflow analysisCoverage report
- Workflow analysis grouped by connector, supported status, and review need.
- Trigger detection, flow outline, and required settings review.
- Compatibility notes before you buy an export package.
- Export packages require a paid workflow credit or team plan.
Migration Pack
The practical starting point for most small Nintex cleanup projects.
$1,999
10 workflow exports
Credits are consumed only when a new workflow package is successfully generated.
10 exportsM365 discoverySaved history
- Ten workflow export credits for a small migration project.
- Re-export the same workflow without consuming another credit.
- Microsoft 365 assisted discovery for SharePoint sites, lists, and libraries.
- Run history, notes, and evidence for handoff or review.
Single workflow and wave packs
Need one workflow or a larger batch? Single workflow exports are $399, and Wave Packs include 50 workflow exports for $7,500.
Team / consultant plan
Teams and consultants can use annual workspace access starting at $9,500/year for larger-volume migration work.
FAQ
Common questions.
Short answers to the questions admins and migration teams ask most.
What does the analysis include?
Flow Migrator analyzes your Nintex export and produces an action‑level coverage report (supported / partial / unsupported), plus a clean flow outline so you can scope and prioritize before rebuilding anything.
Is this fully automatic?
When supported, Flow Migrator can generate an importable Power Automate package (Pro). When it isn’t, you still get the coverage report + draft structure so you’re not rebuilding from a blank page—you’re only rebuilding what’s missing.
When do I need Pro?
Upgrade when you need ZIP downloads (when supported), saved run history, more detailed blocker notes, and retained uploads while a migration is in progress.
Which Nintex formats are supported?
Nintex Automation Cloud export ZIPs and Nintex for SharePoint (.nwf/.wf) exports are supported, including on-prem SharePoint workflows. The analysis report flags partial and unsupported steps, and exported flows may require review for those items.
What if my workflow is unsupported or partial?
Run a workflow analysis first—then send us the export and the coverage report (especially the unsupported actions). Real workflows are the fastest way for us to expand compatibility. Even before support is added, the report tells you exactly what needs manual rebuild work.
Do you retain my uploads?
On the Free tier, files are processed to generate your report and are not retained after processing. On Pro, uploads and run history may be retained up to 6 months by default while a migration project is active.
Can you help estimate migration scope and effort?
Yes. The report shows what maps cleanly, what needs review, and what has to be rebuilt. If you’re migrating a portfolio, contact us and we can help you estimate effort across workflows.
Can we pay via invoice/PO or need admin provisioning?
Yes—if you need invoice/PO or admin provisioning, reach out after signing in and we’ll coordinate billing and access.
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.
Prefer email? Contact us and we’ll respond quickly.