Migrate from Cavu HCM to Bullhorn ATS & CRM

Cavu HCM employee records map to Bullhorn Candidate. We extract name, address, contact details, department, job title, hire date, and compensation from the Employer on Demand portal export. For temp staffing firms, current employees who are placed with clients become active Candidate records; internal support staff become Candidates with a do-not-place flag or are excluded per the customer's scoping decision. The Cavu employee status (active, terminated, on leave) maps to a Bullhorn custom Candidate status field because Bullhorn's standard status is recruiting-stage-driven rather than employment-status-driven.

Cavu HCM stores current job assignment and prior employment within the employee record. We extract each distinct job title, employer name, start and end date, and description and load these as Bullhorn Candidate Employment history records. Bullhorn supports multiple employment entries per Candidate with job title, company name, dates, and description fields. We sequence entries chronologically with the most recent role first.

Cavu HCM's talent management module stores applicant data including application status, screening results, and onboarding task completion. We migrate the most recent application per candidate as a Bullhorn Candidate record, preserving the Cavu application pipeline stage in a custom Candidate field candidate_origin_pipeline__c for reconciliation. The candidate's resume document migrates as a Bullhorn CV/Resume attached to the Candidate record via ContentDocumentLink.

Cavu HCM company records map to Bullhorn Client Corporation. The Cavu company name, address, and industry code map to the corresponding Bullhorn Client Corporation fields. Client Corporation is created before any Candidate import so that the client-facing relationship (Candidate submitted to a Client Corporation's Job Order) is established during migration. We use the Cavu company name as the dedupe key during Bullhorn import.

If Cavu HCM stores internal job requisitions or published job openings, these map to Bullhorn Job Order. Each Job Order in Bullhorn links to a Client Corporation, a Contact at that client, and one or more Job Shifts (full-time, part-time, contract). The Cavu job title and description map to Job Order title and description; salary range maps to pay range. Open, filled, and closed status maps to the corresponding Bullhorn Job Order status values.

Cavu HCM scheduled shifts with employee assignment, start/end time, and client location map to Bullhorn Placement records for temp staffing firms. Each Cavu shift with a client assignment becomes a separate Placement with the Cavu employee as the Candidate, the Cavu company as the Client Corporation, and the shift start/end date as the Placement start/end date. Recurring schedule templates are extracted separately and reconstituted as recurring Placements or Shift Pattern records in Bullhorn.

Cavu HCM payroll earnings records do not have a native Bullhorn equivalent because Bullhorn is not a payroll engine. We convert Cavu earnings into Bullhorn Placement pay rate and bill rate fields. For temp staffing placements, the Cavu employee's base hourly or salary rate becomes the Bullhorn Placement payRate; the Cavu client's billing rate becomes the Bullhorn Placement billRate; and the markup (billRate minus payRate) is preserved for margin reporting. We deliver a separate payroll reconciliation CSV of all extracted earnings, deductions, and taxes for the customer's finance team to import into their payroll system of record.

Cavu HCM federal, state, and local tax withholding setups, including multi-state LDG jurisdiction assignments, are extracted as a separate tax configuration export. These do not load into Bullhorn because Bullhorn does not store tax withholding configurations. We deliver the tax configuration as a structured CSV with jurisdiction codes, withholding rates, and effective dates for the customer's payroll administrator to configure in their new payroll system (whether that is a Bullhorn-integrated payroll partner or a standalone payroll platform).

Cavu HCM garnishment orders, voluntary deductions, and benefit withholdings attach to the employee record. We extract these as structured data and load them into Bullhorn Placement custom fields (if the customer licenses Bullhorn Front Office or Growth and requests garnishment tracking on Placement) or deliver them as a structured CSV alongside the payroll reconciliation file. Bullhorn does not natively process payroll deductions; these are handled by the customer's payroll system.

Cavu HCM benefit elections (health, dental, vision, 401k) with effective dates are extracted per employee. Bullhorn does not have a native benefits enrollment object because it is a recruiting ATS, not an HRMS. We load active benefit enrollment status as Bullhorn Candidate custom fields (e.g., benefits_enrolled__c, benefits_plan_tier__c) or as a Candidate Note for administrative reference. We sequence enrollments chronologically and flag any mid-year enrollment changes as separate Candidate Note entries with effective dates.

Cavu HCM PTO accrual balances and usage history per employee are extracted as structured data. Bullhorn does not have a PTO accrual object. We convert current PTO balance, accrual rate, and usage history into Candidate custom fields (pto_balance_hours__c, pto_accrual_rate__c) or deliver them in the payroll reconciliation file for the customer's new payroll system to consume. Leave type distinctions (vacation, sick, personal) map to separate custom fields per leave type.

Cavu HCM employee documents (new hire forms, tax withholdings, I-9s, performance reviews) export from the Document Storage module as individual files with folder metadata. We load each document as a Bullhorn ContentDocument record and attach it via ContentDocumentLink to the corresponding Candidate or Client Corporation record. We preserve the original Cavu folder structure as Bullhorn ContentWorkspace records (libraries) so that I-9s, tax forms, and performance reviews remain organized. File content migrates as-is; we do not convert file formats.

Cavu HCM time and attendance records (clock-in/clock-out events) export per employee. For temp staffing placements, we convert Cavu time entries into Bullhorn Placement Timecard entries (start time, end time, break, total hours) linked to the corresponding Placement record. Entries that were edited or approved post-submission are flagged with a custom field timecard_edited__c for the customer's timekeeping administrator to review. For non-placement employees, time entries are delivered as a structured CSV for payroll reconciliation.

If Cavu HCM contains custom employee data structures (compliance tracking, certification management, certification expiration schedules), these map to Bullhorn Custom Objects. Bullhorn's API supports custom objects with up to 55 fields per object depending on tier: Front Office Growth and Enterprise allow 10 custom objects; Bullhorn ATS allows 2; ATS Growth allows none. We pre-create the destination Bullhorn custom object schema during the sandbox phase, including all custom fields, picklist values, and lookup relationships, before any data import. Custom object naming follows Bullhorn's __c API name convention.

Cavu HCM pay schedule configuration (weekly, bi-weekly, semi-monthly, monthly) and associated GL mapping export cleanly. Bullhorn does not have a pay schedule configuration object. We deliver pay schedule configuration as a structured reference file with frequency, GL account mappings, and effective dates for the customer's payroll administrator to configure in their new payroll system. Pay schedule frequency also informs the payroll reconciliation CSV column structure.

Cavu HCM's dedicated payroll guide model assigns a named payroll contact per client. We extract all Cavu owner and administrator records and match them by email against Bullhorn User accounts. Any Cavu owner without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Active/inactive status maps to the Bullhorn User isActive flag.