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.
💡 Note: Only Lusha Admins and Managers can configure the integration. Admins must complete the initial setup first. After that, each team member needs to connect their own Lusha account to Salesforce to enable export. You must also be a Salesforce Admin to authorise the connection.
Step 1: Connect Salesforce to Lusha
Log in to your Lusha dashboard.
Go to Settings → Integrations and select Salesforce.
Choose Production or Sandbox, then click Connect.
Sign in to your Salesforce account when prompted. (If you're already logged in, this step is skipped.)
Click Continue to field mapping.
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.
💡 Note: When adding a new field, the Lusha field type and the Salesforce field type must match. For example, a numeric Lusha field like Number of Employees must map to a numeric Salesforce field.
Default field mapping
Lead
Lusha field | Salesforce field |
Email 1 | |
Phone 1 | Phone |
Job title | Title |
Company Name | Company |
Website | Website |
Last Name | Last Name |
First Name | First Name |
Predefined | Lead Source |
Contact
Lusha field | Salesforce field |
Email 1 | |
Phone 1 | Phone |
Job title | Title |
Last Name | Last Name |
First Name | First Name |
Departments | Department |
Account
Lusha field | Salesforce field |
Company Name | Name |
Website | Website |
Description | Description |
Number of Employees | Number of Employees |
For a full list 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.
Select a record type (Lead, Contact, or Account).
Click + Add field and select Predefined Value.
Choose the Salesforce field to populate.
Enter the fixed value you want applied.
Click Save changes before switching tabs.
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.
In Field mapping, click the Advanced button next to Email 1 or Phone 1.
Use the Map dropdown to define the condition and the value to set.
Click Apply, then Save changes at the bottom of the page.
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, users can only export contacts to existing Salesforce accounts — they cannot create new accounts from Lusha.
💡 Note: These settings apply to all team members in your account.
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.
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 the user 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:
Go to Settings → Integrations → Salesforce in your Lusha dashboard.
Click Reconnect (or Connect if the integration appears disconnected).
Sign in to Salesforce when prompted and confirm the permissions.
You should be returned to the Lusha integration settings with the connection restored.
💡 Note: Each user on your team manages their own Salesforce connection. An Admin reconnecting their account does not reconnect other team members. Each person needs to follow these steps from their own Lusha 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.
💡 Note: If reauthentication fails or the integration continues to disconnect frequently, contact Lusha Support via the chat icon in your dashboard and include your Salesforce org ID and the error message shown.
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.
Go to Settings → Integrations → Salesforce → Field Mapping.
Check that the missing fields are mapped. If not, click + Add field and map them.
Toggle on Allow Override for those fields if you want Lusha to update them on future exports.
Click Save changes.
You're all set — your team can now push contacts from Lusha directly into Salesforce. For a full list of error codes, see Salesforce common errors.