Skip to main content

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.

Conversion supports syncing custom fields between Salesforce and Conversion. This page explains how to add new fields to your sync and configure their settings.
Conversion does not automatically import custom fields from Salesforce. Each field you want to sync must be created in Salesforce, created in Conversion, and then mapped explicitly. This prevents unintended Salesforce fields from syncing into your Conversion instance.

Syncing a custom field

Adding a custom field to your sync is a three-step process:

Step 1: Create the field in Salesforce

Your Salesforce admin creates the custom field on the relevant object (Lead, Contact, or Account) in Salesforce. Note the field’s API name (the value ending in __c) — you’ll need it when you map the field in Step 3.
Conversion cannot create fields in your Salesforce org. Creating Salesforce fields requires a Salesforce admin.

Step 2: Create the field in Conversion

In Conversion, go to Settings → Objects → View Object → New → New Field and create the matching field. Choose a data type that’s compatible with the Salesforce field. The field works immediately within Conversion for forms, automation, and segmentation — even before you map it to Salesforce.

Step 3: Map the Conversion field to the Salesforce field

Once both fields exist, connect them so data can sync between them:
1

Navigate to field settings

Go to Settings → Fields in Conversion.
2

Find your Conversion field

Locate the field you created in Step 2.
3

Add a Salesforce mapping

Click the field and select the Salesforce field(s) you want to map it to.
4

Set the sync mode

Choose how data should flow between the systems.
New field mappings are not automatically backfilled. When you add a new field mapping, only contacts that sync going forward will have the field value populated. Existing contacts will not be updated retroactively.If you need to backfill the field value for existing contacts, contact your deployment strategist.

Field Label and Type Updates

When Salesforce Fields Change

If you rename a mapped custom field in Salesforce or change its data type, Conversion detects the change during the next sync and updates its internal tracking. However, the Conversion field’s label and data type do not automatically update – you may want to update these manually for consistency.
Changing a field’s data type in Salesforce may affect how existing values are handled. Review your data after making type changes.

When Conversion Fields Change

Changes to Conversion field labels don’t affect the underlying key or Salesforce mappings. The connection remains intact.

Managing Custom Field Mappings

Viewing Mappings

Navigate to Settings → Fields to see all field mappings. Each field shows which Salesforce objects it’s mapped to (Lead, Contact, Account) and the current sync mode.

Removing Mappings

You can disconnect a custom field from Salesforce by removing its mapping. This stops the sync but preserves all existing data in both systems.
Removing a mapping doesn’t delete historical data. The Conversion field keeps its values but stops receiving updates from Salesforce (and vice versa).

Deleting Fields

Deleting a field in Conversion removes the field and all its data. The corresponding Salesforce field is not affected – it remains in Salesforce with its data intact.

Frequently Asked Questions

This is intentional. Requiring an explicit field creation and mapping step gives you full control over which Salesforce fields enter your Conversion instance, and prevents unrelated or sensitive fields from syncing in unintentionally.
No. Conversion can only read from and write to existing Salesforce fields. Creating new fields in Salesforce requires a Salesforce admin.
Yes. A single Conversion field can be mapped to fields on multiple Salesforce objects (like Lead and Contact). This is how default fields like job_title work—mapped to Title on both Leads and Contacts.
Only if they’re on different objects. You can map Lead.Title and Contact.Title to the same job_title field, but you cannot map two different fields from the same object to one Conversion field.
Go to Settings → Fields, find the field, and modify its Salesforce mapping. You can remove the current mapping and add a different one.

Field Mappings

See all default field mappings between Salesforce and Conversion

Field Sync Preferences

Control how each field syncs with five flexible sync modes