Nintex Automation Cloud
Start with a workflow export ZIP. Review connectors, action mappings, and the work needed in your destination.
Explore this migration pathFlow Migrator · by Horton Scientific
See what your Nintex migration will take.
Get a clear starting point for Power Automate.
Analyze a Nintex export to find supported mappings, configuration needs, and gaps. Build your plan, then generate supported packages when you’re ready.
Your analysis is free with an account. Explore the sample without signing up.
Fit and scope
Start with your migration.
Choose the guidance that fits your source environment or the project you need to deliver.
Nintex for SharePoint
Bring a .nwf or .wf export. Check list dependencies, identities, start conditions, and the work that remains.
Explore this migration pathConsultants and migration teams
Define a representative pilot, agree on responsibilities, and build a defensible delivery estimate.
Explore this migration pathCompare conversion, rebuilding, and redevelopment · Share the buyer’s brief
An actual product example
Follow one workflow through the app.
Explore the anonymized Daily Operations Summary example. Start with the analysis, then inspect the settings and export screen. Select a step to read it at your own pace.
Actual app screens
What to review
This example lists seven supported steps and includes a loop-volume warning. Review action coverage and platform findings together.
What comes next
Open Required settings to review trigger behavior and destination requirements. Coverage alone does not verify runtime behavior.
Review the detected steps, action coverage, and platform-limit checks before continuing.
Anonymized product demonstration. Screens show the review process; results and export allowances depend on your workflow and account.
What the example shows
The sample analysis lists seven supported steps and includes platform checks. The settings screens show the decisions reviewed before package generation.
What still needs validation
The export screen has validation pending. These screenshots do not show a completed import or a tested production workflow. Credit allowances depend on your account; this sample account shows unlimited access.
Explore the interactive sample report · Get the example files and validation worksheet
What you get
Replace guesswork with a reviewable starting point.
Use the report, draft, and supported output to move the project forward.
Scope the conversion
See the detected trigger, actions, connectors, and steps that need attention in one coverage report.
Choose a useful pilot and give the project a clearer scope.
Prepare the destination
Inspect the generated draft and work through the trigger, destination, and connection settings.
Give builders and reviewers a concrete starting point.
Generate supported packages
Use your export access to create a Power Automate package for a workflow that reaches an exportable state.
Take conversion output into your implementation and test environment.
The process
From source export to a reviewed starting point.
- 01
Upload
Start with a Nintex Automation Cloud export ZIP or a Nintex for SharePoint .nwf or .wf export.
- 02
Analyze
Review the detected workflow, action coverage, and flagged gaps. Check the relevant compatibility notes.
- 03
Review and configure
Confirm trigger behavior, map destinations, and resolve the required settings for your workflow.
- 04
Generate
Create a supported package with your available export access. Use the validation checklist for the next stage.
Start free analysis
Sign in or create a free account to begin.
Planning resources
Answer the questions around the conversion.
Scope and cost
Model the project effort
Compare manual and assisted work with visible assumptions. Calibrate the estimate after a pilot.
Open ROI calculator Complex workflowsReview refactor options
Explore the parent and child solution starting point for workflows that exceed supported platform limits.
Explore limit remediation Your first workflowBuild your evaluation plan
Choose your source and preparation stage. Get a checklist for the export, dependencies, and tests your pilot needs.
Plan the first evaluationNeed to review uploaded data or optional tenant connections? Read security and data handling.
Pricing
Analyze free. Choose export capacity when ready.
Start with one workflow, then choose the export allowance that fits your project.
Free analysis
$0analysis
Review coverage and the work flagged for attention before using export capacity.
Start free analysisSingle workflow export
$49one workflow
One export credit for a new workflow. A focused starting point for a supported package.
View export optionsMigration Pack
$39910 workflow exports
Ten export credits for a small project. Re-export the same workflow after adjusting settings without another credit.
View export optionsEstimate the cost and allowance for your workflow count
How export credits work
A credit is used when a package is successfully generated for a new workflow. Re-exporting that workflow does not use another credit. If package generation fails, no credit is spent.
For a larger project, the Wave Pack includes 50 exports for $1,499. The team / consultant plan is $2,999/year with 150 included exports; additional 50-export bundles are $999.
Compare all options and termsBefore you start
A clear answer to the next question.
What do I need to start?
Create a free account and upload a Nintex Automation Cloud export ZIP or a Nintex for SharePoint .nwf / .wf export. You do not need to connect your live tenant for export-based analysis. Explore the sample first or check format and action compatibility.
When do I pay?
Analysis is free. Package generation uses export access, such as workflow credits, a migration pack, or a team plan. Estimate the capacity for your project and check your account for any existing allowance.
How do export credits work?
A credit is consumed when a package is successfully generated for a new workflow. Re-exporting that same workflow after adjusting settings does not use another credit. Failed package generation does not spend a credit.
What if the report flags a gap?
Use the step notes to identify configuration or rebuilding work. The compatibility reference explains mappings, and the evaluation guide helps you record the work. Contact us if a finding needs interpretation.
How are workflow files and saved history handled?
Saved history and batch-upload features can retain workflow files and results. Review data handling and the privacy policy, and discuss any restricted-data or retention requirements before uploading.
Can you help with a larger project or invoice billing?
Yes. Talk through the scope for a portfolio, enterprise pilot, invoice, or purchase order. Use the pilot plan and ROI calculator to prepare the discussion.
Begin with a pilot
Evaluate one workflow before planning the wider project.
Bring a representative Nintex export. Review the conversion findings and decide what to configure, generate, or rebuild next.
Free account required. Package generation depends on workflow support and your export allowance.