Software output
Detected workflow structure, coverage findings, configuration requirements, reviewable draft, and supported generated package output. Partial and unsupported behavior remains visible for a decision.
Flow Migrator · by Horton Scientific
Buyer’s brief
A decision brief for your Nintex migration.
Use this overview with your analysis report and completed pilot worksheet to discuss scope, responsibilities, and export capacity with a manager, client, or purchasing team.
Share this page’s URL or use your browser’s print dialog to save a PDF. This overview is not a project quote, security certification, or guarantee of conversion.
1. What you are evaluating
Flow Migrator analyzes accepted Nintex Automation Cloud ZIPs and Nintex for SharePoint .nwf / .wf exports. It reports action mappings and findings, provides a draft to review, and generates supported Power Automate packages when the workflow reaches an exportable state and the account has export access.
Analysis is free with an account. Check current compatibility for the source and actions in your project. Forms, SharePoint content, and a redesigned business process require separate scope decisions.
2. Agree on the division of work
Implementation responsibility
Your team or partner confirms destinations and connections, resolves gaps, rebuilds behavior where needed, imports the package, and validates triggers, identities, data, branches, and failure paths.
3. Choose capacity after checking fit
| Option | Published price | Included exports | Purchase type |
|---|---|---|---|
| Single workflow export | $49 | 1 | One-time purchase |
| Migration Pack | $399 | 10 | One-time purchase |
| Wave Pack | $1,499 | 50 | One-time purchase |
| Team / consultant | $2,999 / year | 150 annually | Annual subscription |
A credit is used for successful first package generation of a new workflow. Re-exporting that workflow uses no additional credit; failed generation uses no credit. Additional Team bundles provide 50 exports for $999, arranged separately.
Use the workflow-count capacity chooser for your scope and confirm current terms at purchase. Include implementation effort and destination licensing where required; tax, services, and negotiated terms are outside that estimate. Ask about invoice or purchase-order requirements before committing.
4. Decide what a successful pilot must prove
- Select representative workflows and record the expected behavior, dependencies, and business owner.
- Attach the actual analysis report and list the configuration, partial mappings, and rebuilding work.
- Record generated artifacts, destination import results, manual changes, and representative execution tests separately.
- Record effort by activity, assign the remaining work, and obtain acceptance before expanding to a portfolio.
The public synthetic example has passed local artifact checks; live import and execution have not been performed. It establishes neither average savings nor success for your workflow. Use the evaluation guide, enterprise pilot plan, and editable ROI model with your own observations.
5. Resolve the approval questions
- Data handling: workflow definitions can contain business information. Saved history and batch features can retain files and results. Review security and data handling and the privacy policy; agree on restricted-data and retention requirements before uploading.
- Access: export-based analysis does not require a live tenant connection. Optional connected discovery is a separate access decision. Import and testing require appropriate destination permissions, connections, and licensing.
- Ownership: name the implementation, testing, acceptance, and ongoing support owners. Discuss scope and commercial questions with Horton Scientific before treating this brief as an approved delivery plan.
Questions: support@hortonscientific.com · Discuss pilot scope · Discuss purchasing