Migrate from isolved to Bullhorn ATS & CRM

isolved Employee is the core HCM record with SSN, DOB, hire date, employment category, and compensation. We split at migration time: active candidates for open requisitions map to Bullhorn Candidate; current and historical employee records that represent placed workers map to Bullhorn Candidate with a Placement record; records with no recruiting context (pure payroll-only employees) do not have a native Bullhorn equivalent and are flagged for the customer's admin to determine whether to enter manually or store in a custom object. The Candidate custom1-candidate custom50 fields carry the migrated employee identifier for cross-reference.

isolved Employee records with company affiliation map to Bullhorn Contact under the corresponding Company (Client Corporation) record. The mapping uses the employee's work email as the dedupe key. Marital status, citizenship, and ethnicity fields that have no native Bullhorn Contact field are stored in Bullhorn Custom Objects attached to the Contact.

isolved's employer-level Company record (the customer's own organization) maps to Bullhorn Client Corporation only if the isolved instance tracks client companies as a separate entity. Most isolved HCM deployments use Employee as the primary record; in those cases we create a single Client Corporation representing the employer and link all Candidate records to it.

isolved Job Codes are employer-defined picklist values used for classification, compensation rules, and compliance. Bullhorn has no native Job Code field on Candidate or Job. We export the full isolved Job Code picklist table and create a Bullhorn Custom Object (max 55 fields per object) to hold Job Code definitions, then add a lookup Custom Field on Candidate and Job referencing that object. The customer's Bullhorn admin adds the picklist values through Bullhorn Support.

isolved Work Locations drive tax withholding, workers comp codes, and benefit eligibility across geographic or legal work sites. Bullhorn's Job record includes a City and State field but no Work Location concept. We create a Bullhorn Custom Object to store Work Location definitions (address, tax jurisdiction, workers comp code) and add a Custom Field on Candidate and Job referencing it. Multi-state compliance data from isolved is preserved as structured text in the Custom Object.

isolved Pay Groups control pay frequency (weekly, biweekly, semi-monthly, monthly) and overtime rules per group. Bullhorn has no native Pay Group entity. We create a Bullhorn Custom Object with fields for frequency, overtime rule, and effective date, linked to Placement records where applicable. Pay Group definitions that drive billing rates in staffing contexts map to the Placement's bill rate fields.

Historical payroll registers including earnings, deductions, taxes, and garnishment orders migrate to Bullhorn Custom Object records attached to the corresponding Candidate or Contact. We extract full payroll history from isolved as structured line items grouped by pay period, remap deduction codes using the isolved-to-Bullhorn deduction code matrix, and preserve amounts and pay-period dates. Garnishment orders are stored as structured records in a separate Custom Object with fields for order amount, deduction code, and jurisdiction.

Active benefit elections (medical, dental, vision, HSA, FSA, life insurance) migrate to Bullhorn Custom Object records attached to the Candidate or Contact. isolved's plan and rate structure maps to custom fields for plan type, carrier, coverage level, and contribution amounts. Bullhorn does not have a native benefits administration module; the Custom Object approach preserves the election history for reference and audit but does not replace a dedicated benefits administration platform.

Accrued and taken time off by type (PTO, sick, etc.) with carry-forward amounts migrates to Bullhorn Custom Object records. isolved calculates accruals per Work Location and Pay Group rules; we preserve the current balance, accrual rate, and accrual effective date. Bullhorn has no native time-off tracking; this Custom Object serves as a historical record only and cannot drive automated accrual recalculation.

Employee banking information for payroll disbursement migrates to Bullhorn Custom Object records under encryption. We extract account routing number and account number fields, mask them in transit using field-level encryption, and store the masked reference with the Candidate. Bullhorn has no native direct deposit management; the Custom Object preserves the banking reference for customers who continue processing payroll in isolved or a separate payroll platform.

Pending or in-flight change requests (salary change, direct deposit update, name/contact change, HSA election) are stateful records in isolved that do not auto-close on import. We migrate open Workflow Transactions as Bullhorn Note records attached to the Candidate or Contact, with the transaction type and request date preserved in the Note body. Closed transactions are logged as completed Notes for audit trail purposes.

Electronically stored employee file attachments (offer letters, I-9s, performance reviews) migrate as Bullhorn ContentDocument records linked via ContentDocumentLink to the corresponding Candidate or Contact. We export document blobs with metadata from isolved and import to Bullhorn using the File (ContentVersion) API. We cannot guarantee document rendering fidelity for non-standard file types; the customer reviews documents post-migration in Bullhorn's document viewer.