Migrate from Omni HR to Recruit CRM & ATS

Omni HR Employee records map to Recruit CRM Candidate records. We map first name, last name, email, phone, location, employment status, and department. The Candidate record in Recruit CRM will carry the original employee status as a tag or custom field so the migration history is auditable. Manager assignments from Omni HR do not map to a native Recruit CRM field (no org chart object), so we flag these for manual re-entry or documentation.

Omni HR Candidate records are the cleaner migration source for Recruit CRM since both platforms treat candidates as first-class entities. We map candidate name, contact details, application stage, pipeline status, and any custom recruitment fields. Stage names from Omni HR are reconciled against Recruit CRM's pipeline stage values during scoping, with non-matching stages created as new pipeline stages in Recruit CRM before migration begins.

Omni HR Company records (if used as part of recruitment or client tracking) map to Recruit CRM Client. The company name, address, and contact details migrate as Client fields. If Omni HR has no client-company records (typical for an internal HRIS), we skip this object and the customer starts Recruit CRM with an empty Client list to populate as they use the platform for new business.

Omni HR Onboarding task lists, document collection status, and checklist progress map to Candidate records in Recruit CRM with task-oriented custom fields or notes. E-signature metadata does not transfer. Completed onboarding tasks are recorded as Candidate status updates; the original onboarding checklist is preserved as a text summary attached to the Candidate record. Active pending onboarding tasks are flagged for manual follow-up at the destination.

Recruit CRM is a recruitment and applicant tracking platform, not a leave management system. Omni HR Time Off records — leave requests, accrual balances, and approval history — have no equivalent in Recruit CRM's object model. We do not migrate Time Off data. If the customer needs leave history preserved, we recommend exporting Omni HR Time Off records as a CSV archive and storing it outside Recruit CRM for compliance or audit purposes.

Omni HR payroll runs and statutory deduction records (CPF, MPF, EPF, and similar country-specific fields) have no native equivalent in Recruit CRM, which is not a payroll platform. Country-specific statutory fields require explicit mapping by the customer's HR team before any payroll-adjacent data is loaded. We export payroll history as a structured CSV with a country-awareness layer applied during export, and we flag which records require compliance review before import into any payroll-capable destination system.

Omni HR Performance Review records — review cycles, ratings, and feedback text — have no equivalent object in Recruit CRM. Review history migrates as a Candidate note or a separate archived document if the review was tied to a specific employee who is also a candidate in the system. Rating scales and review cycle configuration are not transferable.

Employee documents (contracts, IDs, offer letters) stored as file attachments in Omni HR export as file content with filenames. We re-attach these to the corresponding Candidate record in Recruit CRM. File-to-Candidate linkage is re-established during import by matching the employee name and document type against the candidate record. Any e-signature metadata associated with a document does not transfer.

Omni HR Expense records have no equivalent in Recruit CRM's recruitment-centric object model. We do not migrate expense submissions, approval status, or reimbursement data. This is a known limitation for any staffing agency that tracked candidate-related expenses (interview travel, relocation) in Omni HR; those records should be exported as a CSV archive separately.

Omni HR custom fields defined at the workbook level export with their field definition metadata (name, data type, allowed values) alongside the stored values. We map these to Recruit CRM candidate custom fields using the same field name and data type where supported. Custom fields that use a data type not available in Recruit CRM are converted to the nearest equivalent (e.g., date stored as text becomes a text field with a migration note). Custom field schema is validated in Recruit CRM's sandbox before the full import.

Omni HR's organizational hierarchy — derived from manager assignments on Employee records — has no native Recruit CRM equivalent. We extract the reporting structure from Omni HR employee profiles and produce a written org-chart summary (as a CSV or document) that the customer's Recruit CRM admin can use as reference. The hierarchy cannot be reconstructed as linked records in Recruit CRM without a custom object implementation, which is outside standard migration scope.