How to start your first workflow analysis
Your first run should answer one question quickly: is this workflow mostly supported, partially convertible, or likely to need manual rebuild work? The goal is not to perfect every setting on the first pass. The goal is to get a truthful report and learn what the workflow depends on.
Start with the right file type
Flow Migrator works best when the source export is complete and current. For Nintex for SharePoint, that usually means a .nwf or .wf export. For Nintex Automation Cloud, use the export ZIP rather than a screenshot or copied designer JSON.
If you are unsure which wizard path to use, choose the path that matches the source artifact you actually have today. You can always re-run the analysis after collecting a cleaner export.
- Single workflow is best when you want step-by-step review and export.
- Batch upload is better when you are triaging a portfolio and want coverage at scale.
- A clean export is more valuable than a long setup session with a poor source file.
Use Analyze as a scoping screen first
On an initial run, treat the Analyze screen as a scoping tool, not a final engineering decision. Look at the supported, partial, and unsupported counts first. Then scan the partial items to see whether they are light review items or true blockers.
If the workflow contains heavy SharePoint, approval, or document-generation patterns, expect one more pass through Required settings before export. That is normal. The first run is still valuable because it reveals the shape of the workflow and the likely conversion path.
- High supported count usually means you can move quickly into configuration and export.
- A small number of partial items often means a review pass, not a full rebuild.
- A few unsupported or partial items do not automatically make the workflow a bad candidate.
Do not try to solve every required field on the first pass
Required settings exist to make exported packages cleaner and more importable. They are not there to make you memorize the workflow. The fastest approach is to review the missing list, fill what you know, and come back after the first analysis if needed.
Optional settings are similar. If the workflow has many email actions, the product will usually surface grouped overrides so you can change the repeated target once instead of editing dozens of rows one by one.
- Upload the export and wait for Analyze to finish.
- Review the trigger and the partial items first.
- Open Required settings only after you know which SharePoint references and task options the workflow needs.
- Export only after the required items are truly complete.