Skip to main content
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.
Only Admins and Managers can edit integration settings. You must be an admin in both Lusha and Bullhorn to set up the integration.

Export size and background processing

You can export up to 1,000 contacts to Bullhorn in a single job. Exports of up to 25 contacts process in real time. Larger exports run in the background in 20 batches - you can keep working while the job runs. If your selection exceeds 1,000 contacts, Lusha exports the first 1,000 and leaves the rest marked Not exported, so your next run picks up automatically. The 1,000-record cap is a Bullhorn platform limit and cannot be changed.
Only one CRM export can run at a time per user. To track export status and review any failed contacts, go to Account → CRM export.

How to connect and configure field mapping

1

Open the Integrations tab

Log in to your Lusha dashboard and go to the Integrations tab.
2

Connect Bullhorn

Select Bullhorn from the table and click Connect.
3

Sign in to Bullhorn

Sign in to Bullhorn when prompted (skipped automatically if you’re already logged in).
4

Continue to field mapping

Click Continue to field mapping.
5

Map fields for each record type

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.
Field mapping screen for Bullhorn record types
To allow Lusha to overwrite data in existing Bullhorn records, enable Allow Override.
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

Select a record type (Leads, Candidates, Contacts, or Companies).
2

Add a predefined value field

Click + Add field and choose Predefined Value.
3

Select a Bullhorn field

Select a Bullhorn field from the available options.
4

Enter your predefined value

Enter your predefined value.
5

Save your changes

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

Open Field mapping

In your Lusha account, go to Field mapping.
2

Click Advanced next to Email 1 or Phone 1

Click Advanced next to the Email 1 or Phone 1 field.
Advanced conditional mapping option next to a field
3

Describe the value in the Map dropdown

In the Map dropdown, enter text to describe the value - this creates a predefined field that updates after the parent field is enriched.
4

Apply and save

Click Apply, then Save Changes at the bottom of the page.
Conditional mapping dropdown for a predefined field

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 and choose the object types users can export.
Settings apply to all team members in your account.
Object types available for account export preferences

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 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).
Bullhorn Identifier field mapping screen
Identifier matching logic for leads, candidates, and contacts
Identifier matching logic for companies

Autocomplete settings

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

Default field mapping

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

Leads

Candidates

Contacts

Companies

For a full reference of available Lusha fields, see Fields for field mapping and descriptions.