Skip to main content

🚀 New Salesforce Integration: What’s Changed?

Step-by-step guide to syncing your leads between Salesforce and lemlist

Updated this week

Heey lemlister! 👋

The new Salesforce integration is here—and it's a game-changer! Here’s everything you need to know to get the most out of it.

Team-Level Setup

From now on, the Salesforce integration is managed at the team level. That means:

  • You only need to connect one Salesforce account for your whole team.

  • The connection applies to all campaigns, so no need to set it up over and over again.

  • You define your core sync rules once—lemlist takes care of the rest.

✅ What stays at the campaign level?

Only opportunity (deal) creation rules. You can still configure when a deal is created depending on the specific campaign strategy.

💡 Go to a campaign’s CRM integration settings to define custom triggers for deal creation—these will only apply to that specific campaign.

🧩 What You’ll Find in Team Settings

Your team settings now include several powerful tabs:

1️⃣ General Settings

  • Connect your Salesforce account.

  • Choose when to create contacts in Salesforce:

    • When they’re created in lemlist.

    • When they’re launched in a campaign.

    • When an email or LinkedIn message is sent.

    • When you get a reply.

    • When they’re marked as interested.

2️⃣ Field Mapping

  • Sync contact and company fields between lemlist and Salesforce.

  • Decide whether lemlist contacts are created in Salesforce as Leads or Contacts.

  • Map lemlist company fields with Salesforce Account properties.

3️⃣ User Mapping

  • Map lemlist users to Salesforce users to ensure ownership clarity.

  • If no mapping is set, lemlist uses the default integration user.

4️⃣ Activities Mapping

  • Choose which activities you want to sync.

  • Define how they’re tracked in Salesforce.

5️⃣ Logs

  • View integration logs and monitor all sync activities to troubleshoot issues.

🆕 Contact-Based Sync = Better Data Consistency

Forget the old “lead-only” logic. lemlist now uses Contacts, which means:

  • A person (e.g. François Lejeune) is a single contact who can appear in multiple campaigns.

  • Contacts are no longer isolated per campaign—you now have centralized profiles.

🧭 What does that change?

  • The sync now happens at the contact & company level.

  • Updates in lemlist are reflected in Salesforce—and vice versa! 🤩

🧬 Custom Field Mapping & Bi-Directional Sync

Map any lemlist contact or company field with the corresponding Salesforce property:

  • Contact → Contact or Lead property

  • Company → Account property

By default, sync is bi-directional (lemlist ↔ Salesforce), this means that any change happening in lemlist will update Salesforce, and the other way around.

It is the default and recommended setup but you can change that and opt for :

  • Salesforce priority

  • lemlist priority

  • or disable sync altogether

📥 Improved Activity Mapping

Activities now map more accurately with Salesforce object types:

Activity

Stored in Salesforce as

Email Sent / Reply

EmailMessage

Task

Task

Call

Task with subtype “Call”

Call Note

Task (Call subtype, with updated note)

LinkedIn Msgs

Task completed, subtype “LinkedIn”

Others (e.g., email opened, clicked)

Task completed

✅ Two-way sync also works for tasks: complete or delete them in Salesforce → synced in lemlist (and vice versa).

🧑‍💼 User Mapping = Better Ownership

Assign leads, contacts, and activities to the right people with user mapping. This ensures CRM data ownership stays clean and clear across both tools.

✨ CRM Import Enrichment

Now, when you import leads from Salesforce, you can enrich them using lemlist’s features:

  • LinkedIn enrichment

  • Email finder

  • Phone finder

  • Email verifier

⚙️ Make sure to set up field mapping properly so enriched data goes to the right Salesforce fields.

💡 Ready to connect Salesforce to lemlist?

Here's how to do it:

1️⃣ Click on your name → go to Settings
​

2️⃣ Go to Integrations → Scroll to Salesforce
​

3️⃣ Click Connect and follow the login prompt

4️⃣ Once you are logged in, you can now access your Salesforce integration

5️⃣ Action Required — Click "Settings"

