Migrate from Employment Hero to Bullhorn ATS & CRM

Employment Hero Employee records map to Bullhorn Candidate records. The core fields (name, email, phone, location, start date) migrate directly. We map the Employee's employment status (active, contractor, terminated) to Bullhorn Candidate status (Active, Placed, Passive, Do Not Contact). Address, date of birth, and tax file number equivalents do not have direct Bullhorn fields and are held in a custom field block for HR review if required by the customer's compliance team. We do not migrate employment-of-record data such as superannuation details, tax file numbers, or bank account information because Bullhorn is not a payroll system.

Employment Hero's SmartMatch recruitment module stores job postings and candidate applications. These map to Bullhorn Job (the job order) and the associated Candidate submissions. We retrieve job postings via GET /api/v1/job_posts and map title, description, location, employment type, and salary to Bullhorn Job fields (title, description, address, employmentType, payRate). Candidate applications map to Bullhorn JobApplication records linked to the Job and Candidate. If the customer has a large volume of historical job postings, we migrate the most recent 12-24 months and document the full job history for manual import if needed.

Employment Hero Teams (API label: teams) represent organisational units and team membership. These map to Bullhorn Corporate structure (corporations, divisions, branches) or to Bullhorn Teams if the customer's Bullhorn edition includes team-based user permissions. We preserve team membership by mapping the team membership list to the appropriate Bullhorn Corporate or Branch assignment on the Candidate record. Users from Employment Hero map to Bullhorn User records by email match for placement assignment purposes.

Employment Hero notes attached to employee records migrate to Bullhorn Note records linked to the corresponding Candidate. Employment contracts and compliance documents migrate as Bullhorn ContentDocument records attached via ContentDocumentLink to the Candidate. File names and document associations are preserved; the document content itself migrates by download from Employment Hero and upload to Bullhorn. Any document stored outside the platform (linked files, cloud storage references) is flagged for manual retrieval.

Employment Hero Cost Centres represent departments or cost-attribution units used in rostering and payroll attribution. Bullhorn does not have a native Cost Centre object. We map Cost Centres to Bullhorn Branch records (if the customer's edition supports branches) or to a custom Candidate field costCentre__c. The customer chooses the mapping strategy during scoping based on whether they use Bullhorn's multi-branch feature. Cost-centre hierarchy (parent-child relationships) is preserved as a Branch parent-child structure in Bullhorn if Branch is the chosen destination.

Leave entitlements and accrued balances from Employment Hero map to Bullhorn custom Candidate fields if the staffing firm tracks leave for their placed contractors. Annual leave balance, sick leave balance, and pending leave requests migrate as custom numeric fields on the Candidate record. However, Bullhorn is not a leave management system; the customer must confirm whether leave tracking is required in Bullhorn or will be handled by a separate HR system post-migration. We document the leave inventory mapping and flag any leave types without a Bullhorn field destination.

Historical pay run records and payroll history from Employment Hero do not migrate to Bullhorn. Bullhorn is not a payroll platform and has no pay run, earnings, or deduction objects. We export the payroll history as a structured CSV inventory (pay period, gross pay, net pay, pay components) and deliver it to the customer as a reference document for their HR or finance team to reconcile in their new payroll system post-migration. We also document the employing entity attribution per employee so that the customer's new payroll platform can be configured with the correct legal employer.

Award configurations (Australian industrial awards, UK pay frameworks) in Employment Hero are plan-gated and often require manual setup. Bullhorn does not store award classifications because it is not a payroll system. We document the award configuration per employee (award name, classification, pay point) as a written inventory that the customer's HR team can use to configure their new payroll platform. We flag any employees whose award was not present in Employment Hero's out-of-box library, as those require manual reconfiguration regardless of destination platform.

Employment Hero custom fields are organisation-scoped and can be defined on the Employee object. We retrieve the custom field schema via GET /api/v1/organisations/:id/custom_fields and recreate equivalent custom fields on the Bullhorn Candidate object before migration. Field data types are mapped: text fields to Text, numeric fields to Number, date fields to Date, checkbox fields to Checkbox. Multi-select or tag-style custom fields migrate to Bullhorn Text fields with comma-separated values if the destination Bullhorn edition does not support multi-select picklists on Candidate. We flag any unmappable field types for manual post-migration review.

Approved expense claims from Employment Hero do not migrate to Bullhorn. Bullhorn is not an expense management system and has no expense line-item or receipt-tracking objects. We extract approved expense claims as a structured CSV (employee, claim date, total amount, status) and deliver it as a written inventory. Receipts and line-item detail are exported as file attachments for the customer's finance team to reconcile in their new expense management platform post-migration.

Benefit plans and employee benefit enrollments in Employment Hero are plan-gated (HR Premium and Platinum) and are HR-administration records that have no Bullhorn equivalent. Bullhorn does not store benefit plan configurations or enrollment records. We document active benefit enrollments per employee (benefit type, provider, coverage level, employee contribution) as a written inventory for the customer's HR team to configure in their new benefits administration platform or to discuss with a benefits broker post-migration.

Employment Hero onboarding workflows include document checklists and task steps tied to new hires. Bullhorn does not have an employment onboarding module; onboarding workflows and employment contract generation are not part of the ATS data model. We map active onboarding tasks per employee (task name, assignee, due date, completion status) to a written inventory that the customer's Bullhorn admin can use to configure Bullhorn Tasks or a separate onboarding tool. We flag any custom template steps that require manual rebuild in the customer's chosen onboarding platform.