Migrate from ELMO Suite to Crelate

ELMO employee records do not map to a native Crelate object because Crelate is an ATS without an HRIS schema. We extract active employee profiles (name, email, phone, department, job title, start date, employment type, manager) and import them as Crelate Contacts with a custom field elmo_employee_id__c and a tag 'ELMO Employee' to distinguish them from candidate Contacts. Historical employees who are not active applicants are exported as an inactive-Contact snapshot or held in a JSON export for HRMS storage rather than inflating the Crelate active database.

ELMO candidate profiles, applications, interview scores, and offer letters map to Crelate Contact records. The ELMO application record's stage (applied, screened, interviewed, offered, hired, rejected) maps to Crelate's candidate pipeline stage, which the customer configures during scoping. Offer letter details and compensation expectations stored in ELMO custom fields migrate to Crelate custom fields on the Contact. Candidate status in ELMO (active, withdrawn, hired) becomes Crelate's Status field with a custom mapping table.

ELMO job postings and position records map to Crelate Job. The ELMO job title, department, location, employment type (full-time, part-time, contract), and job description map to Crelate Job Name, Description, Location, and a custom employment_type__c field. Job status (open, on hold, filled, cancelled) maps to Crelate's Job Status field. We resolve the hiring manager reference from ELMO to a Crelate User by email lookup before insert.

ELMO placements and confirmed hires can map to Crelate Opportunity records when the recruiting workflow includes a fee-bearing placement. The Job becomes the WhatId on Opportunity, the placed Contact becomes the WhoId, and the placement fee or markup maps to Opportunity Amount. Split commission among team recruiters maps to Opportunity Partner or a custom commission__c field. Not all ELMO-to-Crelate migrations include placements; we confirm this during scoping.

ELMO client companies attached to a recruitment requisition or placement map to Crelate Company. The company name, website, industry, and address fields map directly. In the agency context, Crelate Company represents the hiring client; in the in-house context, it represents the employer organisation. We use the ELMO organisation name as the dedupe key during import to prevent duplicate Company records.

ELMO onboarding tasks, document checklists, and assignee ownership map to Crelate Task records linked to the candidate Contact. Each ELMO onboarding item becomes a Task with a Body (the task description), a due date from the ELMO checklist, and an assigned User resolved by email from the ELMO assignee. Standalone document checklists that have no Crelate equivalent are exported as a structured JSON attachment on the Contact record.

ELMO employment history (job title changes, department transfers, status transitions) does not map to a native Crelate object. We export the employment timeline as a structured JSON array and attach it to the Contact record as a custom field employment_history__c (long text area), or store it in a Crelate custom object if the customer has provisioned one. The original ELMO employment start date and current status also populate the Contact's hire_date__c and employment_status__c custom fields.

ELMO pay groups, pay rates, salary history, and ANZ-specific fields (TFN declarations, superannuation fund details) have no Crelate equivalent. We export these records as a structured JSON snapshot and deliver them alongside the migration, tagged by ELMO employee ID. The customer's finance or HR admin stores the payroll export in an alternative system or maps the relevant fields (expected salary, notice period, fee expectation) to Crelate custom fields on the Contact if required for recruiting context.

ELMO leave entitlements, accrual rules, and balance snapshots are HRMS-specific data with no Crelate object. We export the leave balance as of the migration date as a structured JSON file tagged by employee ID. The HR admin stores this in an alternative HR system post-migration. Leave data does not belong in an ATS and is flagged as out-of-scope before migration begins to prevent scope inflation.

ELMO review cycles, objectives, goals, appraisal ratings, and competency frameworks have no Crelate object. Rating scales vary significantly by organisation and the destination ATS cannot store them natively. We export review responses as structured records with the reviewer name, reviewee, rating scale value, and free-text response preserved in a JSON export. The HR admin receives the export and decides whether to store it in an alternative performance system or a document management tool.

ELMO course completions, certifications, skill profiles, and completion expiry dates are learning management data with no Crelate equivalent. We export these as structured records tagged by employee ID and course name, with completion status and expiry preserved. Certifications relevant to recruiting (mandatory compliance certifications, clearance types) may optionally map to Crelate custom fields on the Contact if the customer designates them as recruiter-relevant.

ELMO engagement survey responses, participation rates, and sentiment scores are HRMS analytics data. Crelate has no survey object. We export survey results as a structured JSON file tagged by employee ID and survey date. The HR admin stores this in an alternative analytics or engagement platform. Survey data is out-of-scope for the ATS migration and flagged as a separate data extraction deliverable.

ELMO departments, cost centres, business units, and the reporting hierarchy map to a Crelate custom object (Department__c) if the customer has configured one, or are exported as a structured JSON file. Manager assignments from the ELMO org chart populate the Contact's reports_to__c custom field (a lookup to another Contact record) or the Employee custom object. We resolve manager email to a Crelate User or Contact during import.

ELMO roster templates, recurring shifts, and historical time-and-attendance entries are time-and-attendance data with no Crelate equivalent. Crelate is an ATS without a time-tracking module. We export the final roster snapshot and time entries as a structured JSON file for the payroll or finance team to handle separately. Roster data is out-of-scope and explicitly excluded from the Crelate migration scope during scoping.

ELMO expense claims, receipts, approval workflows, and reimbursement status are HRMS finance data. Crelate has no expense module. We export expense records as structured JSON tagged by employee ID. The finance admin stores this in the payroll or expense system. Expense data is out-of-scope for the ATS migration and handled as a separate data extraction.

ELMO custom fields built within the recruitment module map to Crelate custom fields on the appropriate object (Contact for candidate fields, Job for requisition fields, Company for client fields). Crelate supports custom field types including text, number, date, picklist, checkbox, and currency per object. We export the ELMO custom field schema during discovery, define the equivalent Crelate custom fields before migration, and map values field-by-field. Field type conversion (ELMO text area to Crelate long text, ELMO multi-select to Crelate picklist) is handled during the transform phase.