If an action is required to finalize the integration, you’ll see a “Settings” button. Click it!

Define the Salesforce account you want to use to sync your lemlist team. With that new version of the integration you need only to define 1 account through which all connections to Salesforce will be done.

6️⃣ Select your default user - This is useful in case the user mapping is not done or if there is an issue with it, as the default user will be used for contact & company ownership.

7️⃣ Confirm You’re Connected - Once everything is set, you’ll see the ✅ “Connected” status.

❓ Question Time - Still have questions? We've got you covered 👇

What if I have multiple Salesforce accounts?

You must select only one to sync with lemlist. This is your team's shared Salesforce workspace.

⚠️ Campaigns using data from a different Salesforce account will be stopped.
If you're unsure which one to choose, check with your Salesforce admin.

How does field mapping work between lemlist and Salesforce?

Field mapping lets you define how data flows between lemlist and Salesforce. You choose which lemlist field should sync with which Salesforce contact, company, or lead property.

Here’s how it works:

Select a lemlist field and map it to a compatible Salesforce property.

⚠️ You cannot map to Salesforce fields of type: formula, auto number, or roll-up summary.

Choose your sync direction (optional — defaults to bi-directional):

🔁 Bi-directional: changes in either system update the other.

🔒 Salesforce priority: only updates lemlist if Salesforce changes.

✍️ lemlist priority: only updates Salesforce if lemlist changes.

💡 Pro Tip: If you recently created a field in Salesforce and don’t see it in the dropdown, click “Click here to refresh the Salesforce fields” at the bottom of the page.

🚫 Note: Field mapping is not retroactive — if data existed before mapping, it won’t automatically sync.

Also, two fields are automatically created by lemlist in Salesforce and cannot be mapped:

lemlist lead status
lemlist campaign

How does lemlist avoid creating duplicate contacts or companies in Salesforce?

Before creating a new record, lemlist checks your Salesforce database to avoid duplication by looking for the following fields:

🔹 For Leads:

  • Email

  • LinkedIn URL

  • First name + Last name (only if there's a single match in Salesforce)

🔹 For Contacts:

  • Email

  • LinkedIn URL

  • First name + Last name (again, only if there's a unique match)

🔹 For Companies:

  • Domain

  • LinkedIn URL

If any of these values match an existing record, lemlist will associate the new activity or data with the existing record instead of creating a duplicate.

When I import from a contact view filter, lead view filter, or report view filter into a lead list, what information gets imported?

It depends on the type of view you're importing from:

🔹 Contact view filter

lemlist imports:

  • All fields mapped in your contact field mapping

  • Any custom contact fields from your CRM

🔹 Lead view filter

lemlist imports:

  • All fields mapped in your lead field mapping

  • Any custom lead fields from your CRM

🔹 Report view filter

It depends on the type of report:

  • Lead-based report → imports fields from your lead mapping and custom lead fields

  • Contact-based report → imports fields from your contact mapping and custom contact fields

⚠️ Important:
To successfully import from a report view, make sure your Salesforce report includes either:

  • Lead ID for lead reports

  • Contact ID for contact reports

Without this, lemlist won’t be able to match and import the data properly.

I sync my lemlist contacts as leads in Salesforce. What do I need to do for lemlist to fill in the ‘Company’ field on the lead (a required field in Salesforce)?

lemlist automatically handles this for you!

By default, lemlist will populate the ‘Company’ field on the lead in Salesforce using:

  • The company name from the contact’s most recent experience in lemlist

  • Or the experience marked as ‘primary’, if one is set

This ensures the required ‘Company’ field is always filled when syncing leads from lemlist to Salesforce.

🚀 You're now ready to supercharge your outreach with Salesforce and lemlist!

Need help with your Salesforce integration? - our amazing support team is just one click away 🙌

Related Articles
Pipedrive integration: how to import leads from Pipedrive to lemlist
Troubleshoot Data Sync Issues Between lemlist and HubSpot
New HubSpot integration
Field Mapping in HubSpot Integration with lemlist: A Step-by-Step Guide
Did this answer your question?