Evaluation guide
Start with one representative Nintex export. Use the findings to separate conversion output, remaining implementation, and destination testing.
Free account required for your own analysis. Package generation uses export access. The example files below are free to inspect.
Plan the first workflow
Choose your source and preparation stage. Get a practical checklist for the workflow you want to evaluate.
Your choices stay on this page. Download the plan to keep it.
Your next step
Identify the source product and export format. The two guided paths below cover Automation Cloud and Nintex for SharePoint.
Source to confirm · Preparation checklist
Confirm the source product and use its original workflow export. Choose a workflow with expected behavior you can explain.
Review supported, partial, unsupported, and unknown findings. Record settings, remediation, and manual work before choosing export capacity.
Arrange an appropriate Power Platform test environment for import and execution. You can analyze the export before that environment is ready.
When findings and settings are resolved, use export access to generate a supported package. Import it, configure connections, and compare relevant paths and outputs with the source behavior.
Log configuration, rebuilding, import fixes, testing, observed results, and remaining work in the validation worksheet. Use that evidence to decide the next migration wave.
Analysis is free with an account. Review the findings before choosing export capacity.
A reproducible synthetic example
“Evaluation Checkpoint” is a deliberately simple test fixture created for this demonstration. It contains a manual start and three log actions. It is separate from the Daily Operations Summary app screenshots and contains no customer workflow data.
The current parser and converter read the source ZIP and preserve those three literal messages, in order, in generated Compose actions.
Coverage: 3 supported · 0 partial · 0 unsupported. This result applies to this fixture only.
Download this synthetic example in the app’s PDF and CSV report formats. Both include the manual trigger and three actions; destination import and execution remain to be tested.
These are local artifact checks, with live import and execution still pending. This fixture has no business connectors, approvals, custom forms, or complex expressions. It does not demonstrate their conversion, a customer outcome, or a time-saving result.
To continue the example, import the solution into a suitable test environment, review the trigger, run it, and compare the three Compose outputs with the source messages. Record any changes and results in the worksheet.
A more involved synthetic example
“Approval Review Example” adds a business connector, outcome routing, and a counted loop. It is a reproducible test fixture with reserved example addresses. No customer workflow data or destination results are used.
The parser detects 7 source nodes, including branch containers: 7 supported, 0 partial, and 0 unsupported. This coverage result applies only to this fixture.
Replace the reserved approver and SharePoint URL, select a test list with a Title column, and configure the Approvals and SharePoint connections and permissions. Review destination licensing and trigger behavior before importing.
Test both outcomes in a suitable environment. Confirm one item and two checkpoints on Approve, no item on Reject, and the behavior of failed connections, missing permissions, timeouts, and repeat submissions. Record the observed outcomes and every manual change.
These downloads demonstrate local parsing, conversion, and packaging. They do not establish live approval behavior, successful item creation, customer migration results, or time savings.
Record your destination checks in the validation worksheetYour own workflow
Pick a workflow you understand and can test. Include a typical case and a more difficult case before extrapolating to a portfolio. Check sharing permissions and remove sensitive literal values from a copy.
Review supported, partial, and unsupported actions alongside trigger and connector notes. Record what must be configured or rebuilt. Action coverage does not establish runtime equivalence.
Confirm required and optional settings, check export access, and generate a supported package. A successful generation creates an artifact; import and execution still need validation.
Use a suitable test environment. Review connection references, permissions, destinations, trigger behavior, expressions, exception paths, and representative input/output pairs before production use.
Track analysis, configuration, manual rebuilding, import fixes, and testing separately. Use those observations in the ROI calculator and migration plan, including work that remains.
The CSV worksheet has space for expected behavior, observed results, manual work, actual effort, and sign-off. Fill it in with your own evidence; no results are assumed.
