Salesforce integration

The Salesforce integration lets you push contacts revealed in Lusha directly into Salesforce as Leads, Contacts, or Accounts - with no manual data entry. This guide covers how to connect the integration, configure field mapping, and set account export preferences.

​

Export size and background processing

You can export up to 10,000 contacts or companies to Salesforce in a single job. Exports of up to 150 records process in real time. Larger exports run in the background in 20 batches - you can keep working while the job runs. If your selection exceeds 10,000 records, Lusha exports the first 10,000 and leaves the rest marked Not exported, so your next run picks up automatically. The 10,000-record cap is a Salesforce platform limit and cannot be changed.

​

Step 1: Connect Salesforce to Lusha

​

Step 2: Set up field mapping

Field mapping tells Lusha which Salesforce fields to populate when you export a contact. You can map fields for three record types: Lead, Contact, and Account.

• Each Lusha field on the left maps to a Salesforce field on the right.
• You can change any default mapping by selecting a different Salesforce field from the dropdown.
• Toggle on Allow Override if you want Lusha to update fields that already have data in Salesforce.

​

Default field mapping

Lead Contact Account For a full table of available Lusha fields, see Fields for field mapping and descriptions.

​

Step 3: Add predefined value fields (optional)

Predefined value fields let you automatically populate a Salesforce field with a fixed value every time a contact is exported from Lusha.

​

Step 4: Set up conditional field mapping (optional)

Conditional mapping lets you trigger additional field updates when an email or phone field is enriched - useful for lead routing workflows.

​

Step 5: Test your mapping

Before saving your configuration, click Test Mapping at the bottom-right of the screen. Lusha will create and immediately delete a dummy Lead, Contact, and Account in your Salesforce environment to verify that your settings are valid. If the test passes, the Test Mapping button turns green and you can click Save changes. If it fails, Lusha will return the matching Salesforce error to help you fix the configuration.

​

Account export preferences

(Available for Admins only) In the integration settings, you can control which Salesforce object types your team can export to. When the Account creation toggle is off, your team can only export contacts to existing Salesforce accounts - they cannot create new accounts from Lusha.

​

Autocomplete

The autocomplete setting matches the account name in Lusha to an existing account name in Salesforce as you type, saving time during manual exports.

​

Sync opt-out contacts to Salesforce

(Available for Admins only) Lusha can automatically sync a contact’s opt-out status to Salesforce, so your CRM data stays consistent with Lusha’s suppression list without any manual list management. Going forward, any contact marked as opted-out in Lusha automatically syncs to the mapped field in Salesforce - standard and custom fields are both supported. This keeps unsubscribe status consistent across platforms and removes the need to manually manage opt-out lists between Lusha and Salesforce. For background on how Lusha handles opt-outs generally, see Opt-Out Contacts.

​

Connected App / External Client App (CA/ECA) security requirements

Salesforce’s Connected App / External Client App (CA/ECA) framework sets new security requirements for apps that connect over OAuth. Here’s where Lusha’s Salesforce integration stands, as of November 2026:

• Connection type: Lusha connects to Salesforce using a Connected App with OAuth (Web Server flow).
• PKCE (Proof Key for Code Exchange): Supported. If your org requires PKCE, the connection completes normally with no workaround needed.
• Refresh token rotation: Supported on Lusha’s side, and being enabled on the Lusha app following final testing.
• 30-day idle refresh token expiry: Supported on Lusha’s side, and being enabled on the Lusha app following final testing.
• Refresh token IP allowlist: Lusha connects from a set of static outbound IPs, which you can allowlist on the Salesforce side. Contact Lusha Support for the current IP list.
• External Client App (ECA) migration: Not required. Salesforce continues to support existing Connected Apps, so no action is needed on your side.

​

Troubleshooting: Salesforce authentication issues

​

My team is being logged out of Salesforce / lost Salesforce authentication

If your team members see a “reconnect to Salesforce” prompt when trying to export, or find themselves force-logged out of the integration, this is caused by an expired OAuth token. Salesforce OAuth sessions have a finite lifetime. When the token expires, Lusha loses its authorisation to push records and prompts them to reconnect. This is a Salesforce session behaviour, not a Lusha bug. Each affected team member needs to reauthenticate individually. To reconnect your Salesforce account: To reduce how often this happens: In Salesforce, go to Setup → Session Settings and extend the Session Timeout value. Longer session lifetimes mean less frequent reauthentication. Your Salesforce Admin can make this change.

​

Contact imported from LinkedIn is missing fields in Salesforce

If a contact’s LinkedIn URL, website, country, city, industry, or annual revenue isn’t populating in Salesforce, the field isn’t included in your current mapping or the data wasn’t available at the time of export. You’re all set - your team can now push contacts from Lusha directly into Salesforce. For a full table of error codes, see Salesforce common errors.