Migrate from ELMO Suite to Zoho Recruit

Active ELMO employee records that originated from the recruitment or onboarding module migrate to Zoho Recruit Candidate records. We extract candidate name, email, phone, current title, department, and location fields. ELMO records with status = applicant or candidate migrate directly; any ELMO record flagged as a current employee (status = active, employment_type = full-time/part-time) is reconciled with the customer to determine whether the candidate record, the employee record, or both should exist in Zoho Recruit.

ELMO recruitment module job postings, requisitions, and position records map to Zoho Recruit Job Opening. We extract job title, department, location, employment type, job description, and posting date. Position status (open, filled, closed) maps to Zoho Recruit's Opening Status picklist. Job Board distribution settings from ELMO are noted for manual reconfiguration in Zoho Recruit.

ELMO interview schedules, interviewer assignments, interview types, and scores migrate to Zoho Recruit Interview records. We map interviewer name, interview date and time, interview stage, and evaluation score. Score formats from ELMO (numerical, descriptive) are reconciled against Zoho Recruit's rating model or stored as structured notes if no direct type match exists.

ELMO notes attached to candidate or requisition records migrate to Zoho Recruit Task records linked to the corresponding Candidate and Job Opening. Task status, priority, due date, and assignee transfer directly. Recruiter-assigned tasks map by email match to Zoho Recruit User records, with unresolved owners placed in a reconciliation queue.

ELMO offer letter records attached to a candidate are migrated as Zoho Recruit Candidate-level Notes or as structured fields in the Candidate record if the offer details (salary, start date, conditions) are stored in typed fields. We flag offer status (pending, accepted, declined) and map it to Zoho Recruit's candidate pipeline stage.

ELMO onboarding task lists and document checklists migrate as a structured set of Zoho Recruit Tasks under the Candidate record. Tasks are sequenced by step order and assigned to the hiring manager or HR contact by email lookup. Standalone onboarding tasks that do not link to a named Zoho Recruit object are exported as a CSV handoff file for the customer's admin to rebuild as Task lists post-migration.

ELMO user accounts referenced on candidate records, interview assignments, and tasks migrate as Zoho Recruit User records. We resolve each ELMO user by email match against the Zoho Recruit destination User table. The Zoho Recruit free tier supports a limited number of recruiters per plan; we confirm the plan tier before provisioning all users to avoid a licence compliance issue at migration time.

ELMO departments, business units, and cost centres are created as Department records in Zoho Recruit for use as lookup fields on Job Opening and Candidate records. The full org chart and reporting hierarchy are noted for manual configuration in Zoho Recruit Settings since Zoho Recruit's org structure is a reference dataset rather than a full hierarchy engine.

ELMO employment history records attached to an employee (job title changes, department transfers, status transitions) are exported as structured candidate work history entries. Zoho Recruit Candidate records support a Work Experience section where previous employers, job titles, and dates are stored as repeating field groups. We chunk long employment histories and map each entry to the corresponding work history row.

ELMO pay groups, pay rates, salary history, superannuation contributions, and TFN declarations have no Zoho Recruit schema equivalent. Zoho Recruit stores salary as a candidate attribute field for offer-stage reference only, not as a payroll record. We export compensation data as a structured CSV with the full pay history timeline and deliver it to the customer as a financial records handover. The customer configures a Zoho Recruit custom field for salary expectation if offer-stage visibility is required.

ELMO leave entitlements, accrual rules, and balance snapshots are HRMS-specific records that Zoho Recruit does not support. Leave management is outside Zoho Recruit's ATS scope. We export leave balances as of the migration date as a CSV deliverable and note that leave management requires a dedicated HRMS or payroll system post-migration.

ELMO review cycles, objectives, competency ratings, and custom review forms have no Zoho Recruit schema equivalent. Zoho Recruit does not include a performance management module. We export completed review records as structured data including ratings, objectives, and review dates, and flag custom review templates for manual reconciliation. Performance review rebuilds require a separate performance management platform.

ELMO course completions, certifications, skill profiles, and learning paths are outside Zoho Recruit's ATS scope. We export learning completion records as a structured CSV with certification names, completion dates, and expiry dates for the customer's L&D team to migrate to a dedicated learning management system post-migration.

ELMO engagement survey responses, participation rates, and sentiment scores have no Zoho Recruit equivalent. Zoho Recruit does not include an engagement or survey module. We export survey results as structured records for the customer to migrate to an engagement platform or data warehouse.

ELMO roster templates, recurring shifts, and historical time-and-attendance entries are HRMS time-tracking records outside Zoho Recruit's scope. We export a snapshot of current roster assignments and time-entry summaries as CSV deliverables for the customer to migrate to a dedicated time-and-attendance or rostering platform.