Export Payloads configuration to a .payloads file when moving an Integration or Payload between orgs. Actions and their configuration references travel with the export, but the receiving org still needs its Salesforce dependencies and environment-specific setup.

Install a compatible package version and prepare the Salesforce objects and fields used by Queries and Targets. Deploy and activate the required Flow definitions separately.

Prepare Named Credentials and their authentication, certificates, Sites, endpoint access and permissions as required by the integration. A reference to one of these resources in an export does not deploy or authenticate that resource in the destination.

Review environment-specific API endpoints and credentials before running imported Payloads.

Open the Integration or Payload and select Export. Review the preview, then use Copy or Download as appropriate.

The preview is redacted. Copy and Download contain the full configuration, including secrets needed for migration. Handle the exported content accordingly and share it only through an appropriate secure route.

The export includes the selected configuration and its dependencies. For a child Payload Action, this includes the called Payload and its published output configuration. Review the included records before importing. Keep a backup of the destination configuration before overwriting it.

Review the export before moving it to the destination.

Open Import in the destination. Select the .payloads file or paste its Migration JSON. The warning states that existing records with matching API Names will be updated and Payload child configuration will be replaced. Back up matching destination configuration before selecting Import.

To import an entire Integration, use Import from Backup from the Integrations list. To import a Payload into an existing Integration, open that Integration and use its Import button. Payloads remaps the imported configuration to the selected Integration's API name, including references to dependent child Payloads.

Check the destination and keep a backup before importing over matching API names.

After import, open the resulting Integration and inspect each Payload's Action sequence. Check references to Queries, Targets, Flows and child Payloads, along with input mappings and published outputs.

Legacy configuration is converted to Actions within the import transaction. If the import fails, inspect the reported error rather than manually creating partial internal Action records.

Review external endpoint URLs, credential values, file-connection API names and runtime permissions. Test the imported Payload through its intended entry point and inspect the Job.

For Flow Actions, confirm the referenced active Flow exists and its input and output variables match the mappings. For child Payload Actions, confirm the child is in the same Integration and remains eligible.

This example uses two Integrations in the same org: Payloads Demo and Payloads Demo Copy. Exporting Lookup Sample Product also includes its child, Fetch Sample Product. Importing into Payloads Demo Copy creates both Payloads and remaps the child reference. Run the imported parent with {"productId":"1"} and check that its response contains {"productName":"Google Pixel 6 Pro"}. This checks configuration and mapping preservation; a different org still needs the destination checks above.

The completed Job uses the destination Integration's Action API name.

For inbound or email integrations, complete and verify destination-specific addresses and access before switching callers or senders.

See Check the upgrade from legacy Payloads to Actions and Secure Payloads for production.