Migrate from HiBob HRIS to Bullhorn ATS & CRM

HiBob's core People object maps to Bullhorn's Candidate record. We extract personal info (name, email, phone, address), employment status (active, inactive, terminated), start date, and job title. Employment type (full-time, part-time, contractor) maps to Bullhorn's employmentType field. Manager reporting lines from HiBob are preserved as a custom field or lookup to a parent Candidate record. Note that Bullhorn Candidate records do not natively store compensation bands or salary history — these require Custom Objects or Bullhorn's compensation fields if the Front Office edition is licensed.

HiBob's Job Catalog API exposes job roles, job families, and job family groups. Bullhorn has no native Job Profile object at the ATS tier. We create a JobProfile Custom Object (if available in the customer's edition) or map job title and department to custom text fields on the Candidate record. Job family groups map to a custom picklist field that we configure through Bullhorn's Field Mappings interface.

HiBob's org chart derives from manager relationships stored on the Employee object. Bullhorn has no native org chart. We create a ReportingLine Custom Object with employee reference, manager reference, and level number, or we use a hierarchical custom field structure. If the customer's Bullhorn edition limits Custom Objects (ATS Growth: 0, ATS: 2), we scope reporting lines as custom fields on the Candidate record and flag this limitation in the scope document.

HiBob's custom list fields return internal string IDs rather than display values. Bullhorn's Field Mappings interface accepts display values directly for drop-down and multi-select fields. We resolve HiBob's custom field IDs to display labels using the list metadata endpoint, then configure Bullhorn Field Mappings to match the value set exactly. Bullhorn requires that drop-down values be pre-loaded through their support channel before they appear in the UI, so we coordinate this provisioning step during schema design.

HiBob's Time Off API provides leave balances and request history. Bullhorn has no native time-off module. We create a TimeOff Custom Object with fields for employee reference, leave type, balance remaining, and request date. Pending approval requests are flagged separately and escalated to the customer's Bullhorn admin for manual resolution after cutover. If the Bullhorn edition limits Custom Objects, time-off balances are delivered as a CSV report for manual entry or a separate time-off platform decision.

HiBob tracks PDR cycles, ratings, goals, and review text. Bullhorn has no native performance management module. We create a PerformanceReview Custom Object linked to the Candidate record with fields for review period, rating, goals text, and reviewer. If the Bullhorn edition limits Custom Objects, review summaries migrate as note attachments on the Candidate record.

HiBob's Goals API stores Goal Types, Goals, and Key Results with progress data. Bullhorn has no OKR or goal-tracking module. Goals migrate to a Goals Custom Object with parent goal, key result, progress percentage, and status. OKR linkage to performance reviews requires manual re-linkage by the customer's HR admin post-migration.

HiBob engagement survey templates and historical response data have no Bullhorn equivalent. Bullhorn is a recruitment and candidate engagement platform, not an employee engagement tool. We do not migrate engagement survey data. We deliver a written inventory of active survey templates and response history for the customer's HR admin to evaluate as a standalone export. A separate engagement platform (Culture Amp, Lattice, or another) should be selected before migration.

HiBob onboarding workflows are configurable task templates assigned to new hires. Bullhorn's onboarding features are limited to candidate-facing tasks and document collection on the Candidate record. We do not migrate HiBob onboarding flows as executable workflows. We deliver a written inventory of active onboarding task templates, their assignees, and their completion states for the customer's Bullhorn admin to rebuild using Bullhorn's task assignment features or a dedicated onboarding platform.

HiBob document metadata (offer letters, contracts, certifications) is associated with employees. Bullhorn supports file attachments on Candidate records via its document management interface. We extract document metadata and binary files, then attach them to the corresponding Bullhorn Candidate record. Large document volumes require Bullhorn storage capacity review before migration.

HiBob stores compensation bands, salary structures, and compensation history. Bullhorn Front Office editions support a compensation field on the Candidate and Placement records. For ATS-tier customers, compensation history migrates to a Compensation Custom Object or is flagged as a manual re-entry item. Pay rate and bill rate fields on Bullhorn Placement records are mapped from HiBob compensation data where the employment type indicates a contractor or temporary placement relationship.

HiBob's Workforce Planning module handles headcount planning, budget, and opening data. Bullhorn has no workforce planning or headcount budgeting module. We do not migrate workforce planning data. Planning data is delivered as a CSV export for the customer's FP&A team to load into a dedicated planning tool or spreadsheet.