--- schema_version: "1" id: 756b0d3795552573da5fd7af0153044e55a6aca91893a43990d9c6d1c9df35d2 title: Legacy Partner Connect Considerations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 81ecaf7cb20eb207d69c350913bb36263e1e3718a039ea4a26a302f25a0fec97 description: Review considerations about Partner Connect support and setup. products: - Sales - Slack - Cross Cloud release: "264" --- # Legacy Partner Connect Considerations Review considerations about Partner Connect support and setup.
Available in Lightning Experience in Enterprise and Unlimited Editions with Sales or Service. Vendors must purchase a PRM add-on license for the partner admin user and each partner user who exports records. Partners aren’t required to purchase PRM licenses to use Legacy Partner Connect.
- Partner Connect can support record integration with multiple companies. Each org can establish up to 50 connections as a vendor, and up to 50 connections as a partner. But the same two orgs can’t establish multiple connections between them, even if you play a different role in each connection. For example, if you establish a connection as the vendor, you can’t establish a second connection with the same org in which you play the partner. - Sometimes you’re required to adjust your object and field settings to prepare objects for integration across orgs. To make sure you’re able to make any required adjustments, review the setup prerequisites. - During setup, vendors select the objects and fields that they want to map with their partner’s org. Then Salesforce sends an email for each proposed object mapping to the partner admin, asking them to respond with their own object and field mappings. Each email contains a JSON script that a partner must import into Setup to view the vendor’s proposal. - If the partner admin can’t locate their field-mapping email from Salesforce, the vendor admin can resend the email. Vendor admins can go to their previously saved mappings and select **Email Field Mapping** from the actions dropdown menu. - To locate emails, partners can search for emails with “Partner Connect” in the subject. - Vendor admins can edit their fields selected for integration to share additional fields or reduce the fields they’re sharing. But the partner org doesn’t get exports or updates for newly added fields until the partner admin revisits Setup and gets the vendor’s latest mappings. To get the latest mappings, partner admins can update the JSON for that object and then map any additional fields - Vendor org users can’t export records from the vendor’s partner site to the partner org. Only partner users can export records. - Each record can be imported to the partner’s org one time only. If partner users attempt to export a record again, that export is skipped. To see which records have been previously exported, partner users can add the Export Status field to their Lead and Opportunity list views, but vendor admins must give them the permission to do so. See [Give Partner Users Permission to Use Partner Connect](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_vendor_user_perm_set.htm&release=264.0.0&type=5 "When vendor admins are ready to roll out Partner Connect, vendor admins must give partners the permission to export records from your Experience Cloud partner site. We also recommend verifying that partner users have permission to customize list views. That way, partners can add the Export Status field to their list views, so they can see which leads and opportunities have been exported to the partner org already. Salesforce admins don’t have access to the Export Status field, so you can’t add the field to list views on partner users’ behalf.") - After exporting records, a partner user sees a message confirming whether the export attempt was successful. But even successful exports can result in unsuccessful imports to the partner org. Partner Connect sends an email that lists the number of successful, unsuccessful, or skipped imports to the last partner admin who saved the field mappings in the partner org. Admins in either org can prepare a Partner Connect status report to observe export and import issues and evaluate next steps for troubleshooting persistent issues. #### See Also - [Legacy Partner Connect Roles and Responsibilities](https://help.salesforce.com/s/articleView?id=slack.prm_pc_roles_responsibilites.htm&release=264.0.0&type=5 "After a vendor company selects a partner company with whom they want to integrate records, companies must designate a vendor admin and partner admin. Admins must have the bandwidth to collaborate on Partner Connect planning, setup, and maintenance. If record export, import, or update issues occur, an IT professional at the partner company can also offer support.") - [Legacy Partner Connect Setup Prerequisites](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_parent.htm&release=264.0.0&type=5 "Vendors and partners must work together to complete several prerequisites before beginning Partner Connect setup in Salesforce.") - [Map Your Preferred Objects and Fields to Your Vendor’s Org](https://help.salesforce.com/s/articleView?id=slack.prm_pc_prm_pc_setup_partner_map.htm&release=264.0.0&type=5 "After your vendor selects their object and field mappings, you get an email for each object. The emails instruct you on how to complete your mappings. First we guide you through importing your vendor’s object and field selections. Then you select a default user to assign to imported records. Lastly, you select the fields that you want to map to your vendor’s fields. If your vendor elected to send and receive field updates across orgs, you must also review storage options.") - [Integrating Shared Business Across Salesforce Orgs with Legacy Partner Connect](https://help.salesforce.com/s/articleView?id=slack.prm_pc_parent.htm&release=264.0.0&type=5 "Legacy Partner Connect lets vendors and partners work leads and opportunities together, providing visibility on shared business across Salesforce orgs. Partners users log in to a vendor’s Experience Cloud partner site to export records from approved objects to the partner's Salesforce org. Exported records remain connected across orgs, giving users from both companies a read-only glimpse of how records progress independently for each company.") - [How Legacy Partner Connect Exports, Imports, and Integrates Records Across Orgs](https://help.salesforce.com/s/articleView?id=slack.prm_pc_overview_how_biz_tracked.htm&release=264.0.0&type=5 "Learn about how Partner Connect lets vendors and partners work on shared leads and opportunities independently while still providing cross-org visibility into how each record is progressing.")