Skip to main content
This reference tables every field Lusha makes available for field mapping across all CRM integrations. Use it to understand what each field contains and which data type to match on the CRM side.

​
Contact and lead fields

​
Company and account fields

Lusha doesn’t enforce a maximum character length on these fields - values are sent as plain strings with no truncation. Your CRM’s field size decides whether a record lands: if a value is longer than the CRM field, the CRM rejects it and that record’s export fails (for example, a STRING_TOO_LONG error in Salesforce). When sizing your CRM fields for mapping, use generous limits rather than tight ones:
Simplest rule of thumb: 255 characters for text fields, 50 for phone fields.
If you’re on Salesforce, some standard fields have fixed limits you can’t raise (for example, FirstName at 40 characters, Title at 128, Phone at 40). These rarely cause failures, but check them against your setup.

​
Value mapping for picklist fields

When you map Main Industry, Seniority, or Department to a CRM field configured as a picklist, a Value mapping option will appear inline in that field row. This lets you match Lusha’s values to your CRM’s own picklist options. If a Lusha value has no matching entry set up in value mapping, the export will fail for that contact. You must map every Lusha value your team is likely to export. To configure value mapping:
1

Find the picklist field row

In the field mapping table, find the Main Industry, Seniority, or Department row.
2

Click Value mapping

Click Value mapping in that row (only appears when the mapped CRM field is a picklist).
3

Match Lusha values to CRM values

In the dialog, select a Lusha value on the left and your matching CRM picklist value on the right.
4

Add more value mappings

Click + Add to map additional values.
5

Apply and save

Click Apply, then Save changes.
Value mapping is only available when the CRM field is configured as a picklist.