Migrate from ADP Workforce Now to Bullhorn ATS & CRM

ADP Worker records map to Bullhorn Candidate records as the primary migration object. We map WorkerID as Bullhorn candidateID for audit, legalName fields to name fields, preferred communication preferences to Bullhorn email/phone fields, and Worker status (active, terminated, on leave) to Bullhorn employment status. Address data migrates to Candidate address fields. Note that Bullhorn Candidates do not carry employment contract terms natively — pay rate, employment type, and start date from ADP require mapping to Bullhorn's custom fields or to the Candidate Work History object if the staffing agency tracks assignment history. Historical job assignments within ADP may require mapping to Bullhorn Placements if the agency tracks prior placements.

ADP supports 8 types of Worker Custom Fields (amount, code, date, indicator, number, percentage, string, telephone) at both the Worker and Worker Person levels. However, the ADP Workforce Now API does not expose a read endpoint for custom field values — they are write-only. We document which custom fields are in use during scoping, request a reference file of current values from the customer, and recreate them as Bullhorn Candidate custom fields before migration. Bullhorn's custom field creation requires admin access and is scoped to the Candidate record type.

ADP voluntary deduction instructions (health benefits, retirement contributions, voluntary benefits) map partially to Bullhorn. Bullhorn has no native deduction object — we map deduction types, amounts, and frequency to Candidate custom fields or to a billing setup record. Garnishment orders and involuntary withholding orders are explicitly excluded from the ADP Deduction Instruction API and will not transfer via API. We flag all active garnishment orders during scoping and provide a manual reconciliation checklist for the customer's HR admin to recreate in their chosen payroll system post-migration.

ADP benefit enrolments and coverage elections are accessible via ADP's Benefits API (Beneficiaries, Benefit Dependents, External Benefit Plans). Bullhorn has no standard benefits object. We map benefit plan names, coverage levels, and enrolment dates to Candidate custom fields. Plan configurations are employer-specific in ADP and do not map as structured Bullhorn data — we document the benefit plan inventory during scoping for the customer to recreate manually in Bullhorn or retain in a benefits administration system separate from Bullhorn.

ADP Time Off history, current balances, and leave event records are accessible via the ADP Time Off Requests API. Bullhorn has no native time-off or leave management object. We map current accrued balances to Candidate custom fields as a snapshot record, but Bullhorn's standard ATS and CRM does not track leave balances or run leave approval workflows. If the customer needs time-off management in Bullhorn, this requires a Bullhorn Marketplace add-on or a separate time-off system. Leave plan configurations and accrual rules do not migrate and must be rebuilt.

ADP payroll run history, pay stubs, and tax withholding records are accessible via the ADP Payroll API. Bullhorn has no payroll module. We map the most recent pay rate, pay frequency, and standard hours to Candidate custom fields for reference during recruiting and placement activity. Full payroll history (pay stubs, YTD earnings, tax withholding) does not migrate structurally — it is flagged for manual reconciliation or for import into the customer's chosen payroll system if Bullhorn is not the payroll system of record.

ADP Locations and Departments map to Bullhorn Corporate Departments and Branches respectively. Bullhorn's Corporate Department object stores department-level information for client corporations; the Branch object represents staffing office or location-level entities. ADP validation table values for Locations and Departments migrate as Bullhorn reference records. We resolve the ADP Location-to-Bullhorn Branch mapping during scoping, as staffing agencies often have multiple branch offices that need distinct Bullhorn Branch records.

ADP Job Titles from validation tables map to Bullhorn Job Order titles and Candidate skill descriptors. Bullhorn Job Orders store the position title, description, and requirements for open roles; Candidates store skills and work history including prior job titles. We map ADP job title values to Bullhorn Job Order titles and to Candidate skills where the staffing workflow references candidate qualifications against job requirements.

ADP Cost Numbers are used by project-based and construction companies to track labour distribution against projects or cost centres. Bullhorn has no native cost number or labour distribution object. If the customer relies on ADP cost numbers for billing or project tracking, we map them to Bullhorn custom fields on Candidate or Job Order. This mapping is scoped during discovery — Bullhorn does not support the multi-level cost breakdown model that ADP provides without custom field configuration.

ADP termination records (termination date, termination reason, rehire eligibility) map to Bullhorn Candidate employment history entries. Bullhorn's Placement record tracks assignments and their end dates; termination reason and rehire eligibility are stored as custom fields on the Candidate. We map ADP terminationReason and terminationDate to Bullhorn Candidate termination fields and set the rehireEligible flag accordingly.

ADP Workforce Now's Talent Management module — covering performance reviews, goal setting, compensation planning, and learning — is not accessible via the ADP Workforce Now public API. It uses a separate proprietary interface. Bullhorn has no native performance management or learning object. Neither platform supports this data via API for migration. We document the Talent Management module configuration and record types during scoping as a reference for the customer's HR admin to evaluate whether Bullhorn Marketplace add-ons or a separate performance management system is appropriate post-migration.

ADP exposes event notification webhooks for worker lifecycle events (hire, termination, pay rate change, location change). Bullhorn has its own webhook system for recruitment events. During migration, we configure ADP webhooks to capture any changes during the delta sync window. Bullhorn Automation Engine is the destination equivalent for triggering actions on candidate and job events. The migration does not transfer ADP webhook configurations — we document the ADP event types in use and recommend Bullhorn equivalents for the customer's admin to configure post-migration.