When exporting contacts from Lusha to Salesforce, you may encounter errors related to permissions, field mapping, or your Salesforce configuration. This article covers the most common errors and how to fix each one.
💡 Note: Most of these issues can only be resolved by a Salesforce Admin and a Lusha Admin. In many cases, this is the same person.
Reached CRM API limit
This error means your Salesforce account has hit its daily API call limit, which restricts how much data Lusha can read or push.
To fix this:
Ask your Salesforce Admin to increase the daily API limit. They can also adjust it in Lusha via Settings → Integrations → Salesforce → API request limit.
After changing the limit, disconnect and reconnect the Lusha–Salesforce integration for the update to take effect.
Alternatively, wait 24 hours — the API limit resets daily.
Lead assignment rules issue
This error appears when a saved lead is automatically reassigned to another owner, or when Salesforce blocks the lead from saving due to an existing assignment rule.
To fix this, your Salesforce Admin needs to add a new rule to bypass the existing assignment logic for Lusha-sourced leads:
In Salesforce Setup, search for Lead Assignment Rules.
Open the relevant rule and add a new entry at sort order No. 1.
Set the condition: when Lead Source equals Lusha, then select Do Not Reassign Owner.
Save the rule.
Bad value for restricted picklist field
This error means the value Lusha is trying to push to a restricted picklist field in Salesforce doesn't match any of the allowed values in that list. This often comes down to case sensitivity or small differences in how values are written — for example, Lusha sends "Russia" but Salesforce expects "Russian Federation".
To fix this, update your Lusha field mapping so the value matches exactly what's configured in the Salesforce picklist.
Please enter "[field name]" (required field)
This error means a Salesforce field marked as required isn't included in your Lusha field mapping, so Salesforce is blocking the export because that field is empty.
To fix this, add the required Salesforce field to your Lusha field mapping at Settings → Integrations → Salesforce → Field mapping.
No such column "[X]" on entity "[Y]"
This error means a field referenced in your Lusha field mapping doesn't exist in Salesforce.
To fix this, either ask your Salesforce Admin to create the missing field, or remove the field from your Lusha field mapping.
Admin cannot connect the integration ("Something went wrong")
This error means Salesforce is blocking the Lusha app from connecting. Some Salesforce orgs block all third-party app connections by default.
To fix this:
In Salesforce Setup, go to Connected Apps OAuth Usage.
Find Lusha Push to Salesforce and unblock it.
Review your OAuth policies to confirm third-party app connections are permitted.
Adjust IP restrictions if needed to allow data push from Lusha.
The REST API is not enabled for this organization
This error means your Salesforce edition doesn't include Web Services API access, which Lusha requires to push contact data.
To fix this, upgrade to a Salesforce edition that includes API access. See Salesforce's documentation on API-enabled editions for details.
Record Type ID: This ID value isn't valid for the user
This error means the user doesn't have access to the Salesforce Record Type configured in the Lusha integration.
To fix this, either ask your Salesforce Admin to grant the user access to the relevant Record Type, or ask the Lusha Admin to disable the Record Type default or select a Record Type all users can access.
Cannot reference converted lead
This error occurs when Lusha tries to update a record owned by a deactivated Salesforce user.
To fix this:
Create a "General Owner" admin in Salesforce with full read/write access and reassign all objects owned by deactivated users, or
Go to Setup → User Interface and enable both Set Audit Fields upon Record Creation and Update Records with Inactive Owners, or create a permission set with Update Records with Inactive Owners enabled.
See Salesforce's documentation for additional guidance.
Owner is inactive
This error means the Salesforce user who owns the existing record has been deactivated, so Lusha can't update it.
To fix this, create a new Salesforce user and reassign records from deactivated owners, or enable the Update Records with Inactive Owners permission as described above.
If none of the above resolves your issue, contact Lusha Support using the chat icon in your dashboard or email [email protected].