Migrate from OrangeHRM to Bullhorn ATS & CRM

OrangeHRM Employee records split into Bullhorn Candidate and Client Contact based on employment status. Active employees become Bullhorn Client Contact records attached to the agency's own organization as a Client Corporation. Former employees and job applicants from OrangeHRM Recruitment module become Bullhorn Candidate records. Employment dates, job titles, departments, and supervisor relationships migrate as custom fields on both record types for audit and reporting. We use OrangeHRM Advanced REST API v2 (available from version 6.5.11) for bulk export; Starter tier customers provide CSV exports which we parse, normalize, and chunk before Bullhorn API import.

OrangeHRM Recruitment module candidate records migrate directly to Bullhorn Candidate. Application status history, vacancy associations, and application dates transfer to Bullhorn Candidate custom fields and activity timeline entries. OrangeHRM application status values (Applied, Interview Scheduled, Offer Extended, Hired, Rejected) map to Bullhorn Candidate status values. Any OrangeHRM candidate without an email address is flagged for the customer's admin to resolve before import because Bullhorn requires an email for candidate deduplication.

OrangeHRM Job Vacancy records (title, description, hiring manager, status) map to Bullhorn JobOrder. We create JobOrder records in Bullhorn before importing any Candidate submissions so that the JobOrder ID reference is available for linking. OrangeHRM vacancy status (Opened, Closed, Cancelled) maps to Bullhorn JobOrder status. The hiring manager on the OrangeHRM vacancy resolves to a Bullhorn User by email match; unresolved managers go to a reconciliation queue.

OrangeHRM onboarding and offboarding task definitions and per-employee assignments reconstruct as Bullhorn Placement notes and custom fields. Bullhorn has no native onboarding task module; we attach a structured task inventory as a formatted note on the Placement record, listing each task type, assigned owner, due date, and completion status. For Advanced tier customers, we extract task data via ESB; Starter tier customers use CSV export. The customer's Bullhorn admin rebuilds any automated task triggers in Bullhorn's workflow builder post-migration.

OrangeHRM leave balances and historical leave request records do not have a native Bullhorn equivalent. We export leave entitlements per employee per leave type, normalize leave type names against Bullhorn's custom field schema, and attach the balance snapshot as a custom field block or formatted note on the relevant Bullhorn Candidate or Client Contact. Leave request status history (Approved, Rejected, Pending) migrates as a note on the record. Bullhorn does not handle leave management natively; this data serves as a reference record rather than a functional one.

OrangeHRM attendance punch-in and punch-out records, and attendance summaries per employee per period, migrate as supplemental data on the Bullhorn Candidate or Client Contact record. We extract the attendance snapshot as a formatted note capturing date, hours worked, and attendance status. Bullhorn does not have a native attendance module; if the customer needs time tracking in Bullhorn, they configure Bullhorn Middle Office or a third-party time-tracking integration post-migration.

OrangeHRM Performance module review cycles, reviewer assignments, ratings, and goal data map to Bullhorn Placement as custom fields and a structured note. We extract the review summary per employee including cycle name, reviewer, rating, and comments. Bullhorn does not have a native performance appraisal module; goal and competency data that OrangeHRM stores in the Performance module requires custom field creation in Bullhorn or documentation for the customer's admin to handle in a separate HRMS.

OrangeHRM supervisor-employee relationships define the org chart; these map to Bullhorn Corporate records (for client organizations) and internal User-to-User relationships (for the agency's own staff hierarchy). We extract direct-report mappings from OrangeHRM's PIM supervisor field and reconstruct the hierarchy in Bullhorn's internal corporate structure. Sub-department and cost center assignments migrate as custom fields on the Client Contact record.

OrangeHRM version 7.13 structured work schedules (schedule assignments per employee per work week) map to Bullhorn Placement custom fields capturing the schedule type and shift pattern. Bullhorn does not store employee availability or work schedule definitions natively; we attach the schedule data as a reference note on the Placement or Candidate record. Shift pattern definitions require mapping to Bullhorn's scheduling model or documentation for the customer's admin to configure.

OrangeHRM custom fields at the employee level migrate to Bullhorn custom fields on Candidate or Client Contact. Bullhorn supports free-text, drop-down, mini-picker, checkbox, and date field types. We match OrangeHRM field data types to Bullhorn field edit types during mapping. Custom Objects (available on Bullhorn Front Office Growth/Enterprise: up to 10 custom objects with 55 fields each; ATS: 2; ATS Growth: none) are pre-created in the destination before migration for any OrangeHRM custom fields that require a multi-field structured record.

OrangeHRM employee document uploads (contracts, ID scans, certifications) store file metadata (filename, upload date, file type, classification). We export document metadata as a structured record set and provide a file copy package. Document content transfers as a separate file handoff outside the Bullhorn API migration scope; the customer's admin uploads files to the Bullhorn record post-migration. The metadata record links each file to its OrangeHRM employee ID and Bullhorn Candidate or Client Contact ID.

OrangeHRM user accounts and admin role assignments are system configuration, not HR data, and are not migrated. We deliver a written inventory of OrangeHRM user roles, role permissions, and admin assignments for the customer's Bullhorn admin to provision equivalent User roles and access levels in Bullhorn post-migration. OrangeHRM employee records that correspond to active Bullhorn Users are matched by email and linked to the provisioned User record.