# Bullhorn integration

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.

blockquote
💡 Note: Only Admins and Managers can edit integration settings. You must be an admin in both Lusha and Bullhorn to set up the integration.

## How to connect and configure field mapping

1. Log in to your [Lusha dashboard](https://dashboard.lusha.com/) and go to the **[Integrations tab](https://dashboard.lusha.com/lusha-integrations)**.
2. Select **Bullhorn** from the table and click **Connect**.
3. Sign in to Bullhorn when prompted (skipped automatically if you're already logged in).
4. Click **Continue to field mapping**.
5. 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.


img
To allow Lusha to overwrite data in existing Bullhorn records, enable **Allow Override**.

blockquote
💡 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.

## How to add predefined value fields

1. Select a record type (Leads, Candidates, Contacts, or Companies).
2. Click **+ Add field** and choose **Predefined Value**.
3. Select a Bullhorn field from the available options.
4. Enter your predefined value.
5. Click **Save changes** before switching tabs.


## Conditional field mapping

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.

1. In your Lusha account, go to **Field mapping**.
2. Click **Advanced** next to the **Email 1** or **Phone 1** field.


img
1. In the **Map** dropdown, enter text to describe the value — this creates a predefined field that updates after the parent field is enriched.
2. Click **Apply**, then **Save Changes** at the bottom of the page.


img
## Account export preferences

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](https://dashboard.lusha.com/lusha-integrations/advancedSettings/bullhorn/settings)** and choose the object types users can export.

blockquote
💡 Note: Settings apply to all team members in your account.

img
## Bullhorn Identifiers

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](https://dashboard.lusha.com/lusha-integrations/advancedSettings/bullhorn/crmIdentifiers)** and map the fields.

blockquote
💡 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).

img
img
img
## Autocomplete settings

When autocomplete is enabled, the account name fills in automatically based on matching records in your CRM.

img
## Default field mapping

If you modify your mapping and need to revert to the original settings, use the tables below.

## Leads

| **Lusha field** | **Bullhorn field** |
|  --- | --- |
| Full Name | Name |
| Email 1 | Email |
| 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 |


## Candidates

| **Lusha field** | **Bullhorn field** |
|  --- | --- |
| Full Name | Name |
| Email 1 | Email |
| Phone 1 | Phone |
| Email 2 | Email 2 |
| Phone 2 | Phone 2 |
| Source - Predefined | Source |
| lastName | Last Name |
| firstName | First Name |
| Job title | Occupation |


## Contacts

| **Lusha field** | **Bullhorn field** |
|  --- | --- |
| Email1 | Email |
| Phone1 | Phone |
| Job title | Title |
| Last Name | Last Name |
| First Name | First Name |
| Departments | Department |


## Companies

| **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](/user-guide/integrations-basics/fields-for-field-mapping-and-descriptions).