Migrate from ELMO Software to BambooHR

ELMO Employee records (exposed via GET /users and GET /users/{id}) map to BambooHR Employee records. We extract first name, last name, preferred name, date of birth, gender, address, phone, personal email, and emergency contact fields. The ELMO employee ID is stored in a BambooHR custom field elmo_employee_id__c as a dedupe and audit reference. Active and inactive employment status maps directly.

ELMO Positions (GET /positions) define job title and role within the organisational hierarchy. We map each employee's assigned position to the BambooHR Job Title field. Where ELMO positions include seniority or classification prefixes, we strip the prefix or preserve it as a custom field depending on the customer's reporting requirements.

ELMO Departments (GET /departments) map directly to BambooHR Departments. We preserve the full department tree so that parent-child relationships render correctly in BambooHR's org chart. Employees reassign to matching department records during the employee import phase.

ELMO Locations (GET /locations) include physical address and timezone. BambooHR does not have a native Locations object; we store location as a custom field on the employee's Job tab (address fields) and flag any ELMO location used for rostering or compliance reporting as a separate custom field set requiring admin review.

ELMO Legal Entity records (GET /legal-entities) define ABN/ACN-level employer entities required for AU/NZ payroll. BambooHR has no native multi-entity concept; we create a custom List single-answer field called Payroll Entity on the Job tab and map each ELMO Legal Entity value to a matching list option. Organisations with multiple ELMO Legal Entities that need separate payroll runs should plan a parallel payroll vendor selection.

ELMO Employment Details (GET /employment-details) include start date, employment type (full-time/part-time/casual), pay frequency, and superannuation details. BambooHR stores employment type and start date natively; pay frequency, superannuation fund, and TFN migrate as custom fields on the Job tab. Employment history (multiple past employments) migrates as rows in a BambooHR custom table if the customer requires historical tracking.

ELMO leave balances are decorated with entitlement rules and accrual logic from BETA-rated endpoints. We extract the current balance snapshot per employee per leave type and map to BambooHR Time Off types (Annual, Sick, Personal, and custom). Because the ELMO leave request endpoint is BETA, we cross-validate extracted balances against payroll reports exported directly from ELMO's UI before importing into BambooHR. Leave type entitlement rules (accrual rates, carryover limits) are documented as a written spec for the customer's BambooHR admin to configure post-migration.

ELMO configurable leave types (annual, sick, parental, carer's, purchased leave, etc.) map to BambooHR Time Off types, which customers configure under Settings > Time Off > Time Off Types. We export the full leave type schema including whether a type accrues, lapses, or is unlimited, then deliver a leave-type configuration worksheet. Any ELMO leave types without a BambooHR equivalent are flagged for the admin to create as custom types.

ELMO Groups (GET /groups) represent organisational units for access control and reporting. BambooHR does not enforce role-based access groups; we migrate group membership as Tags on the relevant Employee records. The customer's admin reviews the tag list post-migration and determines whether tags should be used for reporting segmentation or archived.

ELMO Configurable Fields (GET /configurable-fields-meta) store per-employee custom metadata unique to each organisation. We extract field definitions and per-employee values during scoping, then create matching custom fields in BambooHR (custom text, number, date, or list fields) before employee import. Multi-select configurable fields in ELMO map to BambooHR multi-select fields; single-select map to list fields. Custom field values migrate alongside employee records in the same import batch.