How Partner Connect Exports, Imports, and Integrates Records Across Orgs

Kicking Off Partner Connect Across Salesforce Orgs

To get started with Partner Connect, vendor and partner admins work together to set up the product. They securely connect their Salesforce orgs, agree on which shared object fields to integrate, and configure the user experience. When both orgs are ready to roll out the feature, vendor admins grant export permissions only to the partner users they select.

During setup, an admin enables Partner Connect in Salesforce Go and grants access to channel managers, admins, and partner users. Then they establish a Salesforce connection and map it to a partner account. They verify object and field mappings and add a record page component to show shared record updates.

Exporting and Importing Records

After setup is complete, partner users can log in to the vendor’s Experience Cloud partner site (1), select records of interest, and export the records to the partner’s own Salesforce org. If Partner Connect exports the records successfully from the vendor’s org (2), Partner Connect then attempts to import the records to the partner’s org (3).

Partner Connect respects the vendor's sharing settings, making sure that partner users see only the records explicitly shared on the Experience Cloud site. Also, vendor admins can limit which objects and fields are available for export during setup.

For example, a vendor admin makes a subset of their accounts, contacts, leads, and opportunities available from the partner site. Vendor and partner admins can then configure Partner Connect to let partner users export the object records. If the vendor and partner agree to export opportunities only, the vendor admin can further narrow the shared data by limiting the available opportunity fields. If a vendor has 25 opportunity fields but wants the partner to export data for only 10 fields, the vendor admin proposes that selection during setup.

Upon import, a version of each exported vendor record is created in the partner's org. Because separate versions now exist in both environments, vendor and partner users can update their respective copies independently over time.

Sending Record Updates Across Salesforce Orgs

During setup, the vendor admin can choose whether updates keep flowing between the original vendor record and the new partner record in both orgs. That lets vendor and partner users see how the other org’s record is progressing over time. Each company can track its own sales stage, deal size, or outcome on shared business, while the other org follows along efficiently.

Vendor admins can select data by field. That gives the vendor fine-tuned control over one-time exports versus ongoing sharing. As a result, the companies can be transparent about their mutual interests while maintaining data privacy where it’s required.

If vendors choose to send and receive updates between orgs, Partner Connect creates a read-only version of the record on the connected external object. The original vendor record maps to the partner’s connected external record across both orgs. When a vendor user updates a field the admin chose for cross-org updates, that update appears on the partner’s connected external record.

Note The Account Name and Primary Campaign Source lookup fields on the Opportunity object are exceptions. A vendor can propose these fields for integration, but a partner can see only the name of the referenced field. These lookup fields don’t support sending or receiving updates.

When a partner user updates a field that sends and receives updates, a read-only copy of the record is created in the vendor’s org. Each later update on that record appears on the corresponding connected external record in the vendor org.

Vendor admins can add the Synced Record Preview component to the record pages of the shared objects. Doing so lets users see the synced records that reflect the latest data saved in the peer’s system.