Migrate from UKG Ready to Bullhorn ATS & CRM

UKG Ready Employee records map to Bullhorn Candidate when the employee's organization is a staffing firm managing its own temporary or permanent placement candidates. We map standard fields: FirstName, LastName, Address, Phone, Email, Date of Birth, HireDate (maps to Candidate DateAdded or a custom field), EmploymentType, and Department (from Cost Center). Active vs inactive employment status maps to Candidate Status (Active, Placed, Inactive). Former employees who remain in the candidate pool are flagged with a status change date.

UKG Ready Employees who represent Client Corporation representatives (hiring managers, procurement contacts) split to Bullhorn Contact records linked to Client Corporation. We identify the split using UKG Ready Cost Center labels or a flag field if present; otherwise the customer defines the split rule during scoping. The original UKG Ready Employee ID is preserved in a Bullhorn custom field for cross-reference.

UKG Ready organizational company records (client companies if UKG is used to track client relationships, or the company's own corporate entity records) map to Bullhorn Client Corporation. We map Company Name, Address, Phone, Website, and Industry classification using Bullhorn's Business Sector picklist. Dedupe key is Company Name or Website domain. If the source UKG Ready tenant holds both internal employees and external client companies in a single Employee table, we apply a filtering rule during scoping to separate them.

UKG Ready Position records (job title, department, reporting structure, employment type, salary range) map to Bullhorn Job Order when migrating from a staffing firm's internal position management. We map Title, Description, Department (from Cost Center), EmploymentType, SalaryRangeLow, and SalaryRangeHigh to Job Order standard and custom fields. UKG Ready's Position data is Enterprise-tier only; if the customer does not have UKG Ready Enterprise, we use Job Requisition records or a structured CSV of open positions.

UKG Ready Base Compensation records (current salary, pay type, effective date, pay group) do not have a native Bullhorn equivalent because Bullhorn is a recruiting platform not a payroll system. We map compensation data to a Bullhorn Custom Object (Placement Compensation) available on Growth and Enterprise tiers with 55 available fields. Fields include PayRate, PayType, EffectiveDate, and ReasonForChange. This object is attached to the Placement record via a lookup relationship. If Bullhorn ATS (2 custom objects) or ATS Growth (0 custom objects) is the destination tier, compensation data maps to custom fields on the Placement object directly.

UKG Ready supports up to 10 HR Custom Fields on the Employee object via the Put HR Custom Fields API. Bullhorn ATS Growth has no custom objects; Bullhorn ATS has 2 custom objects; Bullhorn Growth/Enterprise have 10 custom objects with 55 fields each. We map UKG HR Custom Fields to Bullhorn custom fields on Candidate, Contact, or Client Corporation depending on entity type. Field type mapping (text, date, picklist) is validated against Bullhorn's supported edit types during scoping. If the destination is ATS or ATS Growth, custom fields required for compliance (EEOC, work authorization, certification tracking) take priority over discretionary fields.

UKG Ready Cost Center fields define organizational structure (department, location, business unit). Bullhorn has a Division entity used for organizational reporting. We map the primary UKG Ready Cost Center to Bullhorn Division by creating Division records matching the Cost Center names, then set the Candidate.DivisionID lookup. Third-party integrations with UKG Ready (e.g., Jirav) specifically map to the third Cost Center field regardless of its label; we confirm during scoping which Cost Center field holds the primary organizational unit and validate the correct field is used for both export and Bullhorn import.

UKG Ready Employee Assignment records define how employees relate to Cost Centers, locations, and pay groups. When migrating a staffing firm's candidate-to-placement data, Assignments map to Bullhorn Placement records, which link Candidate to Job Order and Client Corporation with start date, end date, bill rate, and pay rate. We preserve assignment history and active assignments during migration. UKG Assignment start/end dates map to Placement.DateBegin and DateEnd.

UKG Ready Pay Period Profile definitions (weekly, bi-weekly, semi-monthly payroll cycles) do not map to Bullhorn standard objects. We store pay period cadence as custom fields on the Placement object (PayFrequency, NextPayDate) and in a Bullhorn Custom Object (Payroll Configuration) if the Growth/Enterprise tier is in use. The customer's Bullhorn admin configures payroll calendar integration separately if ongoing sync to a payroll system is required.

UKG Ready Accrual Balances (PTO, sick leave, vacation balances carried forward) have no Bullhorn equivalent because Bullhorn does not manage leave or time-off tracking. We do not migrate accrual data. We deliver a written record of current accrual balances by employee as a CSV for the customer's HR admin to maintain in UKG Ready (if retained) or transition to a separate HR system. This is a mandatory disclosure at migration scoping.

UKG Ready Pay Statements (earnings, deductions, net pay by pay period) do not migrate to Bullhorn. Bullhorn is a recruiting CRM, not a payroll platform, and has no pay statement object. We do not migrate pay statement data. If commission tracking is required (common for staffing firm recruiters), we map UKG Ready's compensation records to Bullhorn's Commission object on Placement. All other pay statement data is excluded from migration scope and the customer is informed during scoping.

UKG Ready Time Entries (hours worked, pay codes, exception flags, project codes) do not migrate to Bullhorn. Bullhorn's Shift Planning add-on covers scheduling only and does not receive timesheet data from external HCM systems. We do not migrate time entry records. UKG Ready's time data is tied to the payroll calculation engine; extracting it independently of pay rule configuration produces incomplete data. If the customer requires historical time data in Bullhorn (for staffing firm temp worker tracking), we scope a custom integration separately.