Migrate from Omni HR to Crelate

Omni HR Candidates are stored in the same employee database as Employees, distinguished by an employment_status or record_type field. We split Candidates from Employee records during extraction and map them to Crelate Contact records with a candidate_role flag. Each Candidate's application pipeline stage (Applied, Screening, Interview, Offer, Hired, Rejected) maps to a corresponding Crelate Job Application status. Omni HR's custom candidate fields migrate as Crelate custom fields on the Contact record, with field type mapping (text to Text, numeric to Number, date to Date) confirmed during scoping.

Omni HR employee records map to Crelate Contact. The Omni HR employee record provides first name, last name, email, phone, department, title, manager (as a Contact lookup or name field), hire date, and employment status. Crelate does not have a native HR module, so employment-specific fields like salary, compensation band, benefits enrollment, or probation status do not migrate because no Crelate equivalent exists. Manager assignments migrate as a Crelate Contact lookup by resolving the manager's email address against the imported Contact list.

Omni HR onboarding task checklists and completion states map to Crelate Activity records (Tasks with task_status and description) attached to the relevant Contact. Each onboarding task (e-signature completed, document submitted, orientation attended) becomes a completed Crelate Task with ActivityDate set to the completion timestamp. E-signature completion metadata does not transfer; we document the completion state in the Task description. Onboarding document uploads (offer letter, contract, ID copies) migrate as Crelate file attachments to the Contact record, but the original employee-to-document association requires re-linking manually post-import.

Omni HR leave request history migrates as Crelate Contact Notes with the leave type, date range, duration, and approval status encoded in the note body. Crelate has no accrual balance or leave management module, so current accrued balances cannot be represented as live data. We preserve the complete leave history (leave type, start date, end date, duration, status, and any remarks) in a structured note format per employee. Active pending leave requests are flagged for manual re-entry at Crelate because pending status cannot be meaningfully represented in a note-based migration.

Omni HR payroll runs, YTD accumulations, statutory deductions (CPF, MPF, EPF), and bank account details have no Crelate equivalent. Crelate is an ATS and recruiting CRM with no payroll module. We exclude all payroll data from the migration scope and flag every payroll-related field (gross pay, net pay, deductions, employer contributions, pay frequency, bank account, tax ID) for exclusion during the data extract. This is a hard boundary of the migration; payroll data must remain in Omni HR or move to a dedicated payroll platform separately.

Omni HR can associate a Candidate with a company record (the prospective employer or a client's organization). These company associations map to Crelate Company records. Company name, website, industry, and size migrate 1:1. Company-to-Contact linking is preserved via Crelate's Contact-to-Company lookup, which we resolve during the Contact import phase by matching company name or domain.

Omni HR performance review cycles, reviewer assignments, ratings, and feedback text migrate as Crelate Contact Notes with a structured format (review period, reviewer name, rating, feedback summary). Crelate does not have a native performance management module, so review cycle configuration, rating scale definitions, and review template structure do not migrate. These must be reconfigured or omitted from the destination.

Omni HR employee and candidate documents (contracts, offer letters, IDs, certifications) migrate as Crelate file attachments linked to the corresponding Contact record. We extract document content and filenames from Omni HR and upload them to Crelate's document storage linked to the Contact. The original employee-to-document relationship (which document belongs to which employee) requires manual verification post-import because Omni HR stores document associations as internal references that do not export in the standard API response. We flag any documents where the association cannot be automatically resolved for manual re-linking.

Omni HR approval routing rules, conditional notification triggers, onboarding automation chains, and leave approval workflows are stored in Omni HR's internal workflow engine and are not accessible via the public API. We cannot export workflow configurations as data or code. We document every active workflow (trigger conditions, approval chain, escalation path, automation action) in a written workflow inventory delivered to the customer for manual re-implementation in Crelate's workflow builder.

Omni HR custom fields defined in workbooks require a two-step export: first, we query the workbook schema endpoint to retrieve field names, data types, and allowed values; second, we query the employee or candidate data endpoint for stored values. Both steps are subject to the 60 req/min API limit. The custom field schema maps to Crelate custom fields on the relevant core record type (Contact for employee/candidate fields, Company for organization fields). Field types are mapped: Omni HR text to Crelate Text, Omni HR number to Crelate Number, Omni HR date to Crelate Date.

Omni HR job requisitions or open positions created within Omni HR's recruitment module map to Crelate Job Orders. Job title, job description, department, location, employment type, and hiring manager migrate 1:1. Omni HR pipeline stage names are mapped to Crelate Job Order status values during the transformation step. Active vs. closed status translates directly.

Omni HR expense records (submission data, approval status, reimbursement amounts, cost center assignments) do not map to any Crelate object. Crelate is a recruiting platform and has no expense management capability. Expense records are flagged for exclusion during scoping and must remain in Omni HR or move to a dedicated expense management platform. We document the expense data fields and record counts so the customer can plan a parallel migration to an expense tool if needed.