Migrate from Paycom to Bullhorn ATS & CRM

Paycom Employee records map to Bullhorn Candidate records. The four-character eecode is stored in a custom field paycom_eecode__c for reference. First name, last name, date of birth, SSN (as encrypted custom field), address, phone, and email map to Bullhorn's standard Candidate fields. Employment status (active, terminated, on leave) maps to a custom picklist field. The primary Employee address record maps to Candidate address fields; secondary addresses are stored as custom fields.

Bullhorn has a standard Employee entity separate from Candidate for internal staff of the recruiting firm itself. If the customer is migrating a staffing firm whose own employees are tracked in Paycom (not just their placed contractors), we map those Employee records to Bullhorn's Employee entity. Employee maps 1:1 with standard fields for name, department, title, and manager hierarchy.

Payroll run history from Paycom (pay period dates, gross pay, net pay, federal tax withheld, state tax withheld, and deduction amounts) is aggregated into a payroll summary custom object attached to the Placement record. Because Bullhorn has no payroll run entity, each historical pay period is stored as a separate custom field set on the Placement or as a custom object with a period-date key. We extract the last 12–24 months of runs based on customer scope. The most recent run's gross and net pay also populate the payRate and billRate standard fields on Placement.

Paycom's PTO accrual balance snapshot (current available balance, accrued this year, used this year, carryover cap) migrates as a static numeric custom field on the Placement record. We document the accrual rule (accrual-per-pay-period, front-load, accrual-per-hour, carryover cap) in a separate configuration notes document for the customer's Bullhorn admin. Bullhorn has no native accrual computation engine; if the customer wants accruals recomputed in Bullhorn, they must configure a new accrual policy and re-enact from hire date or set the Paycom balance as a starting point.

Paycom timecard records (clock-in, clock-out timestamps, total hours, overtime flags, absence punches) map to Bullhorn's Time and Expense module where the customer uses Bullhorn's back-office payroll features. Each timecard maps to a Time Entry record linked to the relevant Candidate and JobOrder or Placement. Paycom's labor allocation distributions (department, job, GL code splits) map to Bullhorn's cost center and division fields on Placement.

Paycom garnishment orders (child support, tax levy, creditor garnishment) are stored as typed custom fields on the Placement record. Each garnishment gets its own field set: garnishment_type__c (picklist), garnishment_amount__c (currency), garnishment_percentage__c (decimal), exemption_amount__c (currency), begin_date__c, end_date__c. We do not re-calculate the deduction; the maximum allowable percentage and order amount from Paycom are stored as static values. Bullhorn's admin must configure the garnishment deduction in their external payroll system post-migration.

Paycom benefits elections (medical, dental, vision, 401k, HSA) are stored as a custom object or set of custom fields on the Placement record: benefits_plan__c, coverage_tier__c (employee, employee+spouse, family), deduction_per_pay_period__c, and effective_date__c. Bullhorn has no native benefits enrollment module; the customer maintains benefits administration in a separate system or broker platform. We document active enrollments as a static snapshot only.

Paycom's Vault payroll card enrollment status (enrolled flag, card delivery status, card number last four) migrates to a custom field vault_enrolled__c on the Candidate record. Bullhorn does not have a native payroll card product; the customer must re-enroll employees in their chosen payroll card provider post-migration if applicable.

Paycom's client-specific custom fields on the new hire profile (text, select, and date types) are extracted via the get_new_hire_custom_fields endpoint and mapped to Bullhorn custom fields of equivalent type on the Candidate or Placement record. We create Bullhorn custom fields using the Admin > Field Mappings interface. Bullhorn caps custom fields per entity; if the customer has more custom fields than Bullhorn allows, we use Bullhorn custom objects as an overflow container.

Paycom Enhanced Background Check results (check status, completion date, pass/fail flags, check type) map to Bullhorn's standard background check fields on the Candidate record and to custom fields for any additional result data. Bullhorn's Talent Platform (onboarding module) can initiate new background checks post-migration; the Paycom historical record is preserved for audit and compliance purposes.

Paycom's labor allocation distributions (category codes, detail codes, GL codes, department splits) map to Bullhorn's cost_center__c, division__c, and GL_code__c custom fields on Placement. Paycom allows split allocations across multiple departments or jobs per pay period; we store the primary allocation as the standard field value and additional split allocations in a custom object with a sequence field.

If Paycom is used for any candidate or applicant tracking in addition to HCM, those records map to Bullhorn Candidate with standard field mapping. Paycom's candidate status and source fields map to Bullhorn's status and source picklist values. Resume documents migrate as Bullhorn attachments linked to the Candidate record.