Convert document (Word to PDF)

What it does

This action works with SharePoint list items, files, folders, metadata, content approval, or permissions. The key migration inputs are the target site, list or library, field mappings, and any dynamic item identifiers.

How Flow Migrator maps it

Flow Migrator maps this to Convert Word Document to PDF + Create file using Word Online (Business) / SharePoint. Maps Nintex Convert document to Word Online (Business) Convert Word Document to PDF and SharePoint Create file. Preserves the source URL, output URL, source library, overwrite intent, and Nintex error variables. The destination library URL stored in an on-premises workflow constant must be replaced with its Microsoft 365 value before production activation. Flow Migrator can preserve and generate the core mapping, but this action should be reviewed after import.

Common migration issues

• Review the generated action after import because some Nintex behavior does not map one-to-one to Power Automate.
• Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

Validation checklist

1. Review this item before export or immediately after import.
2. Open the generated flow and confirm the action card imported correctly.
3. Validate connection references and required settings before running the flow.
4. Test with representative source data from the original workflow.
5. Confirm site/list/library names and complex field mappings in the target tenant.