Migrate from Workforce Analytics to Bullhorn ATS & CRM

Workforce Analytics Employee records map to Bullhorn Candidate. We extract firstName, lastName, email, phone, jobTitle, and hireDate into Bullhorn Candidate fields. The source employee ID is stored in a Bullhorn custom text field as a reference key for downstream lookups. Active employees in the recruiting pipeline become Bullhorn Candidates; former employees are migrated as Candidates with status set accordingly.

Workforce Analytics employees who also function as internal contacts, HR liaisons, or approvers within the Bullhorn system map to ClientContact. The mapping uses the same employee fields but targets the ClientContact entity so that Bullhorn can track relationships with internal stakeholders separate from external candidate and client records.

Workforce Analytics organizational units and departments map to Bullhorn ClientCorporation. The department name becomes the ClientCorporation name, and the business sector becomes the industry classification. Department headcount and division hierarchy are stored in Bullhorn custom fields. A custom text field holds the parent department identifier for hierarchy reconstruction.

Workforce Analytics positions map to Bullhorn JobOrder. The position title becomes the jobTitle, the employment type (full-time, contract, part-time) maps to employmentType, and the jobDescription field carries the position summary. If the customer uses Bullhorn for both internal staffing and external candidate placement, each Workforce Analytics position becomes a JobOrder with status reflecting its current filling state.

The Workforce Analytics manager-employee relationship is mapped by adding a custom Candidate or ClientContact text field (managerName__c) and optionally a Manager ID lookup field. After migration, Bullhorn's hierarchy is reconstructed by matching manager IDs from the source to Bullhorn user or contact records. Bullhorn does not have a native employee org chart; this configuration enables reporting queries by manager name.

Workforce Analytics employmentStatus (active, on-leave, terminated, suspended) has no native Bullhorn equivalent. We create a Bullhorn Candidate custom picklist field (employmentStatus__c) with values matching the source status vocabulary. A workflow or Bullhorn Automation rule can be configured by the customer's admin to set Candidate status (active, archived) based on employmentStatus__c after migration.

Each Workforce Analytics effective-dated employment change (position change, status change, compensation adjustment, promotion) is stored as a separate time-slice record. We map these to Bullhorn Candidate WorkHistory entries with the effective date as startDate, the next slice date minus one day as endDate, and the position title as jobTitleName. Bullhorn WorkHistory is designed for recruiting resumes, not HRMS time-slices; we migrate the data as-is and store the original effective date in a custom field for audit fidelity.

Workforce Analytics compensation fields (salary, hourlyRate, payFrequency, bonus) map to Bullhorn Candidate custom fields. We use numeric field types for salary and hourly rate rather than text to preserve analytical capability. A Bullhorn custom text field holds the original payFrequency value for reference. Bullhorn edition determines whether these are simple custom fields or custom object entries; we recommend simple custom fields on the Candidate entity for compensation data to avoid consuming custom object capacity.

Workforce Analytics performance ratings (ratings, scores, review dates, review cycle) map to a Bullhorn Custom Object linked to the Candidate record. Bullhorn custom objects support up to 10 on Front Office Growth and Enterprise editions, but only 2 on standard Bullhorn ATS and none on ATS Growth. We create this custom object only where the customer's Bullhorn edition supports it and note the constraint during scoping. Performance review scores are stored as numeric fields; review dates use Bullhorn date field type.

Workforce Analytics retention signals such as flight risk, tenure, engagement score, and last review date map to a Bullhorn Custom Object linked to the Candidate. Tenure is computed from originalHireDate in Workforce Analytics and stored as a numeric field in Bullhorn. Bullhorn has no native engagement scoring; this custom object carries the source signals so that the customer retains the data even if the scoring model is rebuilt in Bullhorn Automation post-migration. Subject to the same Bullhorn edition limits as the Performance Review custom object.

Candidates sourced externally to Workforce Analytics and tracked as external recruits map directly to Bullhorn Candidate without transformation. Email, phone, skills, and work history migrate via the same Candidate work history mapping described above. The source system of record identifier is preserved in a custom Bullhorn field so that record lineage is traceable post-migration.

Workforce Analytics custom HRMS fields that do not map to standard Bullhorn Candidate or JobOrder fields are evaluated during discovery. Fields with simple data types (text, number, date, picklist) become Bullhorn Candidate or JobOrder custom fields. Fields with complex structures or that reference other HRMS entities become Bullhorn Custom Objects. The customer chooses which custom fields to prioritize; Bullhorn's 55-field limit per custom object and the 2-10 custom object cap by edition may require the customer to defer some low-priority fields to post-migration.