Who can do this: Owners. Bullhorn needs to be connected.
Field mapping fills candidate fields with data from Bullhorn when you add a candidate from Bullhorn to a job submission list, for example salary, availability or a Bullhorn custom field.
Have these ready: the Bullhorn fields you want to bring in. If the Candidately field doesn't exist yet, create it first. See Add, rename or hide fields on candidate profiles.
Map a field
Click your name at the bottom left, then Settings.
Under Integrations, click Bullhorn.
Scroll to Field mappings (marked Beta). Under Candidate field mapping, click Add new field.
In the new row, pick the Bullhorn field on the left, then the Candidately field it should fill on the right. You can type to filter both lists. Pick fields of a similar type, for example a Bullhorn money field for Rate (per Year).
Click Save changes in the bar at the bottom.
To remove a mapping, click the X at the end of its row and click Save changes.
What happens next
When someone adds a candidate from Bullhorn to a list, the mapped fields come in with the candidate, along with name, job title, email, phone, address and skills. This works when you use Import candidate from Bullhorn on a list and when candidates are imported automatically from a connected Bullhorn job.
Your client only sees a mapped field if it's in the list's candidate appearance and has a value. See Choose what clients see on candidate profiles (candidate appearance).
Map fields from the job submission
Job submission field mapping works the same way, but reads the candidate's Bullhorn job submission instead of the candidate record. Use it for details that belong to one job, like the salary or start date agreed for that submission.
In Field mappings, under Job submission field mapping, click Add new field.
Pick the Bullhorn submission field and the Candidately field, then click Save changes.
It only runs on lists connected to a Bullhorn job. Candidately reads the candidate's most recent submission for that job.
Good to know
Mapping goes one way, from Bullhorn to Candidately, when the candidate is added. Edits you make in Candidately don't go back to Bullhorn.
Mapping is set once for your whole company. It isn't per list.
Each Candidately field can be mapped once, in either section.
If you map Job title, the job title from the CV replaces it when the CV is read. Mapped custom fields keep their Bullhorn value.
When a candidate is added to a list from an existing candidate profile, the mapping isn't run again. The list candidate gets the values from the profile.
If a Bullhorn select value doesn't exist as an option in Candidately, it's kept and shown with a Bullhorn icon.
To map stages to Bullhorn statuses, see Map submission stages to Bullhorn statuses.