Migrate from ELMO Software to Crelate

ELMO employee records from HR Core map to Crelate Candidate profiles. We extract name, contact details, employment status, start date, position title, department, and location from ELMO's GET /users endpoint. Employee email becomes the primary dedupe key in Crelate. Custom configurable fields on the employee record migrate to Crelate's custom candidate fields, which we define during schema design. Active employees who are also hiring targets may carry a separate candidate record for internal mobility roles.

ELMO positions from GET /positions define job title, reporting line, and organisational hierarchy. These map to Crelate Job Orders where position title becomes the job title, and the position description migrates to the job description field. Seniority level, job family, and employment type (full-time/part-time/casual) from the ELMO position record migrate to corresponding Crelate job order fields. Multiple ELMO positions with identical titles are deduplicated into a single Crelate Job Order with a note in the migration log.

ELMO department records from GET /departments preserve the full organisational tree. We import the department hierarchy as Crelate department tags or hiring team assignments depending on whether the customer uses Crelate's team-based access model. Child departments are created as sub-tags under parent department names. The department-to-recruiter assignment migrates as a Crelate team membership record.

ELMO location records from GET /locations include physical address, city, state, and timezone. These migrate to Crelate office records, which are attached to job orders to indicate work location for distributed roles. ELMO's multi-location setup (AU/NZ/SG) is preserved so that Crelate job orders carry the correct regional office reference. Remote or hybrid designations from ELMO's location type field migrate as a Crelate work-style attribute on the job order.

ELMO legal entity records from GET /legal-entities define ABN/ACN-level employer entities for AU/NZ payroll compliance. These migrate to Crelate as company records that represent the employing entity for contractor and permanent placement roles. Legal entity codes and registration numbers migrate to custom fields on the Crelate company record. If the customer is a staffing firm using Crelate to track placements at client companies, legal entities from ELMO map to Crelate client records.

ELMO employment details from GET /employment-details cover start date, employment type, pay frequency, and superannuation details. These migrate as custom fields on the Crelate Candidate record rather than as a native object. Employment type (full-time/part-time/casual) maps to a Crelate candidate custom field; start date maps to the candidate start date field if Crelate supports it or a custom date field otherwise. Superannuation fund and contribution details from ELMO are preserved in custom fields but flagged as HRIS-domain data requiring a separate payroll platform.

ELMO groups from GET /groups define organisational units for access control and reporting. These migrate to Crelate team records or access groups depending on the customer's Crelate tier and team configuration. Group membership for each employee maps to Crelate team membership assignments. Groups used purely for HR reporting (not recruiting) are flagged for the customer as out-of-scope for Crelate and noted as requiring the parallel HRIS destination.

ELMO organisations commonly add custom configurable fields to employee records for industry-specific data. We export the full custom field schema from GET /configurable-fields-meta, then create matching custom fields in Crelate during schema design before any candidate records load. Field types are mapped: ELMO text becomes Crelate text, ELMO date becomes Crelate date, ELMO dropdown becomes Crelate picklist. Custom fields with no Crelate equivalent are added as Crelate custom fields with the original ELMO field label preserved in the field description.

ELMO leave requests from the BETA GET /leave-requests endpoint and leave balances are not relevant to Crelate's ATS data model. Leave management is an HR Core function that requires a dedicated HRIS on the destination side. We extract a snapshot of current leave balances from ELMO's UI export (required because the API endpoint is BETA) and deliver it as a structured CSV to the customer for import into the parallel HRIS. The migration log notes this as out-of-scope with the recommended HRIS destination noted.

ELMO payroll calendar definitions (pay periods, pay run dates, STP reporting cycles) are organisation-level payroll configurations. Crelate is an ATS and does not manage payroll. These records are flagged as out-of-scope during scoping, and the customer is advised to configure payroll in their chosen parallel HRIS (Xero, MYOB, QuickBooks, or similar). The migration log documents the ELMO payroll calendar configuration for the customer's HRIS implementation team.

ELMO Learning module records (courses, completion status, quiz scores, custom courses) are not supported in Crelate. If the customer used ELMO's recruitment module for hiring training candidates, we extract candidate skill tags and completion records as CSV for the customer to import manually into Crelate's skills matrix or a dedicated LMS. This is documented in the migration handoff with the recommendation to evaluate Crelate's skill tagging feature for this data.

ELMO Recruitment module job postings map to Crelate Job Orders. We extract job title, description, requirements, location, department assignment, employment type, and posting status. Active postings in ELMO are set to Active in Crelate; closed postings become Archived in Crelate with a close date preserved. Candidate pipeline stages from ELMO's recruitment module map to Crelate pipeline stages, which we configure during schema design before any records load.