Migrate from HROne to Bullhorn ATS & CRM

HROne Employee records require an explicit type decision during scoping. Employees who represent placed candidates or prospective talent map to Bullhorn Candidate. Employees who represent existing clients or hiring managers map to Bullhorn Contact attached to a ClientCorporation. Internal staff with no candidate or client relationship do not map into Bullhorn; we flag these for the customer to retain in HROne or another HRMS post-migration. We use email address as the dedupe key during Bullhorn import and preserve the original HROne employee ID in a custom field hrone_employee_id__c for audit and cross-reference.

HROne's org structure (departments, cost centers, reporting hierarchy) maps to Bullhorn ClientCorporation for external-facing organizational records. For internal department tracking within Bullhorn, we use Bullhorn's Custom Objects to preserve department assignments if the customer requires them for reporting across placements.

HROne salary structures, pay components, and compensation histories do not have a native Bullhorn standard object equivalent. We map these to a Bullhorn Custom Object (created per Bullhorn's custom object setup process) attached to the Candidate record. Fields include pay frequency, currency, base salary, and relevant allowances. Compensation on active Placements can be stored on the Placement record directly if the Bullhorn edition supports the required fields.

Clock-in/out logs, shift assignments, and overtime records in HROne store timestamps in the local timezone of the office or biometric device. We normalize all timestamps to UTC during transformation before mapping to Bullhorn. Bullhorn has no native attendance tracking module; attendance data maps to a Bullhorn Custom Object attached to the Candidate or Placement record, or is flagged for handoff to Bullhorn Time & Expense if that companion product is included in the customer's Bullhorn license.

Leave entitlements, accrual policies, and current balances from HROne do not map into Bullhorn's ATS schema. Bullhorn is not designed to manage leave tracking. We map leave balance data to a Bullhorn Custom Object if the customer needs it visible on the candidate or placement record, but we recommend a separate HRMS or Bullhorn Time & Expense for leave management post-migration. Carry-forward rules and leave type configurations are preserved in the mapping document for the customer's HR admin.

HROne stores employee documents as file attachments or DocumentTemplate records. We extract file binaries and their metadata (document type, language, upload date) from HROne and import them into Bullhorn as ContentDocument records linked via ContentDocumentLink to the corresponding Candidate or Contact. We preserve the original document name and add a custom field for document type classification.

HROne's recruitment module (available on Enterprise tier) stores job postings, candidate pipelines, and applicant data. Job title, department, location, and employment type from HROne map directly to Bullhorn JobOrder. Applicant status values from HROne map to Bullhorn JobSubmission status values with a mapping table provided during discovery. Interview scores and recruiter-specific custom fields may require Custom Objects in Bullhorn if the fields do not map to standard Candidate properties.

HROne applicants on a job opening map to Bullhorn Candidate records with a JobSubmission linking each Candidate to the corresponding JobOrder. We map the HROne applicant status (applied, screening, interview, offer, hired, rejected) to the equivalent Bullhorn status values using a translation table. If HROne stores interview scorecards, these map to Bullhorn Custom Objects on the Candidate or JobSubmission.

Goals, appraisal cycles, and review ratings from HROne's performance module do not have a standard Bullhorn equivalent. We map appraisal data to a Bullhorn Custom Object attached to the Candidate record, with fields for appraisal date, rating, reviewer, and comments. If the customer does not license Bullhorn custom objects, we store appraisal summaries as Note records linked to the Candidate.

The HROne org chart (departments, manager relationships, cost centers) maps to Bullhorn ClientCorporation records for external organizations and to Bullhorn Custom Objects or a structured field mapping for internal reporting. Manager relationships from HROne are preserved as Bullhorn User-to-Candidate or User-to-Contact relationships for placement supervisory tracking.

HROne organizations frequently add instance-specific custom fields to the Employee object. These are not consistently exposed via the HROne public API and may only appear in UI exports. We perform a manual custom-field discovery step: we compare the HROne API export against a UI-generated sample export and flag any discrepancy. Unmapped custom fields migrate to Bullhorn Custom Object fields, created per Bullhorn's schema-before-data approach. We validate field type compatibility (text, number, date, picklist) during mapping.

HROne user accounts (including system accounts, shared logins, and inactive accounts retained for historical access) do not all map to Bullhorn users. We audit the HROne user list separately from the employee list and flag accounts that should not be replicated in Bullhorn to avoid inflating billable-seat counts. Active HROne users with recruitment responsibilities map to Bullhorn User records by email match. Any HROne user without a matching Bullhorn User is held in a reconciliation queue for the customer's admin to provision before candidate data import resumes.