Migrate from Apex Human Capital Management to Bullhorn ATS & CRM

Apex Employee records map to Bullhorn Candidate records using the employee core fields (name, address, phone, email, hire date, job title, department) as Candidate standard fields. The Apex Employee ID is preserved in a Bullhorn custom field (e.g. apx_employee_id__c) as the dedupe key and cross-reference for any downstream reconciliation. Employment status (active/terminated) in Apex maps to Candidate status in Bullhorn, but the destination status taxonomy is recruiting-specific (lead, applicant, placed, do not contact) rather than HR-specific.

Pay rate, salary, bonus, and commission history from Apex extract as a compensation timeline. Bullhorn's standard Candidate object does not include a compensation history sub-object; these fields map to Bullhorn custom fields (e.g. apx_current_salary__c, apx_target_pay__c, apx_bonus_history__c) that Bullhorn Support provisions before load. The customer decides during scoping whether full historical compensation (multiple years) is retained in Bullhorn or archived externally.

Apex department hierarchy and reporting lines export as a flat list with parent references. Bullhorn does not have a native org chart object; department and division information from Apex maps to Bullhorn Candidate custom fields or to the JobOrder BusinessSector field if placements are tied to departments in the customer's staffing model. We reconstruct the tree and flatten it to the most granular unit that maps cleanly.

Payroll run history, earnings, deductions, and tax withholdings stored in Apex have no Bullhorn equivalent. Bullhorn is a recruiting ATS, not a payroll system. We export the payroll register data as a structured CSV archive that the customer's finance team retains outside Bullhorn. If the customer needs to reference historical payroll data during candidate billing or contractor rate negotiations, we document the payroll export schema so it can be joined to Bullhorn Candidate records via the apx_employee_id__c key in a BI tool or spreadsheet.

Federal, state, and local tax registration IDs and jurisdiction-specific withholding rules per employee in Apex do not map to any Bullhorn object. Bullhorn does not process payroll tax and has no tax jurisdiction taxonomy. We extract the full jurisdiction taxonomy from Apex as a reference CSV with the employee's apx_employee_id__c as the join key. The customer's payroll team retains this data for W-2 processing and any future payroll system configuration.

Current PTO accrual balances and carryover snapshots export from Apex. Bullhorn's standard schema has no accrual balance field on Candidate. We map current balance values to Bullhorn custom fields (e.g. apx_pto_balance__c, apx_sick_balance__c) provisioned via Bullhorn Support. Accrual rate logic, carryover rules, and cap configurations are client-specific Apex tables that do not migrate automatically; we document every accrual policy found in the export and provide a policy inventory so the customer's HR team can rebuild rules in their chosen time-off management tool.

Health, dental, vision, and retirement plan elections per employee export as an election snapshot including coverage start dates and carrier plan IDs. Bullhorn has no benefits administration module and no object to store election records. We export the full benefits election data as a structured archive keyed to the Apex Employee ID. The customer's benefits administrator retains this data for COBRA processing, benefits reconciliation, or future enrollment in a payroll or benefits platform.

Clock-in/out records and hours worked per pay period export per employee. Bullhorn standard objects do not include time entry records. If the customer licenses Bullhorn's Sirenum WFM module, we coordinate with Sirenum data migration separately; otherwise we export time entry summaries as a structured archive keyed to apx_employee_id__c for the customer's payroll or finance team to reconcile against their current payroll processor.

Onboarding documents, offer letters, I-9s, and employee files stored as binary blobs or linked URLs in Apex export with filenames and employee associations preserved. We attach these to the corresponding Bullhorn Candidate record via Bullhorn's document upload API, mapping the Apex employee record to the Bullhorn Candidate ID. Resume files and certifications attach as ContentDocument records; employment contracts and offer letters attach as Candidate document records. We flag any file format that Bullhorn's document handler does not support and provide an alternative download path.

1095-C forms and coverage measurement period records export with employee associations intact. Bullhorn has no ACA compliance module. We export the full ACA record set as a structured archive keyed to apx_employee_id__c for the customer's HR and compliance team to retain for IRS filing purposes. This data does not load into Bullhorn but must be preserved for audit trails regardless of the payroll system in use.

If Apex HCM stores open job requisitions or position records alongside employee data, these map to Bullhorn JobOrder. Job title, department, employment type, and pay rate range map to JobOrder standard fields. Skills requirements and job description map to Bullhorn custom fields or the Description field. We identify whether position data exists in the Apex export during discovery.

If the customer uses Apex HCM to track staffing placements or contractor assignments (a common configuration for staffing firms that use Apex internally alongside their recruiting operations), placement records map to Bullhorn Placement. The Apex employee record for a placed contractor maps to the Candidate record; the client or assignment maps to the Bullhorn ClientCorporation or JobOrder. We validate placement-to-candidate linkage during discovery to confirm this mapping applies.