Migrate from Infor HCM to Bullhorn ATS & CRM

Infor HCM Employee records map to Bullhorn Candidate. Core biographical fields (legal name, date of birth, address, contact details, employment status) migrate directly. Infor's effective-dated job-title and manager-assignment rows extract as a dated history; the latest active row drives the primary Candidate record, and prior rows load into a Bullhorn Custom Object (e.g., customObject1s) as a job history timeline to preserve the full record. Employee type (full-time, contractor, temporary) maps to Bullhorn employmentType with a custom source_hcm_employee_type__c field retained for audit.

Infor HCM employee records for the customer's own internal staff (not contractors being placed) map to Bullhorn ClientContact records representing the agency's internal employees using Bullhorn. This distinction is determined during scoping based on the customer's use case; the same Infor employee table may yield both Candidate and ClientContact records depending on whether the individual is a contractor being placed or an internal staffer.

Infor HCM org structures are hierarchical trees with cost center and location associations. Bullhorn does not have a native internal org chart object. We reconstruct the org tree by mapping each Infor org unit to a Bullhorn Category (for internal department classification) or a ClientCorporation record (if the org unit represents a client relationship). The parent-child hierarchy is preserved by storing the Infor parent_org_id as a custom field on each Category for post-migration admin reconstruction.

Infor HCM Positions define headcount slots with grade, department, and salary grade associations. When the customer uses Infor HCM to track open job reqs or req-linked positions, these map to Bullhorn JobOrder records representing open job orders to be filled. A single Infor Position can yield one JobOrder in Bullhorn. Position hierarchies (reporting lines encoded in position structures) are stored as custom fields on the JobOrder for admin to map to Bullhorn's reporting structure post-load.

Infor HCM compensation history (salary, bonus, equity entries with effective dates) extracts as a dated history table. We load the most recent compensation row as the primary pay rate on the Bullhorn Placement record (fields: payRate, billRate, OTMultiplier). Prior history rows load into a Bullhorn Custom Object (e.g., customObject2s) as a compensation timeline with effectiveDate, payType, and amount fields. Bullhorn's compensation timeline is flat per Placement rather than a full retroactive history table; the Custom Object preserves the audit trail within Bullhorn's limits.

Infor HCM benefit plan enrollments and coverage tiers map to Bullhorn Custom Objects attached to the Candidate record. We extract plan name, enrollment date, coverage level (employee, employee-plus-spouse, family), and carrier. Bullhorn has no native benefits object, so plan identifiers and enrollment details live in the Custom Object. Benefit plan identifiers in Infor are customer-specific and must be mapped to the customer's post-migration benefits administration system by the admin.

Infor Workforce Management time entries, absence balances, and accrual calculations map to Bullhorn Custom Objects on the Candidate or ClientContact record. We extract current PTO/sick balances and leave histories as typed records (leaveType, balanceHours, asOfDate). Infor accrual calculation rules (accrual rates, carryover limits, vesting schedules) are calculation logic that does not migrate; we document the current rule set for the customer's HR admin to configure in their chosen benefits or payroll system post-migration.

Infor Talent Management performance documents, goal alignments, and review ratings extract as flat records per completed review cycle. We map to Bullhorn Custom Objects (e.g., customObject3s) attached to the Candidate record with fields: reviewCycle, overallRating, competencyScores, goalStatus, and comments. Review template structures and competency framework definitions in Infor are configuration data that does not have a direct Bullhorn equivalent; we deliver a template inventory for the admin to rebuild in Bullhorn's goal-setting or a third-party performance tool.

Infor Talent Science skills, certifications, and credential data link to employee records as tagged attributes. These migrate as Bullhorn Candidate skills, certifications, and credentials using Bullhorn's standard Candidate fields (skillIDs, certification, education). Infor skill taxonomy codes map to Bullhorn skill name strings with a source_taxonomy__c field retained for reference. Where the Infor taxonomy is more granular than Bullhorn's flat skill list allows, we map to the closest Bullhorn skill or store the original taxonomy code as a custom text field.

Infor M3 and HCM user-defined fields (alphanumeric, numeric, date, text) defined in CMS470 sessions are extracted as name-value pairs per record. Bullhorn editions limit Custom Objects to 10 (Growth/Enterprise ATS) or 2 (standard ATS), each with a maximum of 55 fields. During scoping, we inventory every Infor user-defined field per object, rank them by business criticality, and allocate high-priority fields to Bullhorn customObject slots. Fields exceeding the allocation are flagged in a written supplement for Bullhorn admin to add via Bullhorn Support tickets post-load. Fields are type-mapped: Infor date UDFs become Bullhorn date fields, numeric UDFs become Bullhorn float or integer fields, text UDFs become Bullhorn string fields.

Infor Document Management (IDM) documents and SharePoint attachments (contracts, IDs, performance records) attached to employee records extract as binary files. We map them to Bullhorn's ContentDocument (Files) attached to the corresponding Candidate or ClientContact record via ContentDocumentLink. Bullhorn supports file upload via REST API, so documents attach to the correct parent record using the employee-to-candidate ID mapping. Document version history from IDM is excluded per Infor's standard export limitation; we flag this for compliance review.

Infor LN payroll journal entries and GL postings live in the financial module rather than HCM proper. We extract payroll register data (pay period, gross pay, deductions, net pay) via file export. Pay calculation rules, tax jurisdiction configurations, and GL account mappings are Infor LN configuration that does not migrate. We deliver a payroll register summary extract for the customer's new payroll administrator to set up in their chosen payroll system. Bullhorn does not include native payroll; the payroll system replacement is a separate evaluation.

Infor HCM contractor and contingent worker records (if stored in the same employee table) map to Bullhorn Candidate records with the employmentType set to Contract. If the contractor has an active placement assignment in Infor HCM, that assignment maps to a Bullhorn Placement record with status, start date, end date, and bill/pay rates. Contractor skill classifications from Infor migrate as Candidate skills using the same taxonomy mapping as permanent employee skills.