Migrate from HROffice to Bullhorn ATS & CRM

HROffice Candidate records map directly to Bullhorn Candidate. Standard fields (name, contact details, application status, skills, notes) migrate as-is. The HROffice candidate record may carry supplemental assignment history (prior placements, assignment types, time-in-service) that we attach as custom fields on the Bullhorn Candidate to preserve placement context without creating duplicate records. If HROffice candidates have multiple active assignments, each assignment becomes a separate Bullhorn Placement record linked to the same Candidate.

HROffice Applications tied to job postings map to Bullhorn Application records. Application date, status pipeline, and recruiter notes preserve. The HROffice application-to-candidate relationship maps cleanly to Bullhorn's Candidate-to-Application relationship. We use the HROffice candidate ID as a custom field (hroffice_candidate_id__c) on the Bullhorn Candidate for reconciliation after cutover.

HROffice Job Postings map to Bullhorn Job Order records. Job title, description, location, department, employment type, and pay range migrate directly. Employer branding content (logos, career site layout, custom CSS) does not migrate—these are CMS assets in HROffice with no Bullhorn equivalent. We export the job description text and metadata and flag branded content requiring rebuild in Bullhorn's career portal configuration. Published date and expiration date map to Bullhorn date fields.

HROffice Assignments (temporary placements, temp-to-perm arrangements, direct placements) represent the core staffing-agency data object. We create Bullhorn Placement records for each active or recently completed HROffice assignment, linking the Placement to the Candidate and the Job Order. Assignment type (temporary, temp-to-perm, direct hire) maps to Bullhorn Placement record type. Start date, end date, and assignment status migrate as Placement fields. The original HROffice assignment record is preserved as a custom object or related list entry on the Bullhorn Candidate for audit purposes. This prevents HROffice's assignment-based model from being forced into a continuous employment record, which would create duplicate or conflicting placement histories.

For candidates with historical assignment records where a full Placement is not warranted (short-term fill-in assignments, reference-only placements), we store assignment summary data as custom fields on the Bullhorn Candidate: last_assignment_type__c, last_assignment_start__c, last_assignment_end__c, last_pay_rate__c, total_assignments_completed__c. This preserves staffing history without overpopulating the Bullhorn Placement object with low-value historical records.

HROffice weekly timecard records (hours worked, submission dates, approval status) map to Bullhorn Time & Expense entries if the customer licenses Bullhorn Time & Expense or Bullhorn Middle Office. Timecards link to the Bullhorn Placement record representing the assignment. Hours worked, work dates, and pay rate migrate to the time entry. If the customer does not license Bullhorn Time & Expense, we export timecard history as a standalone custom object (hroffice_timecard__c) on the Placement for record retention purposes.

HROffice compensation records (pay type, hourly rate or salary, effective dates for each assignment) map to Bullhorn Placement pay rate and bill rate fields. HROffice's pay_type property (hourly, salary, temp-to-perm fixed) maps to Bullhorn's payRateType and billRateType fields. We validate rate formats during import because HROffice may store rates as decimal strings and Bullhorn expects numeric values. Overtime rates, shift premiums, and expense allowances from HROffice migrate as custom fields on the Placement record.

HROffice job postings may carry custom career site fields specific to the organization's branded job portal. We export these as Bullhorn custom fields on the Job Order entity (e.g., department_cost_center__c, hiring_manager_email__c, remote_policy__c). The employer branding fields (logo, banner image, CSS) do not map and are flagged for rebuild in Bullhorn's career portal. Department and location metadata from HROffice map to Bullhorn Job Order standard fields.

HROffice internal users (recruiters, administrators, hiring managers) map to Bullhorn User records. We extract HROffice users by email address as the dedupe key and match against the Bullhorn destination org's User table. User role and permission sets from HROffice do not have a direct Bullhorn equivalent; we flag the HROffice role assignments in the migration deliverable and the customer's Bullhorn admin provisions corresponding Bullhorn permission sets post-migration. Any HROffice user without a matching Bullhorn User goes to a reconciliation queue.

HROffice may track temporary workers or contractors as users for timecard submission purposes. These are not system users in the Bullhorn sense but rather candidates on assignment. We identify these HROffice user records during discovery and migrate them as Bullhorn Candidate records with the assignment history attached, rather than as Bullhorn User records. The customer's Bullhorn admin reviews and provisions system access as needed post-migration.

HROffice benefit enrollment records (plan type, enrollment date, coverage level, dependent information) migrate as custom fields on the Bullhorn Candidate or, for benefits tied to a specific assignment, on the Placement record. Bullhorn does not have a native benefits management module; benefit data is stored as structured custom fields. We preserve the benefit plan name, effective date, and coverage tier as separate custom fields and flag the benefit data for the customer's HR admin to validate post-migration.

HROffice recruiter notes attached to candidates, applications, or assignments migrate to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate, Job Order, or Placement. Rich text formatting from HROffice note bodies preserves in Bullhorn Note where the format is compatible (plain text and basic HTML; complex CSS-styled content is simplified). Note creation date and author (HROffice user) migrate with author preserved as a text string if the user does not have a Bullhorn User record.