---
schema_version: "1"
id: c3c9e8de312c16d38403ba17f96097c77905b6ae86dc96dd0d26360770d5242a
title: Legacy Partner Connect Object and Field Integration Considerations for Vendors
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_setup_prereq_mapping_plan_vendor.md
canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan_vendor.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f9c776e838771ba7240a8a608c4070e911be3d70c38cf4dcd4bda1c3ec44371d
description: Share key details about your object and field integration with your partner admin. Sometimes you must adjust objects, fields, or customize other settings to accommodate discrepancies in how each Salesforce org stores data.
products:
  - Sales
  - Slack
  - Cross Cloud
release: "264"
---
# Legacy Partner Connect Object and Field Integration Considerations for Vendors

Share key details about your object and field integration with your partner admin. Sometimes you must adjust objects, fields, or customize other settings to accommodate discrepancies in how each Salesforce org stores data.

- The objects that you plan to integrate (Lead, Opportunity, or both)
- The fields on each object that you plan to integrate. Of those fields, indicate these details.
- - If not obvious, a description of how you use the field
    - Required fields
    - Field types. Not all field types are available for mapping. See [Legacy Partner Connect Limits and Limitations](https://help.salesforce.com/s/articleView?id=slack.prm_pc_limits.htm&release=264.0.0&type=5 "Review limits and limitations for Partner Connect.").
    - For picklist fields, the picklist options that you provide for users to select
    - For currency fields, the type of currency
    - The fields for which you plan to send and receive updates across Salesforce orgs. You can send and receive updates on up to 10 fields per object. Vendors choose fields for update on behalf of both companies.

After sharing your plan, wait to hear back from your partner admin on how your objects and fields map to their own. Be prepared to coordinate on a plan for adjusting objects, fields, or customizing other settings to accommodate discrepancies. Don’t forget to train your users on any process changes so that your users are aware of how you plan to track data.

#### See Also

- [Select Vendor Objects and Fields to Integrate with the Partner’s Salesforce Org](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_vendor_map.htm&release=264.0.0&type=5 "After inviting a partner to connect, vendor admins must select the objects and fields that they want to integrate with their partner’s Salesforce org. During this step, vendors indicate which objects and fields contain data that they want partner users to be able to export. Vendors also select which field updates are sent and received across orgs and where the read-only partner version of the record is stored. Then we email the partner admin, asking them to select the objects and fields that they want to map to yours.")
- [Prepare Legacy Partner Connect Objects for Connected External Records](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prepare_cnnctd_extl_objects.htm&release=264.0.0&type=5 "To let your users see and track the progress of shared leads and opportunities, you can opt to store a read-only version of the other org’s record in your own org. The Connected External Lead and Connected External Opportunity objects store these read-only records. Learn how vendor and partner admins can prepare the connected external objects to make sure they're ready to save the read-only records for Partner Connect.")
- [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.")