Migrate from Arcoro to Bullhorn ATS & CRM

Arcoro Employee records map to Bullhorn Candidate. The Employee firstName, lastName, and email map to Candidate name and email fields. Custom CoreHR fields on Employee migrate to Bullhorn custom fields on Candidate via the Bullhorn REST API custom field endpoint. Employment status (active, terminated, on leave) maps to Candidate employmentType and a custom status field. We resolve duplicate candidates by email during import and flag records requiring manual review.

Arcoro ATS Applicant records map directly to Bullhorn Candidate. The applicant sourcing channel, stage history, scorecards, and notes migrate as Candidate custom fields and note attachments. Resume files attached to Arcoro Applicants upload to Bullhorn as ContentDocument records linked via ContentDocumentLink to the Candidate. Arcoro stage names map to Bullhorn Candidate status values via a configuration table built during scoping.

Arcoro onboarding workflow tasks and document checklists migrate as Bullhorn Candidate custom fields tracking completion status and as attached documents in Bullhorn's document management structure. Workflow state (active, completed, pending) does not transfer as live workflow triggers; we document each onboarding workflow's task sequence for the customer's Bullhorn admin to rebuild using Bullhorn's workflow engine or Bullhorn Onboarding (formerly Able) if licensed.

Arcoro time entries with hours, job cost codes, overtime calculations, and pay period data map to Bullhorn custom fields on Candidate or to Bullhorn Time & Expense if the customer licenses that module. Job cost code structures from Arcoro (which cannot simultaneously break into job, phase, cost code, and cost class) require flattening before migration. We build a crosswalk table during scoping that maps Arcoro cost codes to the destination's coding scheme and flag unmapped codes for admin resolution.

Historical payroll records including earnings, deductions, and tax withholdings per pay period migrate as read-only custom fields on Bullhorn Candidate or as Placement billing records if the Bullhorn Back Office module is licensed. We export payroll history as archival data preserving compensation context; Bullhorn does not process payroll directly but can store the record for reference. Compensation data lands last in the migration sequence to preserve audit trails.

Benefit records showing active plans, coverage levels, and election dates map to Bullhorn Candidate custom fields. Plan names and coverage tiers from Arcoro migrate as text or picklist values. Plans without a direct Bullhorn equivalent are flagged in the migration report with a note for the customer's benefits administrator to reconcile post-migration. Active benefit status does not trigger ongoing enrollment sync.

Arcoro certification records including issue dates, expiration dates, and renewal alert settings map to Bullhorn Candidate credential records or custom date fields. We preserve expiration dates as Bullhorn date fields and create a renewal alert tracking workflow in the migration handoff document. Construction-specific certifications (OSHA 10-hour, apprenticeship cards, trade licenses) migrate with their original names and expiry context intact.

Arcoro job cost codes associated with time entries require mapping to Bullhorn's equivalent structure. Because Arcoro cannot simultaneously represent job, phase, cost code, and cost class, we flatten the hierarchy into delimited custom fields or a cross-reference table that maps to Bullhorn JobOrder custom fields or Candidate custom fields. We flag codes without a destination equivalent and deliver the crosswalk as a configuration artifact.

CoreHR custom fields on Employee and Applicant records migrate to Bullhorn Candidate custom fields. We discover custom field names, types, and values via Arcoro CoreHR export configuration and map them to Bullhorn's custom field API. Bullhorn imposes character limits and type constraints (100-character text limits on some fields) that may require truncation or reformatting; we flag these during the field-mapping phase.

Documents stored per Employee or Applicant in Arcoro (onboarding paperwork, signed agreements, performance reviews) export as file attachments and import to Bullhorn as ContentDocument and ContentVersion records linked via ContentDocumentLink to the corresponding Candidate. Resume files migrate as the primary Candidate resume in Bullhorn's resume parsing field.

Arcoro employment history records including previous positions, tenure dates, and termination records migrate to Bullhorn Candidate custom fields and Notes. Termination reason and rehire eligibility flags from Arcoro map to custom picklist fields on Candidate for reference by the customer's recruiting and compliance teams.

Arcoro stores company and contractor entity data related to construction projects or client companies. These map to Bullhorn ClientCorporation records, which represent the staffing firm's client companies. The Arcoro entity name becomes ClientCorporation name, and any associated address or contact data maps to ClientCorporation address fields. ClientCorporation is created before Candidate records so that any Candidate-to-Client relationship lookups are satisfied at import time.