Migrate from Bullhorn Connexys ATS to Crelate

Bullhorn Candidate records map directly to Crelate Contact records. We preserve name, email, phone, resume content (parsed or raw), work history, skills, salary expectations, and source attribution. Candidate status from Bullhorn (Active, Inactive, Archived) maps to Crelate Contact status. Custom fields on Candidate beyond the 20-field Crelate entity cap require field-culling decisions during scoping; we flag the top-used fields and recommend which to drop based on usage frequency data from the discovery audit.

Bullhorn ClientCorporation records map to Crelate Company records. We preserve company name, industry, address, billing information, and linked Contact associations. ClientCorporation custom fields migrate subject to the 20-field cap per entity. Multiple Contacts per Company in Bullhorn map cleanly to the Crelate Company-Contact relationship.

Bullhorn ClientContact records (hiring managers, client-side contacts) map to Crelate Contact records linked to the corresponding Company. We preserve name, email, phone, title, and the relationship to ClientCorporation. ClientContact custom fields migrate subject to the 20-field per-entity cap. If a ClientContact in Bullhorn has no associated ClientCorporation, we create a stub Company record to satisfy Crelate's Company-Contact relationship.

Bullhorn JobOrder records map to Crelate Job records. We preserve job title, requirements, salary range, location, job description, status (Open, Placed, Closed), and owner assignment. Custom fields on JobOrder migrate subject to the 20-field cap. Bullhorn job status flags (Hot, Priority) map to Crelate custom Job fields if the customer's workflow depends on them.

Bullhorn JobSubmission is a junction object linking a Candidate to a JobOrder with a submission date, status, and history. Crelate has no separate JobSubmission entity — candidate-to-job associations are tracked via pipeline stages on the Job. We resolve this by mapping the JobSubmission status to the appropriate pipeline stage in Crelate (Applied, Screening, Interview, Offer, Hired). The submission timestamp becomes the stage-entry timestamp. If a Candidate was submitted to the same JobOrder multiple times (re-submissions), we create separate pipeline entries or consolidate based on the customer's preference during scoping.

Bullhorn Placement records capture the final hire outcome: Candidate, JobOrder, start date, salary, bill rate, and placement status. We map Placements to Crelate Job records with a filled status, and create an Opportunity record linked to the Job and the placing Contact for revenue tracking. The Placement start date, salary, and bill rate migrate to custom fields on the Crelate Job record. If the customer uses Placement for commission or billing tracking, we map that data to Opportunity fields or a custom Crelate field.

Bullhorn Custom Objects (up to 10 instances on Front Office Growth/Enterprise, each with up to 55 fields) extend Candidates, Contacts, Companies, Jobs, and Placements. Crelate has no separate Custom Object entity. We audit every Bullhorn Custom Object and field during discovery, then compress them into custom fields on the corresponding Crelate entity. Fields exceeding the 20-field cap are prioritised by usage frequency and any beyond the cap are documented for the customer's admin to handle manually post-migration. This is the most significant data-fidelity risk in the migration and requires explicit sign-off before migration begins.

Bullhorn User records representing recruiters, administrators, and managers map to Crelate User records. We resolve User assignments on Candidate, JobOrder, and Placement records by email match. Any Bullhorn User without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Bullhorn users map to inactive Crelate users to preserve historical assignment audit trails.

Resume files and attachments export from Bullhorn via REST API and ingest into Crelate as Contact attachments or Job attachments. We handle chunked extraction for large file volumes and preserve the link to the parent Contact or Job record. Parsed resume data (skills, work history, education) maps to the corresponding Crelate Contact fields; raw resume files are attached as documents. We flag any file type that Crelate's attachment API does not support and flag them for manual upload post-migration.

Bullhorn Job Reporting tracks each Candidate's movement through pipeline stages with timestamps and the assigning User. Crelate does not expose an equivalent junction object; stage history is implicit in the pipeline timeline. We reconstruct stage-transition history as a series of Crelate stage entries with timestamps, and preserve the assigning User by linking to the Crelate User. If Job Reporting records in the source are incomplete or contain errors (a known Bullhorn data-quality issue), we reconstruct missing transitions where source data allows and flag gaps in the delivered migration report.

Bullhorn Notes, Appointments, and Tasks on Candidate, Contact, JobOrder, and Placement records map to Crelate Activities linked to the corresponding Contact or Job. Note body text, appointment details (date, duration, location), and task details (status, priority, due date) migrate directly. Timestamp preservation ensures the activity timeline reflects the original Bullhorn record dates. Linked User assignments migrate via the User email resolution.

Candidate Tax Info (federal filing status, exemptions) and compliance-related custom fields vary by region and Bullhorn instance configuration. We map standard compliance fields to Crelate custom fields on the Contact record, subject to the 20-field cap. GDPR consent records migrate to a custom Crelate field capturing consent date, consent type, and source. Any compliance fields exceeding the cap are flagged for the customer's admin to address post-migration.