> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review contact sync settings

> Review Salesforce record and field sync rules, then verify one contact before using the data.

## Open the right workspace settings

Click the workspace name at the top left, choose **Workspace settings**, then **CRM and syncing**.

Use a workspace with Salesforce already connected. Under **CRM**, confirm that the organization is the one you intend to use. Review changes with your workspace administrator and use a test contact you can inspect in both systems.

<Frame caption="CRM and syncing brings together the connection, API limits, and record sync rules. This example workspace is not yet connected.">
  <img src="https://mintcdn.com/conversion/wAU_-MPK8jx_KVnq/images/user-guide/sync-overview.jpg?fit=max&auto=format&n=wAU_-MPK8jx_KVnq&q=85&s=8384bbe98d291b34f36fb9e4103439a2" alt="CRM and syncing settings with the Salesforce connection card, Use sandbox option, Connect button, and API rate limits" width="1280" height="720" data-path="images/user-guide/sync-overview.jpg" />
</Frame>

<Note>
  Settings on the **CRM and syncing → Overview** page save as you change them. Review the intended behavior first; there is no final Save button for the whole page.
</Note>

## Decide which records move in each direction

Agree on these choices with your administrator:

1. Should Salesforce leads, contacts, or both be available to receive marketing emails? Review [Read data from Salesforce](/product-docs/workspace-settings/crm-and-syncing/overview#read-data-from-salesforce).
2. Should changes made in Conversion update Salesforce? Review [Write data to Salesforce](/product-docs/workspace-settings/crm-and-syncing/overview#write-data-to-salesforce).
3. When a new contact syncs to Salesforce, should it become a Lead or a Contact linked to an Account? Review [New contacts](/product-docs/workspace-settings/crm-and-syncing/overview#new-contacts).

Use the [CRM and syncing reference](/product-docs/workspace-settings/crm-and-syncing/overview) for toggle dependencies, deletion behavior, and API limits before changing those settings.

## Check the fields your email needs

Workspace switches control record sync. Each **field mapping** separately determines where a value comes from and which value wins.

For an email that greets contacts by name, start with Email and First Name. Include any other field you plan to use for personalization or workflow criteria.

1. Open **Objects**, choose **Contacts**, and open **Fields**.
2. Search for the field by label or key. The key, such as `first_name`, is what you use in Liquid.
3. Open the field's options menu and choose **Edit**.
4. In **Linked Salesforce fields**, review the mappings for **Lead** and **Contact** separately. A contact field can have a different link for each Salesforce object.
5. If a mapping is missing or needs a different mode, follow [Linking fields to Salesforce](/product-docs/workspace-settings/objects/fields#linking-fields-to-salesforce), then return here to test the result.

<Frame caption="A contact field has separate mapping rows for Salesforce Contact and Lead. This example has no linked fields yet.">
  <img src="https://mintcdn.com/conversion/wAU_-MPK8jx_KVnq/images/user-guide/sync-field-mapping.jpg?fit=max&auto=format&n=wAU_-MPK8jx_KVnq&q=85&s=110de1ef8bd2507badbd09d5efbbe7f5" alt="Update field dialog for First Name showing its first_name key and separate Contact and Lead rows under Linked Salesforce fields" width="1280" height="720" data-path="images/user-guide/sync-field-mapping.jpg" />
</Frame>

For **First Name**, decide what should happen if the name in Conversion differs from Salesforce. Use the [sync mode comparison](/product-docs/sync/salesforce/setup/field-sync-preferences#sync-mode-comparison) to choose which system should win, and check [field restrictions](/product-docs/sync/salesforce/setup/field-sync-preferences#sync-mode-restrictions) before saving. Linking a field can import existing Salesforce values.

## Verify one record before relying on the sync

Use a test record and a field whose sync behavior you have agreed on. Record the value you expect to see before making the test change.

1. If testing inbound sync, change the test record in Salesforce. If testing outbound sync, make the intended change in Conversion's record editor.
2. Return to **CRM and syncing → Overview → View logs** in **Recent sync health**.
3. Choose **Inbound** or **Outbound** and a recent time range. Open the relevant batch with **View**.
4. Find the test record and inspect its status and field details. A completed batch can still contain skipped records.
5. Open the destination record and compare the actual field value with your expected value. Then preview an email with that contact to check the data where it will be used.

If the expected change has not appeared, check [sync timing](/product-docs/workspace-settings/crm-and-syncing/sync-activity#how-syncing-is-batched). If the record is skipped or fails, look up its [record message](/product-docs/workspace-settings/crm-and-syncing/sync-activity#record-messages) before changing settings or retrying it.