Salesforce Store a 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 Create ContentVersion + Get ContentVersion using Salesforce. Supported for Nintex Automation Cloud Salesforce store-file Xtension actions. Emits Salesforce ContentVersion creation, then reads ContentDocumentId back into the original Nintex output object for downstream file-association steps. Validate file content shape, file-size limits, and Salesforce Files permissions in UAT. 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.