Generate cleaner packages, export reports, fix common import failures, and understand what preflight is checking.
If a package downloads but fails to import, the error is usually specific and fixable. These guides cover package generation, branded reports, preflight checks, and the import errors users hit most often.
Articles in this category
Browse all guides in Export & import.
How to download CSV and PDF analysis reports
Export a workflow analysis report for migration planning, ticketing, stakeholder review, or customer evidence.
What export preflight checks before package download
Understand the checks Flow Migrator runs before letting a generated Power Automate package download.
How to generate and import your first package
Use Analyze and Required settings to reduce surprises, then validate the imported package in Power Automate before calling the migration done.
How to fix duplicate action name errors on import
Resolve 'The template action names must be unique' errors by re-exporting after the naming review pass and checking deep branches for collisions.
How to fix nesting-limit errors on import
Power Automate allows up to eight levels of nested actions; trivial wrapper scopes often need to be flattened before export.
How to fix self runAfter errors on import
Resolve 'The action cannot be itself' errors by checking flattened wrapper scopes and repaired action dependencies.
How to fix 'Required settings incomplete' export errors
If export still says a list or library is missing, the problem is usually stale analysis data or reference-name mismatch, not the idea of the site URL itself.