Convert Nintex to Power Automate—faster (V1)
Flow Migrator V1 generates an action-by-action readiness report and a draft Power Automate flow from your Nintex export. If the conversion isn’t fully automatic for your workflow yet, you still get a structured outline that usually saves hours.
Free AnalyzerCoverage reportZIP export (when supported)
Best supported in V1
Nintex Automation Cloud exports (ZIP containing
workflows/<GUID>/design.json) are the primary supported path. Nintex for SharePoint on‑prem exports (.nwf/.wf) are Experimental (not officially supported yet).What you get
- A connector-grouped action list (supported / partial / unsupported), so you know what will import cleanly.
- A human-readable flow outline to rebuild only the missing pieces.
- An importable Power Automate ZIP package when your workflow is within current V1 coverage.
V1 scope (and limitations)
Flow Migrator V1 is intentionally scoped to common migration patterns first. You should expect some manual work for complex branching, uncommon actions, or niche connectors.
Why it still helps even when it’s not 100%
The slow part of migrations is usually figuring out structure, data sources, and where each action goes. Flow Migrator’s output gives you a starting draft plus an explicit “what to fix” list.
On‑prem exports
Nintex for SharePoint 2016/2019 exports (
.nwf/.wf) are Experimental (not officially supported yet). You can analyze them today. Package generation may be available in some environments as an experimental feature, but you should expect placeholders and connector rework.Supported connectors (growing)
V1 focuses on the most common Microsoft 365 migration targets. Coverage varies by action.
SharePoint Online
List items (create/update), fields mapping, and common list-driven triggers.
Approvals
Task/approval-style steps mapped best-effort to Approvals patterns.
Office 365 Outlook
Send email notifications where the Nintex action maps cleanly.
Teams + OneDrive
Basic Teams posting and common file operations (varies by workflow).