The Analyze page can export the detected workflow mapping as a CSV or a branded PDF. Use the CSV for detailed tracking and the PDF for stakeholder-ready migration summaries.
5 min readUpdated May 22, 2026reportsCSVPDF
Quick answer
In shortExport a workflow analysis report for migration planning, ticketing, stakeholder review, or customer evidence.
Most likely causeUse the CSV when you need a step-level mapping table for backlog planning, remediation tickets, or spreadsheet review. It includes sequence, Nintex step, connector, original step ID, status, Power Automate target, target connector, and notes.
What to do nextMake the fix, generate a new package, and import the new ZIP instead of retrying the old one.
When to use CSV vs PDF
Use the CSV when you need a step-level mapping table for backlog planning, remediation tickets, or spreadsheet review. It includes sequence, Nintex step, connector, original step ID, status, Power Automate target, target connector, and notes.
Use the PDF when you need a branded executive or workflow-owner summary. It includes workflow summary, coverage counts, connectors, risk flags, Power Automate limit-risk items, child workflow dependencies, and recommended next steps.
How filenames are chosen
PDF filenames are based on the workflow name when one is available, with a fallback to the source file name. This makes reports easier to store in migration folders or attach to customer work items.
If the workflow name changes after re-analysis, generate a new report so the filename and report title stay aligned.
What to include in a migration packet
The PDF summary for the workflow owner.
The CSV mapping for the delivery team.
The exported Power Automate package when the workflow is ready for import.
A list of partial and high-risk limit items that need validation.
Related articles
Keep reading the next most relevant guides for this workflow pattern.
