Migrate from eArcu to Bullhorn ATS & CRM

eArcu Candidate records carrying name, contact details, work history, and custom profile fields map to Bullhorn Candidate. We extract all standard fields and any custom properties, mapping them to Bullhorn custom fields on the Candidate entity. Assessment scores (cognitive, personality, situational judgement) attach as linked records and are mapped to Bullhorn custom fields or a custom object. Stage history timestamps migrate to Bullhorn note or activity records attached to the Candidate.

eArcu Requisition fields (title, department, location, employment type, pipeline assignment) map to Bullhorn JobOrder. We extract any custom approval workflow configurations on the Requisition and document them as a rebuild guide for Bullhorn. eArcu does not expose a native bulk-export endpoint; extraction relies on the customer's integration account or the platform's reporting export, which we confirm during discovery.

eArcu Application records link a Candidate to a Requisition with timestamps for each stage transition. These map directly to Bullhorn JobSubmission. We preserve the full stage history including stage-entry dates by creating note or activity records on the JobSubmission in Bullhorn, since Bullhorn's standard JobSubmission does not store a detailed stage transition log. The candidate-to-job linkage resolves via Bullhorn's CandidateReference and JobOrderReference fields.

eArcu's configurable pipeline stages per requisition map to Bullhorn JobOrder pipeline definitions and status values. We extract the full stage list per requisition type during scoping and create corresponding Bullhorn pipeline configurations. Stage-entry dates from eArcu migrate as note records attached to JobSubmission so that the historical progression is preserved in Bullhorn.

Cognitive test results, personality questionnaire scores, and situational judgement data stored as linked records in eArcu are exported as raw scores with assessment type metadata. We map these to Bullhorn custom fields on the Candidate record, or to a Bullhorn Custom Object (if the customer's Bullhorn edition supports it and the volume of assessment data warrants a separate object). Bullhorn ATS Growth is limited to 2 Custom Objects; Front Office Growth and Enterprise support up to 10.

eArcu User accounts, roles, and permissions define who can view or act on requisitions and candidates. We export the user roster with role assignments and map to Bullhorn's User and permission model. Owner resolution happens by matching eArcu user email to Bullhorn user email. Any eArcu user without a Bullhorn counterpart is held in a reconciliation queue for the customer's admin to provision before record import resumes.

eArcu Offer records include compensation details, start dates, and approval status. Bullhorn does not have a separate Offer object in the standard ATS schema; offer data is typically stored on the Placement record or in custom fields. We map eArcu offer fields to Bullhorn Placement fields and any applicable custom fields. If the customer's Bullhorn edition supports Custom Objects, we may use a dedicated Offer custom object.

CVs, cover letters, and supporting files attached to Candidates or Applications in eArcu are extracted as binary files and re-uploaded to Bullhorn's native document store attached to the corresponding Candidate record. We preserve original filenames and attach them to the correct Candidate using Bullhorn's resume and attachment upload API. Document ordering and any folder structure in eArcu is documented for manual reorganisation in Bullhorn.

Career portal pages, job board widgets, and branding assets in eArcu are HTML and CSS configurations rather than structured database records. These cannot be meaningfully exported as records and do not transfer to Bullhorn's Career Portal configuration. We export any available content export package from eArcu and deliver it alongside a rebuild guide for Bullhorn Career Portal setup.

Animated onboarding content and structured onboarding task sequences in eArcu are platform-native configurations that do not export as discrete data records. We document the existing onboarding package structure during extraction as a reference for the customer's Bullhorn admin to rebuild using Bullhorn Onboarding (formerly Able). Onboarding data cannot be programmatically transferred.

eArcu configurable hiring pipelines and stage definitions per requisition type are workflow configurations, not data records. We document the pipeline and stage structure for each requisition type during extraction and deliver a configuration guide for Bullhorn. Workflow rebuild is outside migration scope; the customer's Bullhorn admin or an implementation partner handles it post-migration.

eArcu's configurable custom fields on Candidate, Requisition, and Application records require mapping to Bullhorn's custom field model. Bullhorn supports custom fields on all standard entities (Candidate, JobOrder, JobSubmission, etc.) via the Admin Field Mappings interface. If custom field counts exceed Bullhorn's standard custom field limits per entity, we recommend a Bullhorn Custom Object, subject to the edition limit (2 on ATS Growth, 10 on Front Office Growth and Enterprise).