Migrate from eBoss to Bullhorn ATS & CRM

eBoss Employee records map to Bullhorn Candidate as the primary recruitment person record. First name, last name, email, phone, address, employment status, start date, and job title migrate to Bullhorn Candidate standard fields. Employment history from eBoss (prior positions, employer names, dates) migrates to Bullhorn Candidate work history custom fields or a separate employment history Custom Object if the Front Office Growth or Enterprise edition is the destination. We use the eBoss /custom/process SQL endpoint to extract fields not exposed in the standard API when needed.

eBoss Employees who are also client-facing recruiters or internal contacts merge into Bullhorn ClientContact records in addition to Candidate records. We use the eBoss employee type or department field to determine whether a record maps to Candidate only (job seeker), ClientContact only (client-side employee), or both (internal recruiter). The merged approach requires the dual import strategy: Candidate first, then ClientContact with the candidate-to-contact link resolved via Bullhorn's Candidate-to-Contact association fields.

eBoss Company records (employers, client organizations) map directly to Bullhorn ClientCorporation. Company name, address, industry, phone, website, and tax ID migrate to standard ClientCorporation fields. ClientCorporation is created before any Candidate import so that the clientCorporationID lookup is satisfied at the moment of Candidate-to-Client linking.

eBoss job requisitions or open positions map to Bullhorn JobOrder. Job title, description, requirements, salary range, employment type (full-time, contract, part-time), and status migrate to standard JobOrder fields. JobOrder status values (Open, Closed, Filled, On Hold) map from eBoss job status. The clientCorporationID on JobOrder references the mapped ClientCorporation.

eBoss job applications map to Bullhorn JobSubmission (also called JobApplication in some Bullhorn editions). The submission links a Candidate to a JobOrder, with status values (Applied, Screening, Interview, Offer, Rejected, Placed) mapped from eBoss application status. Submission date and source (referral, job board, direct) migrate as standard fields. We resolve the candidateID and jobOrderID references before JobSubmission insert.

eBoss placement or hire records (candidates placed in jobs) map to Bullhorn Placement. Start date, end date, pay rate, bill rate, client corporation, candidate, job order, and status (Active, Completed, Terminated) migrate to standard Placement fields. Commission tracking fields in Bullhorn Placement capture any eBoss compensation data tied to a successful hire. Placement requires resolved references to Candidate, ClientCorporation, JobOrder, and the billing User (recruiter who owns the placement).

eBoss employment history rows (prior employers, job titles, start/end dates) attached to an Employee map to Bullhorn Candidate work history if the Bullhorn edition supports it, or to a Custom Object (Front Office Growth/Enterprise only; 2 objects on Bullhorn ATS, none on ATS Growth). We confirm the target Bullhorn edition during scoping to determine whether we configure a Custom Object for employment history or use Bullhorn's native work history fields. Custom Object fields require Bullhorn Support to provision before migration.

eBoss custom fields on Employee, Company, and Job records that have no Bullhorn standard field equivalent map to Bullhorn custom fields (if within the entity's custom field allowance) or to Custom Objects (if complex or high-volume). Each eBoss custom field undergoes a type assessment: text fields map to Bullhorn text custom fields, dropdowns map to picklist custom fields, dates map to date fields, and multi-value fields map to multi-select picklists. Bullhorn's custom field limit per entity varies; we audit the target edition during scoping.

eBoss documents attached to Employee records (resumes, contracts, certifications) migrate to Bullhorn ContentDocument linked via ContentDocumentLink to the corresponding Candidate record. The eBoss file list endpoint (/files/list/candidate_id/{id}) and download endpoint (/files/filebycandidate) handle extraction. Documents receive a ContentDocumentLink with LinkedEntityId pointing to the migrated Candidate ID. File names and MIME types are preserved from the eBoss response.

eBoss PTO balance records (accrued, used, remaining by leave type) have no direct Bullhorn equivalent because Bullhorn is a recruitment ATS rather than an HRMS payroll system. We migrate PTO data as a Custom Object on the Candidate or as a Note attached to the Candidate record, depending on the Bullhorn edition. Bullhorn Support must provision any Custom Object used for PTO tracking before migration. This is a data preservation step, not a payroll engine transfer.

eBoss compensation data (salary, pay frequency, bonus structure, pay rate for contractors) migrates to Bullhorn Placement fields for placed candidates or to a Custom Object for pre-placement candidates. Bullhorn Placement has standard fields for pay rate and bill rate that capture the most common compensation elements. Extended compensation fields (allowances, equity, bonus schedules) require a Custom Object provisioned by Bullhorn Support. This is record data, not payroll configuration; tax setup and payroll integrations do not migrate.

eBoss hierarchical reporting relationships (manager-employee links) map to Bullhorn Candidate fields or to Bullhorn User reporting structure. For internal recruiters managed in Bullhorn, we map to the User object's manager lookup. For candidate reporting lines relevant to staffing (such as client company manager for a placed contractor), we use a Custom Object or a custom Candidate field. We resolve manager ID to Bullhorn User ID via email matching.