Copy item

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 Get file properties or filtered Get files + Copy file (document libraries); Get item + Create item (lists) using SharePoint. For document libraries, maps ID lookups to Get file properties + Copy file and non-ID lookups to filtered Get files (properties only) + a Copy file loop. Destination library, root-folder behavior, and overwrite intent are preserved. Ordinary-list copies use a detected common-field Get item + Create item pattern and should be validated for required and complex fields. 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.
• Check converted expressions, branch ordering, loop exit conditions, and state-machine transitions.
• 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.