Migrate from Employment Hero to BambooHR

Employment Hero employee records map directly to BambooHR employees. Core fields including name, date of birth, contact details, employment status, hire date, and location transfer cleanly. We resolve the location assignment by extracting the employee's employing entity and primary work location from Employment Hero and mapping to the nearest BambooHR location. Any employees without a clear location assignment are flagged for manual review before import.

Employment Hero's multi-entity model (separate ABNs and legal employers) has no direct BambooHR equivalent. Each distinct employing entity maps to a BambooHR Location, which captures the legal employer name and address. If the organisation operates a single employing entity, this is straightforward. If multiple ABNs exist, we consolidate them into a flat location list and note the ABN-to-location mapping in the migration inventory for the customer's HR admin to maintain going forward.

Base salary, pay frequency, and earning items migrate to BambooHR's Pay fields. Non-standard earning components (allowances, bonuses, superannuation) are mapped to BambooHR's custom Pay types or stored as notes on the employee record depending on whether the customer's BambooHR plan supports the pay component structure. We flag any earning types that do not map cleanly to BambooHR's supported pay fields for HR admin review.

Historical pay run records export from Employment Hero via CSV/XLSX and migrate to BambooHR as pay history entries. We sequence pay runs chronologically by pay period, chunking exports to respect the 100-requests-per-minute API ceiling during any API-mediated re-import. BambooHR's payroll add-on is US-only; international customers use this migration to establish an employee data baseline and plan a separate payroll provider migration or integration.

Leave entitlements, accrued balances, and pending requests migrate to BambooHR Time Off. Leave type names transfer directly; accrual rates and carry-over rules require HR admin review because BambooHR's leave configuration differs from Employment Hero's award-linked accrual engine. Any leave types not supported in BambooHR (for example, extended unpaid leave categories) are logged for manual post-migration configuration.

Employment Hero cost centres map to BambooHR departments. We preserve the full cost-centre hierarchy from GET /api/v1/organisations/:id/cost_centres, re-creating the department structure in BambooHR before any employee import so that the department assignment is satisfied at the time of record insert. Department heads migrate as manager assignments on the corresponding employee records.

Employment Hero Teams (backward-compatible with the API's 'teams' namespace) correspond to the group membership in BambooHR. Team membership transfers as a direct assignment to each employee. If the organisation uses teams for approval routing, we note this dependency and flag it for the HR admin to re-establish in BambooHR's approval workflow configuration.

Employment Hero custom fields are organisation-scoped and must be explicitly recreated in BambooHR before any employee record that references them is imported. We retrieve the custom field schema via GET /api/v1/organisations/:id/custom_fields, map field types to their nearest BambooHR equivalents (text, number, date, dropdown, checkbox), and deploy the field definitions to BambooHR before migration. Any custom fields that cannot be represented in BambooHR are logged for manual review.

Timesheet data exports from Employment Hero and migrates to BambooHR's Time Tracking module (add-on feature). Clocking records and manual timesheet entries map to work types and hours. Cost attribution from the source timesheet is stored as a note or custom field in BambooHR since BambooHR's Time Tracking does not natively support cost-centre attribution.

Employment contracts, compliance documents, and onboarding files transfer as file-based imports. We preserve file names and associate each document with the correct employee record in BambooHR using the document naming convention and any metadata available in the source export. Large document sets are chunked by employee batch to avoid timeout-induced gaps. We note any file size limits or format restrictions in the destination during scoping.

Employment Hero onboarding workflows include document collection and task checklists tied to new hires. Workflow templates do not migrate 1:1. We map active onboarding tasks and document collection requirements to BambooHR's onboarding checklist format and deliver a written handoff document specifying which tasks, document types, and manager notifications the HR admin should configure in BambooHR post-migration.