What the public evidence shows
The public sample demonstrates a simple Automation Cloud mapping, not a Nintex for SharePoint migration. Use your own representative SharePoint export to establish fit for this path.
Inspect the evidence and worksheetNintex for SharePoint
Assess Nintex for SharePoint .nwf and .wf exports, review list and identity dependencies, and plan the configuration and testing needed for Power Automate.
Free account required for your own analysis. Package generation depends on workflow support and your export allowance.
Use an accepted Nintex for SharePoint workflow export, including exports from on-premises SharePoint. Keep a record of its source list, expected behavior, and dependencies. Review the definition for sensitive values before uploading it.
Review data handling before uploadingMake the scope explicit
Identify destination lists and libraries, field types, lookup values, and attachment behavior. Moving the workflow does not itself copy the underlying SharePoint content or create every dependency.
Record when the workflow should run, variable defaults, people and groups, approval outcomes, and permissions. Compare these with the generated draft and destination settings.
Plan form changes separately. InfoPath and Nintex form conversion belongs to Form Migrator; workflow analysis does not establish that a task form or custom behavior has been rebuilt.
Choose a workflow with a known list and a small set of test items. Verify its start conditions, field changes, attachments, identities, branches, and failure behavior in a suitable destination test environment.
The public sample demonstrates a simple Automation Cloud mapping, not a Nintex for SharePoint migration. Use your own representative SharePoint export to establish fit for this path.
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