Skip to main content
Conversion supports syncing custom fields between Salesforce and Conversion. This page explains how to add new fields to your sync, whether you’re starting from Salesforce or from Conversion.

​
Two Ways to Add Custom Fields

You can add custom fields to your sync starting from either system:

Starting from Salesforce

Create a custom field in Salesforce, and Conversion automatically detects and maps it on the next sync.

Starting from Conversion

Create a field in Conversion first, then connect it to a Salesforce field later (automatically or manually).

​
Starting from Salesforce

This is the most common approach. When you add custom fields to Salesforce, Conversion automatically detects and syncs them.

​
How Auto-Detection Works

During each sync, Conversion scans your Salesforce org for new custom fields. When a new custom field is found, Conversion automatically creates a corresponding field and mapping. You don’t need to configure anything manually – just add the field in Salesforce and it starts syncing on the next cycle.

​
The Detection Process

When Conversion encounters a new Salesforce custom field:
1

Check if already tracked

If Conversion already knows about this Salesforce field from a previous sync, it uses the existing mapping. No changes are made.
2

Look for a matching Conversion field

Conversion searches for an existing field with the same key (the Salesforce API name). If found, it links the Salesforce field to that existing Conversion field.
3

Create a new field if needed

If no matching field exists, Conversion creates a new field using the Salesforce field’s API name as the key and its label as the display name.
4

Apply a default sync mode

New fields default to Prefer Salesforce Unless Empty, or Always Prefer Salesforce if the field is read-only in Salesforce.

​
Automatic Unification Across Objects

Conversion uses the Salesforce field’s API name as the key for matching. This means fields with the same API name on different Salesforce objects automatically map to the same Conversion field.
You create a custom field Customer_Segment__c on both Salesforce Leads and Contacts.What happens:
  1. When syncing Leads, Conversion detects Customer_Segment__c and creates a Customer_Segment__c field in Conversion
  2. When syncing Contacts, Conversion detects Customer_Segment__c and finds the existing field
  3. Conversion automatically maps both Salesforce fields to the same Conversion field
Result: Lead and Contact data flows into a single unified field. When a Lead converts to a Contact in Salesforce, the data continues syncing seamlessly.
This automatic unification means you don’t need to manually configure anything when you have matching custom fields across Leads and Contacts.
This matching only applies within the same Conversion object type. Since Leads and Contacts both sync as Conversion contacts, their fields can unify. Account fields sync to companies separately and won’t merge with Lead or Contact fields of the same name. Standard fields like Industry and Company Name are an exception.

​
Default Sync Modes

Salesforce Field TypeDefault Sync ModeWhy
Editable custom fieldPrefer Salesforce Unless EmptyAllows Conversion to fill gaps while respecting Salesforce data
Read-only custom fieldAlways Prefer SalesforceField cannot be written to, so one-way sync only
You can change the sync mode after detection for editable fields. See Field Sync Preferences for details.

​
Starting from Conversion

Sometimes you want to create a field in Conversion first – perhaps for data you’re collecting through forms before your Salesforce admin has created the corresponding field. You might also want to create fields in Conversion that never sync to Salesforce for marketing purposes.

​
Creating Fields in Conversion

You can create custom fields directly in Conversion through Settings → Fields. These fields work immediately within Conversion for forms, automation, and segmentation.
Creating a field in Conversion does not automatically create a field in Salesforce. Conversion cannot create fields in your Salesforce org – that requires a Salesforce admin.

​
Connecting to Salesforce Later

Once your Salesforce admin creates a matching custom field, you have two options for connecting them:

​
Option 1: Automatic Connection

If you create a Salesforce field with the same API name as your Conversion field, Conversion automatically connects them on the next sync.
  1. You create a Preferred_Language__c field in Conversion
  2. Later, your Salesforce admin creates Preferred_Language__c on Leads
  3. On the next sync, Conversion detects the new Salesforce field
  4. Conversion finds the existing Preferred_Language__c field (matching key)
  5. The fields are automatically linked – no manual configuration needed
Data now syncs between the Salesforce field and the Conversion field you created earlier.
For automatic connection to work, the Salesforce field’s API name (including the __c suffix) should match your Conversion field’s key. Coordinate with your Salesforce admin on naming.

​
Option 2: Manual Mapping

If the field names don’t match, or you want to connect a Conversion field to a differently-named Salesforce field, you can create the mapping manually:
1

Navigate to field settings

Go to Settings → Fields in Conversion.
2

Find your Conversion field

Locate the field you want to connect to Salesforce.
3

Add a Salesforce mapping

Click on 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.

​
Field Label and Type Updates

​
When Salesforce Fields Change

If you rename a 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

No. Conversion can only read from and write to existing Salesforce fields. Creating new fields in Salesforce requires a Salesforce admin.
Data is stored in your Conversion field immediately. Once you connect it to a Salesforce field, future syncs will push existing Conversion values to Salesforce (based on your sync mode settings).
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.
Check that the field is a custom field (API name ends in __c). Standard Salesforce fields are handled through default mappings and aren’t auto-detected. Also ensure a sync has run since you created the 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