Copy file / Move file

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 Copy file or Move file using SharePoint / OneDrive for Business / Google Drive. Maps file movement where the source and destination connector are known. NAC SharePoint copy_or_move_file is converted to a file-property lookup followed by native SharePoint Copy file or Move file. Validate folder paths, overwrite behavior, and source-delete semantics after import. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• 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. Open the generated flow and confirm the action card imported correctly.
2. Validate connection references and required settings before running the flow.
3. Test with representative source data from the original workflow.
4. Confirm site/list/library names and complex field mappings in the target tenant.