> ## 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.

# Field Mappings

> How Conversion maps fields between Salesforce objects and Conversion contacts and companies.

Conversion maintains a mapping layer that connects Salesforce fields to Conversion fields. This page explains how these mappings work, what's configured by default, and how custom fields are handled.

## How Field Mappings Work

Field mappings define the relationship between two concepts:

<CardGroup cols={2}>
  <Card title="Salesforce Fields" icon="salesforce">
    Fields on Salesforce objects (Leads, Contacts, Accounts) that Conversion reads from and writes to.
  </Card>

  <Card title="Conversion Fields" icon="database">
    The fields stored on Conversion Contacts and Companies.
  </Card>
</CardGroup>

A mapping connects one or more Salesforce fields to a single Conversion field. For example, the `first_name` field in Conversion is mapped to both `FirstName` on Salesforce Leads and `FirstName` on Salesforce Contacts.

<Note>
  Field mappings control *which* fields sync. [Sync modes](/product-docs/sync/salesforce/setup/field-sync-preferences) control *how* they sync (direction and conflict resolution).
</Note>

***

## Object-Level Mapping

Conversion tracks which Salesforce objects each field is connected to. This determines where data can flow.

### Contact Field Mappings

| Mapping Scenario                            | Sync Behavior                                                         |
| :------------------------------------------ | :-------------------------------------------------------------------- |
| Field mapped to **Leads only**              | Syncs only with Salesforce Leads. Write-backs go only to Leads.       |
| Field mapped to **Contacts only**           | Syncs only with Salesforce Contacts. Write-backs go only to Contacts. |
| Field mapped to **both Leads and Contacts** | Syncs with both objects. Write-backs apply to both.                   |

<Accordion title="Example: Job Title field">
  The `job_title` field in Conversion is mapped to:

  * `Title` on Salesforce Leads
  * `Title` on Salesforce Contacts

  When a Lead syncs in, the `Title` value populates `job_title`. When that Lead converts to a Contact in Salesforce, the Contact's `Title` continues syncing to the same `job_title` field.

  When Conversion writes back changes to `job_title`, it updates the appropriate Salesforce object based on whether the contact is currently linked to a Lead or Contact.
</Accordion>

### Company Field Mappings

| Mapping Scenario                            | Sync Behavior                                                                                                           |
| :------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------- |
| Field mapped to **Accounts only**           | Syncs only with Salesforce Accounts. Write-backs go only to Accounts.                                                   |
| Field mapped to **both Leads and Accounts** | Syncs with both objects. Write-backs apply to both depending on if the contact is tied to a Salesforce Lead or Contact. |

<Accordion title="Example: Industry field">
  The `industry` field in Conversion is mapped to:

  * `Industry` on Salesforce Leads
  * `Industry` on Salesforce Accounts

  When a Lead syncs in, the `Industry` value populates the company's `industry` field. When a Contact syncs in with an associated Account, the Account's `Industry` syncs to the same field.

  This unified mapping means company data stays consistent regardless of whether it originated from a Lead or an Account. When Conversion writes back changes, it updates the appropriate Salesforce object based on the company's current associations.
</Accordion>

***

## Default Mappings

Conversion ships with a set of default mappings that connect standard Salesforce fields to Conversion fields. These mappings are pre-configured and cannot be removed.

<Info>
  While you cannot remove default mappings, you can still configure the [sync mode](/product-docs/sync/salesforce/setup/field-sync-preferences) for most fields to control how data flows.
</Info>

***

## Default Contact Field Mappings

These mappings connect Salesforce Lead and Contact fields to Conversion contact fields.

### Lead → Contact Field Mappings

| Salesforce Lead Field | Conversion Field |
| :-------------------- | :--------------- |
| `Email`               | `email`          |
| `FirstName`           | `first_name`     |
| `LastName`            | `last_name`      |
| `Title`               | `job_title`      |
| `Phone`               | `phone`          |
| `MobilePhone`         | `mobile_phone`   |
| `Fax`                 | `fax`            |
| `City`                | `city`           |
| `State`               | `state`          |
| `PostalCode`          | `postal_code`    |
| `Country`             | `country`        |
| `Street`              | `street`         |
| `Description`         | `description`    |
| `LeadSource`          | `lead_source`    |
| `Status`              | `lead_status`    |
| `Salutation`          | `salutation`     |
| `OwnerId`             | `owner_id`       |

### Contact → Contact Field Mappings

| Salesforce Contact Field | Conversion Field |
| :----------------------- | :--------------- |
| `Email`                  | `email`          |
| `FirstName`              | `first_name`     |
| `LastName`               | `last_name`      |
| `Title`                  | `job_title`      |
| `Phone`                  | `phone`          |
| `MobilePhone`            | `mobile_phone`   |
| `Fax`                    | `fax`            |
| `MailingCity`            | `city`           |
| `MailingState`           | `state`          |
| `MailingPostalCode`      | `postal_code`    |
| `MailingCountry`         | `country`        |
| `MailingStreet`          | `street`         |
| `Description`            | `description`    |
| `LeadSource`             | `lead_source`    |
| `Salutation`             | `salutation`     |
| `Department`             | `department`     |
| `Birthdate`              | `date_of_birth`  |
| `OwnerId`                | `owner_id`       |

<Tip>
  Notice that Salesforce Leads use `City`, `State`, etc., while Contacts use `MailingCity`, `MailingState`, etc. Conversion handles this automatically – both map to the same fields.
</Tip>

***

## Default Company Field Mappings

These mappings connect Salesforce Lead (company fields) and Account fields to Conversion Company fields.

### Lead → Company Field Mappings

When syncing Leads, certain fields represent company-level data rather than person-level data. These map to Company fields.

| Salesforce Lead Field | Conversion Company Field |
| :-------------------- | :----------------------- |
| `Company`             | `company_name`           |
| `Website`             | `website`                |
| `Industry`            | `industry`               |
| `AnnualRevenue`       | `annual_revenue`         |
| `NumberOfEmployees`   | `number_of_employees`    |

### Account → Company Field Mappings

| Salesforce Account Field | Conversion Company Field |
| :----------------------- | :----------------------- |
| `Name`                   | `company_name`           |
| `Website`                | `website`                |
| `Industry`               | `industry`               |
| `AnnualRevenue`          | `annual_revenue`         |
| `NumberOfEmployees`      | `number_of_employees`    |
| `Phone`                  | `phone`                  |
| `Description`            | `description`            |
| `AccountSource`          | `account_source`         |
| `Type`                   | `account_type`           |
| `BillingStreet`          | `billing_address`        |
| `BillingCity`            | `billing_city`           |
| `BillingState`           | `billing_state`          |
| `BillingStateCode`       | `billing_state_code`     |
| `BillingPostalCode`      | `billing_postal_code`    |
| `BillingCountry`         | `billing_country`        |
| `OwnerId`                | `owner_id`               |

***

## Custom Fields

Beyond the default mappings above, you can sync custom Salesforce fields to Conversion. Custom fields aren't imported automatically — each field must be created in Salesforce, created in Conversion, and then mapped explicitly. This gives you full control over which Salesforce fields enter your Conversion instance.

<Card title="Custom Fields Guide" icon="plus" href="/product-docs/sync/salesforce/custom-fields">
  Learn how to add custom fields to your sync, step by step.
</Card>