Migrate from Omni HR to Bullhorn ATS & CRM

Omni HR Employee records map to Bullhorn Candidate. Profile fields (name, email, phone, address, employment status, department, job title, start date, manager) migrate 1:1 into Bullhorn Candidate standard fields. Omni HR custom properties on employees map to Bullhorn custom fields on the Candidate entity. Bullhorn Support must provision customObject1 through customObject10 on Candidate before migration if any Omni HR custom fields exist. We coordinate this provisioning during the configuration phase. Historical employment data (prior companies, previous titles) migrates into Candidate work history custom fields or as separate CandidateWorkHistory records if the destination Bullhorn instance has that entity enabled.

Omni HR recruitment candidate records map directly to Bullhorn Candidate. Application stage names from Omni HR (Applied, Screening, Interview, Offer, Hired) map to Bullhorn Candidate status or a custom status field we configure during migration. Resume content migrates into the Candidate's attached resume or the resume field. Source attribution (where the candidate came from) migrates to the Candidate source field.

Omni HR Company records (if present as part of the Omni HR recruitment module) map to Bullhorn ClientCorporation. Company name, industry, website, address, and primary contact details migrate into Bullhorn ClientCorporation standard fields. The ClientCorporation record is created first so that subsequent Contact and Candidate-to-Client associations resolve correctly at import time.

Omni HR Onboarding records (task checklists, document collection status, e-signature completions) have no Bullhorn equivalent. Bullhorn does not store internal employee onboarding state as a native object. We export the Omni HR onboarding task list and completion status as a written checklist document that the customer's Bullhorn admin uses to manually configure Tasks or a custom onboarding tracking object post-migration. E-signature metadata does not transfer and requires re-execution in Bullhorn's document tools.

Omni HR leave requests and accrued balances have no Bullhorn equivalent. Bullhorn is a recruitment ATS, not an HRIS, and does not natively track employee time-off balances or approval workflows. We export leave history (request dates, leave type, approval status, accrual balances) as a CSV inventory for the customer's admin to re-enter in their separate HRIS or in Bullhorn custom fields if they configure a leave tracking object. Pending leave requests are flagged as open items requiring manual resolution before migration cutover.

Omni HR performance review cycles, ratings, and feedback text have no Bullhorn equivalent. Bullhorn does not store internal employee performance data as a standard object. We export performance records as a structured CSV inventory including reviewer assignments, rating values, review cycle dates, and feedback content. The customer's admin rebuilds these in a separate performance management tool or in Bullhorn custom fields if they provision a Performance custom object.

Employee documents (contracts, IDs, offer letters) stored in Omni HR migrate as Bullhorn ContentDocument records attached to the corresponding Candidate or ClientCorporation via ContentDocumentLink. We export document content, filenames, and MIME types. Document-to-employee associations migrate as ContentDocumentLink records. Bullhorn's document viewer and e-signature capabilities replace Omni HR's document handling post-migration.

Omni HR expense submissions and reimbursement records have no Bullhorn equivalent. Bullhorn is a recruitment ATS and does not handle employee expense management. We export expense records (submission dates, amounts, cost centers, approval status) as a CSV for the customer's admin to re-enter in their separate expense management tool. Approved and pending expense statuses are flagged during scoping.

Omni HR payroll history (pay periods, gross/net amounts, statutory deductions including CPF, MPF, EPF contributions) has no Bullhorn equivalent. Bullhorn does not process payroll. We export payroll year-to-date accumulations, deduction amounts, and bank account details as a structured CSV for the customer's admin to import into their separate payroll system. Country-specific statutory fields are preserved with their original values and field names for compliance reference.

Omni HR organizational hierarchy derived from manager assignments on employee profiles migrates into Bullhorn as Candidate reporting structure if the Bullhorn instance has a custom field or custom object for internal hierarchy. Bullhorn's primary use case is external recruitment rather than internal org structure, so the hierarchy is preserved as a reference mapping rather than a native Bullhorn object. We deliver the org chart as a written document and CSV for manual configuration.

Omni HR workbook-scoped custom fields require a two-step export: first the field definition metadata (field name, data type, allowed values) from Omni HR's workbook schema, then the stored values from the employee or candidate records. Bullhorn custom fields on Candidate, ClientCorporation, JobOrder, Placement, Opportunity, and Lead must be provisioned by Bullhorn Support before migration. We coordinate the provisioning ticket, define the target customObject schema during scoping, and map Omni HR's custom field values into Bullhorn custom fields during import. If Omni HR has more than 10 custom fields on any entity, we prioritize the most business-critical fields and flag the remainder for post-migration manual entry.

Omni HR approval routing rules, leave approval chains, onboarding automation triggers, and notification workflows are stored in Omni HR's workflow engine and are not accessible via the public API. We do not export or import workflow configurations. During scoping, we document the active workflow rules (approval chains, escalation paths, automation triggers) as a written inventory so the customer's Bullhorn admin can re-implement them in Bullhorn Automation (formerly Herefish) or configure them manually post-migration.