Migrate from Bullhorn Connexys ATS to Bullhorn ATS & CRM

Bullhorn Connexys Candidate records map directly to Bullhorn Candidate records. Standard fields (name, email, phone, resume, work history, skills, salary, tax information) export cleanly via the Salesforce REST API and import to Bullhorn via the Candidate entity endpoint. We preserve GDPR consent flags as a custom consent field and flag any Candidate records with incomplete Tax Info for admin review before import.

JobOrder records from Connexys map to Bullhorn JobOrder with all standard job fields (title, description, requirements, salary range, status) preserved. Custom job fields migrate as Bullhorn custom fields with equivalent data types. We resolve the pipeline stage association to the Job Reporting object during import so that stage history is seeded from day one rather than requiring reconstruction.

Connexys Account records (representing client companies) map to Bullhorn Account. The one-to-many relationship between Accounts and multiple Contacts is preserved. Billing, industry, and contact association data migrate as standard Account fields. Multi-office Account structures in Connexys map to multiple Account records in Bullhorn or to a single Account with branch custom fields, depending on the customer's preference during scoping.

Connexys Contact records (hiring managers and client-side contacts) map to Bullhorn Contact with the Account-Contact association preserved via the AccountId lookup. Custom Contact fields migrate to Bullhorn custom Contact fields. Any Contact records without an associated Account are held in a reconciliation queue for the customer's admin to resolve before final import.

Placement records in Connexys map to Bullhorn Placement, linking the Candidate to the JobOrder and recording start date, salary, billing rate, and status. Placement records are imported after both Candidate and JobOrder are present in Bullhorn to satisfy foreign-key constraints. Historical Placements retain their original start dates and status values.

The Job Reporting junction object in Bullhorn ATS v1 tracks each Candidate's movement through pipeline stages (Application, Submittal, Interview, Offer, Placement) with timestamps and associated User. We audit Job Reporting completeness in Connexys during discovery. If stage-transition records are incomplete or contain errors, we reconstruct missing transitions from the JobOrder's activity log where timestamps are available, and flag any periods where stage history cannot be verified.

Connexys Custom Objects built on the Salesforce platform migrate to Bullhorn Custom Objects with equivalent field structures. Bullhorn Custom Objects support up to 55 fields per object with the same edit-type limits (up to 20 checkboxes, dropdowns, or pickers per object). We pre-create the Bullhorn Custom Object schema using the Custom Object Setup Spreadsheet submitted via Bullhorn Support before any data import. If the source Connexys instance uses more Custom Objects than the destination Bullhorn edition allows (10 for Front Office Growth/Enterprise, 2 for Bullhorn ATS), we cull objects explicitly identified by the customer before migration.

Connexys User records map to Bullhorn User records. We resolve users by email address. Any Connexys User without a matching Bullhorn User is held in the reconciliation queue; the customer's Bullhorn admin provisions missing Users (active or inactive based on the original user's status) before record import resumes. Owner assignments on Candidate, JobOrder, and Placement records are resolved at migration time using the User mapping table.

Resume files export from Connexys via the Salesforce ContentDocument and ContentVersion objects. We extract the parsed resume text (stored in Connexys custom fields or the resume body) and import it to Bullhorn's Candidate resume field. File attachments migrate as Bullhorn document records linked to the parent Candidate, Contact, JobOrder, or Placement. Large attachment volumes require chunked handling to stay within Bullhorn API throughput limits.

Bullhorn Connexys tracks activity feeds and notes on Candidate, Contact, JobOrder, and Placement records via Salesforce Activity and ContentNote objects. We export note body text and timestamps and import them to Bullhorn's activity feed and notes section. Activity timestamps preserve the original Connexys date to maintain the timeline audit trail. Note attachments migrate as ContentDocument records linked via ContentDocumentLink to the parent record.

Candidate Tax Info (federal filing status, exemptions) and region-specific compliance custom fields migrate as Bullhorn custom Candidate fields. GDPR consent records are preserved as a consent-date custom field with a boolean consent-given flag. If Connexys uses Salesforce GDPR consent objects, we map those to the equivalent Bullhorn custom fields during transformation.

Connexys integrations installed from the Salesforce AppExchange (third-party VMS connectors, payroll tools, background check providers) do not migrate automatically to Bullhorn. We deliver a written inventory of every active AppExchange package with its purpose, configuration, and recommended Bullhorn Marketplace equivalent or native Bullhorn replacement. The customer's admin or a Bullhorn implementation partner reinstalls and reconfigures integrations post-migration.