Consultants and migration teams
Use representative Nintex exports to plan a migration pilot, define the remediation backlog, agree on responsibilities, and choose export capacity for client delivery.
Free account required for your own analysis. Package generation depends on workflow support and your export allowance.
Agree with the customer on permission to use workflow exports and on data handling before uploading them. Select typical and difficult workflows, with known owners, dependencies, and expected outcomes. Keep client projects and their access requirements clear.
Review data handling before uploadingMake the scope explicit
Distinguish assessment evidence, generated packages, configuration, remediation, import, testing, and acceptance. Assign each activity to the customer, implementation partner, or another agreed owner.
Record pilot effort by activity and use it to calibrate the ROI calculator. Include unsupported behavior, dependencies, connector requirements, and testing instead of treating an action-coverage percentage as a savings percentage.
Use the existing workflow-count chooser to compare one-time packs and annual Team access. Confirm workspace access, billing, and customer-specific terms before including them in a proposal.
Use the enterprise pilot plan to select 5–10 representative workflows. Agree on acceptance criteria, record manual work and destination test results, and review the remediation backlog before expanding delivery.
Existing public demonstrations explain the review process and a simple synthetic mapping. They do not establish client delivery times or average savings. Add your own observed pilot evidence to the buyer’s brief.
Inspect the evidence and worksheetUse the analysis report, remaining-work list, pilot results, and current commercial terms to explain the proposed scope. The buyer’s brief brings those decisions together.
Share the buyer’s brief
