Migrate from Eploy to Bullhorn ATS & CRM

Eploy Job records (title, department, location, salary bands, workflow assignment) map 1:1 to Bullhorn Job Order records. Custom job fields from Eploy migrate to Bullhorn custom fields on Job Order. The job-to-workflow linkage in Eploy maps to the Job Order's status and custom status picklist values that we configure during Bullhorn schema design.

Eploy Candidate records (contact details, skills, notes, application history, status) map directly to Bullhorn Candidate. A Bullhorn Candidate does not require a Company record to exist first, but we create Client Corporation records during migration to enable the placement chain. Duplicates are resolved by email deduplication key during import.

Eploy workflow stages are organisation-specific with no canonical list in the API; we discover them by aggregating distinct stage values across active jobs during discovery. Each Eploy stage maps to a Bullhorn Job Order status or a custom status picklist value. Stage transition timestamps preserve as a separate audit object linked to the candidate's submission record.

Hiring manager assignments in Eploy (specific users tied to jobs and workflow stages) map to Bullhorn Job Order ownership and the primary Contact record on the Client Corporation. Role-based permissions that Eploy grants at the portal level may not translate directly to Bullhorn's permission set model; we flag these for Bullhorn admin review during scoping.

Eploy Offer records (salary, start date, role details, e-signature status) map to Bullhorn Placement records once the candidate is placed against a Job Order. If placement has not occurred at migration time, we create a Candidate custom field set capturing the offer details and flag the record for the Bullhorn team to convert to a Placement upon hire.

Eploy's onboarding module (reference collection, contracts, compliance documents) lives in a separate schema that may not fully expose all fields via the standard API. We query the onboarding endpoints explicitly during discovery, migrate what is accessible, and recommend a manual CSV export for records with partial schemas. Bullhorn Onboarding (part of Bullhorn One) is a separate licensed module; we document the onboarding data gap and map the record structure for re-entry post-migration.

Eploy referral records (linking an employee to a referred candidate with reward status) map to Bullhorn Candidate records with a referral source custom picklist field and a referring employee custom lookup field. Reward status migrates as a text field; the monetary reward value does not transfer unless a custom numeric field is created in Bullhorn.

Eploy Talent Pools (saved candidate collections for future roles) migrate as Bullhorn Candidate Tags or Segments. Pool membership preserves as a tag value on each Candidate record, enabling the Bullhorn team to recreate Talent Pool views through Bullhorn's built-in search and filter capabilities. We map pool names to tag values during scoping with customer confirmation.

Organisations add custom fields to Eploy Job records. We detect the custom property schema during discovery and create corresponding custom fields in Bullhorn on the Job Order entity via Bullhorn's custom fields API. Custom field type mapping (text, number, date, picklist) is confirmed with the customer before schema deployment.

Eploy custom candidate properties migrate to Bullhorn Candidate custom fields. Multi-select checkbox properties in Eploy map to Bullhorn multi-select picklists. Long-text notes migrate to Bullhorn Candidate custom text area fields. Custom field name collisions with Bullhorn standard fields are resolved by appending a suffix during scoping.

Assessment scores and results from Eploy attach to candidate records. We migrate structured assessment data as custom fields on the Candidate object. Visual or scored assessments that do not fit a typed field migrate as a Note record attached to the Candidate with the assessment content preserved in the body. The assessment provider reference migrates as a text field.

Eploy serves resume and document URLs rather than inline blobs. We enumerate all attachment URLs, download each file to temporary storage, then upload each to Bullhorn's attachment endpoint as a multipart/form-data binary blob. Large volumes of attachments (hundreds per candidate in compliance-heavy sectors) extend migration time. Filenames and the associated Candidate record link are preserved. This two-pass pattern is required because Bullhorn does not accept redirect URLs as attachment sources.

Eploy email and SMS threads tied to candidates migrate as Note records in Bullhorn linked to the Candidate. Formatting may flatten in transit. SMS content migrates as a separate Note record with an sms_thread__c custom flag for Bullhorn admin identification. Timestamps are preserved in the Note's created date for timeline ordering.

Each Eploy candidate-to-job submission creates a Candidate Job Submission record in Bullhorn linking the Candidate to the Job Order. We preserve the Eploy submission date and the workflow stage at submission time as custom fields on the Bullhorn submission record. Multiple submissions for the same candidate to different jobs create separate submission records.