Migrate from ELMO Suite to Recruit CRM & ATS

ELMO candidate profiles — including name, email, phone, resume, skills, and application history — map to Recruit CRM Candidate records. ANZ-specific fields such as visa status, TFN (Tax File Number) declarations, and right-to-work documentation stored in ELMO custom fields migrate as Recruit CRM custom fields. We resolve duplicate candidates by email dedupe before import and flag any ambiguous duplicates in a reconciliation queue.

ELMO job or vacancy records map to Recruit CRM Job records. Fields including job title, department, location, employment type, and job description transfer directly. Position status (open, filled, cancelled) maps to Recruit CRM job status values. Internal versus external job flags are preserved as custom fields if Recruit CRM's standard status values do not cover the customer's distinction.

ELMO applications — linking a candidate to a job with stage, source, and submission date — map to Recruit CRM application records. Application stage values (applied, screening, interview, offer, hired, rejected) map to Recruit CRM pipeline stage values. Where ELMO stores interview scores and interviewer feedback as sub-records, these migrate as Recruit CRM interview notes linked to the application.

ELMO interview records (scheduled time, interviewer, interview type, feedback scores, outcome) split into Recruit CRM Interview records and linked Candidate notes. Feedback scores stored as structured rating fields in ELMO become Recruit CRM custom fields on the Interview record; free-text interviewer notes migrate as Candidate Activity notes for full candidate timeline visibility.

ELMO onboarding task lists, document checklists, and assignee ownership map to Recruit CRM onboarding or task records where the customer's Recruit CRM plan supports onboarding objects. Standalone task lists that do not map to a named Recruit CRM object migrate as structured candidate activity records. We confirm Recruit CRM plan feature support during scoping before committing to object-level mapping.

ELMO employee records for individuals recruited through the ATS module who are now active employees map to Recruit CRM Candidates with a placed/hired status flag. This preserves the hiring pipeline history without duplicating data in an HRMS that the customer may no longer maintain. Historical employment type and start date migrate as custom fields.

ELMO organisations or company records linked to job vacancies map to Recruit CRM Client records. Company name, address, industry, and contact details transfer directly. ELMO records that represent staffing agency clients rather than the agency's own org chart map to Client; records representing the agency's own legal entities map to a separate company profile as agreed during scoping.

ELMO engagement records — call logs, email threads, meeting notes, and general notes — attached to candidates or jobs migrate as Recruit CRM Activity records on the corresponding Candidate or Job. Engagement timestamps, disposition codes, and outcome notes preserve. Email body content migrates as note content with the sender and recipient preserved in the activity record.

ELMO organisations frequently use custom candidate rating templates, competency scorecards, and interview evaluation forms that do not have a direct Recruit CRM equivalent object. We export these as structured records with field-level mapping to Recruit CRM custom fields and flag any rating scale that cannot map to a Recruit CRM picklist or number field for manual post-migration reconciliation.

ELMO payroll records, leave balances, superannuation contributions, performance review cycles, goals, and learning completion records have no native equivalent in Recruit CRM's ATS schema. We export these as structured CSV/JSON records at migration cutover and hand them to the customer for archiving or importing into a separate HRMS. We do not attempt to force HRMS data into a recruitment CRM's data model.