Learning objective
By the end of this tutorial, you'll know how to map lemlist data fields to Salesforce, control which direction each field syncs, and connect lemlist users to their Salesforce counterparts — so the right data flows to the right place, automatically attributed to the right rep.
Why this matters
Field mapping is what turns a connected integration into a useful one. Without it, lemlist activity data has nowhere to go in Salesforce. Without user mapping, every activity gets logged under a generic default user — making rep-level reporting and quota tracking unreliable. Getting both right means your CRM is always accurate and your team always knows where each deal stands.
Prerequisites
Your Salesforce integration is connected in lemlist (see How to connect lemlist to Salesforce)
You have lemlist admin access
You know which Salesforce fields you want to receive lemlist data
Phase 1: Map your fields
Step 1: Open the Field Mapping tab and map your fields
In the Salesforce integration, open the Field Mapping tab. You'll see a list of lemlist fields on the left and a mapping to Salesforce fields on the right. Start with your most essential fields — name, email, and campaign name — then add more once sync is confirmed working.
Open the Field Mapping tab, then map lemlist fields to Salesforce fields in the list.
Step 2: Set the sync direction for each field
For each mapped field, use the direction icon to control data flow. This is where most mistakes happen — setting the wrong direction can overwrite good data in one system with stale data from the other.
lemlist → Salesforce: pushes outreach data into your CRM. Use for engagement fields (emails sent, reply status, campaign name)
Salesforce → lemlist: pulls CRM data into lemlist. Use for fields your CRM owns (phone number, deal stage)
Both directions: keeps both in sync. Use carefully — only for fields both systems legitimately update
For each mapped field, use the direction icon to set how data syncs.
Step 3: Add a custom lemlist field (optional)
If you need to sync a field that doesn't exist in lemlist by default, create a custom one. This is useful when your Salesforce org has custom fields you want lemlist to populate — for example, a campaign tracking field specific to your workflow.
In the Field Mapping tab, click Add a custom field.
Enter the Field name, choose the Field type, then click Create field.
You cannot map to Formula, Auto Number, or Roll-Up Summary fields in Salesforce — these are calculated automatically and can't be written to externally. Field mapping is not retroactive: only new or updated records sync after you save mapping changes.
Phase 2: Map your users
Step 4: Open the User Mapping tab
Open the User Mapping tab and connect each lemlist user to their Salesforce counterpart. Without this, all lemlist-synced activities are logged under the fallback user configured in Define default ownership — making it impossible to attribute outreach to individual reps for reporting or quota purposes.
Open the User Mapping tab, then map each lemlist user to the appropriate Salesforce user.
Fallback behavior: if a lemlist user isn't mapped, the integration falls back to the default Salesforce user configured for the connection.
You can map multiple lemlist users to one Salesforce user, but you cannot map one lemlist user to multiple Salesforce users.
Define default ownership (fallback behavior)
The Define default ownership section in the User Mapping tab lets you explicitly choose what happens when no user mapping match is found, for each sync direction:
CRM → lemlist: choose a lemlist user, or select No owner to leave contacts/companies unassigned rather than silently assigning them to a default user.
lemlist → CRM: choose a Salesforce user. Salesforce doesn't support a native "no owner" value — if you need this, create a dedicated Salesforce user named "No owner".
Access these settings by clicking the ✏️ icon on the General tab, or by navigating directly to the User Mapping tab.
💡 Default configuration: Existing teams keep their current default user — no behavior change unless you switch. New Salesforce teams default to "No owner" for CRM → lemlist; lemlist → CRM keeps the default user.
Practical example
A RevOps manager sets up field mapping for a 10-rep team. They map Email (bidirectional), Campaign Name → lemlist_Campaign__c (lemlist → Salesforce, for reporting), and Phone (Salesforce → lemlist, to enrich leads). They also map all 10 reps to their Salesforce counterparts. Result: every activity in Salesforce is attributed to the right rep, and campaign data flows into CRM reports automatically.
Troubleshooting
Fields not appearing in Salesforce after mapping
Root cause: Field mapping is not retroactive — only records created or updated after the mapping change will sync.
Make a small update to a lead in lemlist to trigger a sync
Check the Logs tab to confirm the sync went through
Wait a few minutes — syncs are near real-time but not instant
Can't find a Salesforce field to map to
Root cause: The field may be a Formula, Auto Number, or Roll-Up Summary type — these cannot be written to externally.
Create a standard text or number field in Salesforce to receive the data instead
Formula fields are calculated by Salesforce automatically and are read-only from external tools
Activities logged under the wrong rep in Salesforce
Root cause: The lemlist user hasn't been mapped in User Mapping, so their activities fall back to the default Salesforce user.
Go to the User Mapping tab and connect the missing lemlist user to their Salesforce counterpart. Also check the Define default ownership section to confirm the fallback user is correctly set
Future syncs will use the correct attribution — past records won't be updated retroactively