Migrate your ELMO Software data

Employee records are the primary object in ELMO HR Core. The API exposes GET /users and GET /users/{id} endpoints returning name, contact details and employment metadata. We migrate employee profiles as the anchor record and preserve all linked objects against the same employee ID.

Positions define the organisational hierarchy and role assignments. Exposed via GET /positions in the ELMO User API v1. We map each employee's position_id to the destination's job title or role field.

Departments are exposed via GET /departments in the ELMO User API. We preserve the full department tree and reassign employees to matching department records on the destination side.

Locations are available via GET /locations and include physical address and timezone information. We migrate these as branch or office entities applicable to rostering and compliance.

Legal Entity records define payroll entities and ABN/ACN-level employer records required for AU/NZ payroll. Exposed via GET /legal-entities. We preserve these as-is to maintain payroll configuration integrity.

Employment details include start date, employment type (full-time/part-time/casual), pay frequency and superannuation details. These are stored as a separate GET /employment-details endpoint. We map each employment record to the destination's employee profile fields and flag any fields that require re-entry due to schema differences.

ELMO's payroll calendar defines pay periods, pay run dates and STP reporting cycles. These are organisation-level configurations rather than per-employee records. We export the calendar definition and advise customers to reconfigure it on the destination platform as part of the cutover checklist.

Leave requests and leave balances are exposed via GET /leave-requests (BETA endpoint per ELMO docs). Balances are decorated with entitlement rules and accrual logic. We extract current balance snapshots and map them to the destination's leave management system, noting that accrual logic is not exportable and must be recalculated.

Leave types (annual, sick, parental, etc.) are configurable at the organisation level. We export the full leave type schema including entitlement rules and map them to the closest matching leave categories on the destination platform.

Groups in ELMO HRIS represent organisational units for access control and reporting. Exposed via GET /groups in the Unified.to integration. We migrate group membership alongside employee records and flag any custom access-control logic that requires manual reassignment.

ELMO supports configurable metadata fields per organisation. The API exposes GET /configurable-fields-meta to retrieve field definitions. We extract custom field values per employee record and map them to destination custom fields, noting that field type differences (dropdown vs free text) may require transformation.