Migrate your Employment Hero data

The core record object. We migrate employee profiles with employment status, start dates, location, employing entity, and owner assignment. Standard fields map cleanly across systems; we validate required fields per plan tier before import.

Base salary, pay frequency, and earning items are supported but vary by plan tier (HR Standard vs Premium vs Platinum). We preserve pay schedule and salary history, mapping any non-standard earning codes to destination equivalents.

Historical pay run records can be exported via CSV/XLSX from Payroll classic or the web platform. We sequence these chronologically, chunking by pay period to avoid exceeding API rate limits during re-import.

Leave entitlements, accrued balances, and pending requests are tied to award classifications. We migrate active balances and flag any leave types not supported in the destination platform for manual review.

Custom fields are organisation-scoped and can be created on the Employee object. We retrieve the custom field schema via GET /api/v1/organisations/:id/custom_fields before migration and apply the same field structure at the destination.

Cost Centres represent departments or cost-attribution units used in rostering and payroll attribution. The API exposes GET /api/v1/organisations/:id/cost_centres. We preserve the full cost-centre hierarchy and reassign employee cost-centre mappings during import.

Teams correspond to the 'Groups' label in the current UI; the API retains 'teams' in endpoint names and field responses for backward compatibility. No schema change is needed — we migrate the team membership records as-is.

Timesheet data can be exported from the platform or pushed via API. We handle both clocking records and manual timesheet entries, mapping work types and cost attribution to destination equivalents.

Employment contracts, compliance documents, and onboarding files can be exported. Document migration is file-based; we preserve file names and association to the correct employee record, noting any size limits in the destination platform.

Expense claims with line items, approval status, and receipts are supported. We migrate approved claims and map the approval workflow status to the destination's equivalent workflow state.

Benefit plans and employee enrollments are plan-gated. We map active benefit enrollments and flag any benefit types not available in the destination for HR review prior to cutover.

An employing entity is a separate business or ABN operating under the same payroll file. Multi-entity organisations require us to map employees to the correct employing entity during import — failure to do so causes payroll attribution errors.

Award configurations (Australian industrial awards, UK pay frameworks) are plan-gated and may require manual setup if the specific award is not in the out-of-box library. We flag missing awards during scoping so the customer can configure them before go-live.

Onboarding workflows include document collection and task checklists tied to new hires. Workflow templates may not migrate 1:1; we map active onboarding tasks and flag any custom template steps that need rebuilding at the destination.

Job postings, applications, and candidate records are part of the SmartMatch recruitment module. We migrate candidate profiles and application status, mapping to the destination's recruitment pipeline structure.