Migrate from Omni HR to Zoho Recruit

Omni HR employee records map to Zoho Recruit Contact only if the employee represents a contact record (referral source, vendor contact, or former employee to keep on file). Active employee records that are not job applicants do not have a direct Zoho Recruit equivalent since Zoho Recruit is an ATS, not an HRIS. We flag employee records by employment status during scoping and route active employees to a reconciliation queue for the customer to decide whether to keep as Contact records, move to a separate HRIS destination, or treat as inactive and archive.

Omni HR recruitment candidates map directly to Zoho Recruit Candidate records. Candidate profile fields (name, email, phone, resume, source, pipeline stage) migrate 1:1. Omni HR custom candidate fields migrate to Zoho Recruit custom candidate fields, subject to Zoho Recruit's custom field limit of 50 per module on Standard or 300 on Enterprise. We validate the candidate field count against the destination plan tier before import and flag any fields requiring redesign or removal.

Omni HR candidate pipeline stages map to Zoho Recruit Job Opening records with corresponding candidate status assignments. Each Omni HR recruitment pipeline becomes a Zoho Recruit Job Opening with its own pipeline stages. Stage names and probabilities are configured in Zoho Recruit's pipeline settings before candidate import to ensure status mapping accuracy. Active job postings in Omni HR migrate as Job Opening records in Zoho Recruit.

Omni HR onboarding task checklists and e-signature completion states decompose into Zoho Recruit Interview records and Candidate custom fields. The onboarding task list does not map to a single Zoho Recruit object; we split task completion status into Zoho Recruit Interview records for structured hiring stages and Candidate custom fields (checkbox or multi-select) for document and checklist items. E-signature metadata does not transfer and is flagged for manual re-collection at the destination.

Omni HR performance review records map to Zoho Recruit Assessment records. Review cycle, rating scores, reviewer comments, and reviewer assignments transfer to Assessment fields. Zoho Recruit Assessment records are structured for pre-hire skills and psychometric assessments rather than employee performance reviews, so review type and scale fields require explicit mapping during scoping. The customer configures Assessment form templates in Zoho Recruit to match their review format before migration.

Employee documents (contracts, offer letters, IDs, certifications) stored in Omni HR migrate to Zoho Recruit's Document Library under the associated Candidate or Contact record. File content and filenames transfer directly. Document version history and e-signature status do not transfer. File attachment associations to specific employees require re-linkage in Zoho Recruit after migration since the storage reference is not preserved.

Omni HR workbook-scoped custom field definitions and their stored values export via a two-step API query (schema endpoint plus data endpoint). We create equivalent custom fields in Zoho Recruit per module, match data types (text, number, date, picklist), and import values. Field count validation against Zoho Recruit's tier limit (50 Standard, 300 Enterprise) is required before import; custom fields exceeding the limit are flagged for removal, consolidation, or Enterprise plan upgrade.

Omni HR organizational hierarchy derived from manager-employee relationships maps to Zoho Recruit Departments. Each distinct manager chain in Omni HR becomes a Zoho Recruit Department with the manager as the department head. The full flat hierarchy maps to a nested department tree. We extract manager relationships from Omni HR employee profiles and construct the department structure in Zoho Recruit before any candidate or contact import.

Omni HR time-off records (leave requests, accrual balances, approval status) have no equivalent in Zoho Recruit, which is an ATS without a time-off or HRIS module. Historical leave balances and request history cannot migrate to Zoho Recruit. We include time-off records in the migration scope inventory but flag them as requiring a separate HRIS destination or manual record if the customer needs to preserve them. Pending time-off requests are flagged for manual resolution before cutover.

Omni HR payroll runs with YTD accumulations, statutory deductions (CPF, MPF, EPF), gross/net amounts, and bank account details have no equivalent in Zoho Recruit and cannot migrate. Payroll data is outside Zoho Recruit's data model scope entirely. We include payroll records in the migration scope inventory, confirm the customer's destination for payroll data, and note that payroll migration to a dedicated HRIS or payroll platform is a separate engagement. Country-specific statutory field mapping is documented for any future payroll system migration.

Omni HR expense submissions with line items, approval status, cost center assignments, and reimbursement amounts have no equivalent in Zoho Recruit. Zoho Recruit is an ATS and does not have an expense module. Approved expense history is included in the migration scope inventory but flagged as requiring a separate financial system destination or manual export for record retention. Pending expenses are flagged for manual resolution before cutover.

Omni HR approval chains, notification triggers, conditional routing rules, and escalation paths are stored in Omni HR's workflow engine and are not accessible via the public API. We cannot import workflow configurations into Zoho Recruit because the automation models are structurally different. We document every active Omni HR workflow (trigger, conditions, actions, assigned approvers) in a written inventory and the customer rebuilds them in Zoho Recruit Blueprint or Workflow Rules post-migration. This is a manual step that adds post-migration implementation effort.