The Lusha integration with Bullhorn lets you map Lusha data fields directly to your Bullhorn records - so enriched contact data lands in the right place automatically, without jumping between platforms.
💡 Note: Only Admins and Managers can edit integration settings. You must be an admin in both Lusha and Bullhorn to set up the integration.
- Log in to your Lusha dashboard and go to the Integrations tab.
- Select Bullhorn from the table and click Connect.
- Sign in to Bullhorn when prompted (skipped automatically if you're already logged in).
- Click Continue to field mapping.
- Under Field mapping, you'll see four record types: Leads, Candidates, Contacts, and Companies. Map Lusha fields to the corresponding Bullhorn fields for each record type.
To allow Lusha to overwrite data in existing Bullhorn records, enable Allow Override.
💡 Note: When adding a new field, the field type in Bullhorn must match the Lusha field type. Each field can be remapped to a different Bullhorn field to control exactly where enriched data lands.
- Select a record type (Leads, Candidates, Contacts, or Companies).
- Click + Add field and choose Predefined Value.
- Select a Bullhorn field from the available options.
- Enter your predefined value.
- Click Save changes before switching tabs.
Conditional field mapping lets you set secondary field values that update automatically when an email or phone field is enriched — useful for routing leads or flagging record status.
- In your Lusha account, go to Field mapping.
- Click Advanced next to the Email 1 or Phone 1 field.
In the Map dropdown, enter text to describe the value — this creates a predefined field that updates after the parent field is enriched.
Click Apply, then Save Changes at the bottom of the page.
Admins can select which object types users can export to Bullhorn. When a toggle is off, users can only save to existing Bullhorn accounts — not create new ones.
To manage export preferences, go to Field mapping → Settings tab and choose the object types users can export.
💡 Note: Settings apply to all team members in your account.
The Bullhorn Identifiers feature checks whether a contact, lead, or account already exists in your Bullhorn CRM before saving - preventing duplicate records and unnecessary credit spend.
To set up: go to Field mapping → Bullhorn Identifier tab and map the fields.
💡 It's recommended to keep the default Identifier mapping as-is to ensure optimal duplicate detection.
Identifier logic for leads, candidates, and contacts matches on: full name + company name/website, or email address. For companies: company name or website (domain URL).
When autocomplete is enabled, the account name fills in automatically based on matching records in your CRM.
If you modify your mapping and need to revert to the original settings, use the tables below.
| Lusha field | Bullhorn field |
|---|---|
| Full Name | Name |
| Email 1 | |
| Phone 1 | Phone |
| Email 2 | Email 2 |
| Phone 2 | Phone 2 |
| Last Name | Last Name |
| First Name | First Name |
| Predefined | Lead Source |
| Job title | Occupation |
| Lusha field | Bullhorn field |
|---|---|
| Full Name | Name |
| Email 1 | |
| Phone 1 | Phone |
| Email 2 | Email 2 |
| Phone 2 | Phone 2 |
| Source - Predefined | Source |
| lastName | Last Name |
| firstName | First Name |
| Job title | Occupation |
| Lusha field | Bullhorn field |
|---|---|
| Email1 | |
| Phone1 | Phone |
| Job title | Title |
| Last Name | Last Name |
| First Name | First Name |
| Departments | Department |
| Lusha field | Bullhorn field |
|---|---|
| Company Name | Name |
| Company Phone | Phone |
| Website | Company URL |
| Company Main Industry | Industry table |
| Employees | Num Employees |
| Description | Company Description |
For a full reference of available Lusha fields, see Fields for field mapping and descriptions.