Migrate from Paradox to Bullhorn ATS & CRM

Paradox Candidates with an active hiring pipeline status map to Bullhorn Lead for unqualified prospects and Bullhorn Contact for candidates attached to a ClientCorporation. We apply a status-based split rule during scoping: Candidates with a status of Applied or Screening map to Lead; status of Interview, Offer, or Hired map to Contact with ClientCorporationId resolved. The original Paradox candidate status is preserved in a custom field paradox_original_status__c on both Lead and Contact for audit trail and reporting continuity.

If the destination Bullhorn org uses Bullhorn Candidate Management (a product layer available on Core and above) rather than the standard Lead-Contact model, we map Paradox Candidates directly to the Bullhorn Candidate entity with all screening responses, scheduling data, and custom field values preserved. We configure the Bullhorn Candidate custom object during schema pre-configuration before any data import begins.

Paradox Jobs map directly to Bullhorn JobOrder. The Job title, description, status (open, closed, filled), and hiring-team assignments migrate as JobOrder fields. Active job status is preserved; closed jobs are migrated as historical records with status set to 'Closed' in Bullhorn. We resolve the Job's owning recruiter (Paradox owner) to a Bullhorn User by email match before JobOrder import.

Paradox Jobs reference a company or client. We map the parent company to Bullhorn ClientCorporation, creating the corporation record first and linking it to the JobOrder via clientCorporationID. If the Paradox Job does not have an associated client (internal requisition), we create a ClientCorporation record labeled 'Internal' and link it explicitly.

Paradox Events (scheduled interviews and assessments) map to Bullhorn PlacementInterview records. Start datetime, end datetime, interview type, and participant assignments migrate. The participant links (candidate, interviewer) are resolved via the Paradox Candidate to Bullhorn Lead/Contact mapping and the Paradox owner to Bullhorn User mapping. If the destination Bullhorn instance does not have PlacementInterview configured, events migrate as CalendarEvent records with a custom event_type field set to 'Interview'.

Paradox Olivia screening response logs are structured Q&A conversations between the chatbot and the candidate. Bullhorn has no native screening-response object, so we map these to Bullhorn Note records attached to the candidate's Lead or Contact. Each Note captures the question text, answer text, and timestamp from the Paradox interaction. If the customer uses a third-party screening tool integrated with Paradox, we flag the tool for separate export handling and do not assume the screening content lives inside Paradox.

Paradox Schedules capture candidate availability windows and calendar-linked scheduling links. Bullhorn stores interview scheduling within PlacementInterview and through Bullhorn's native calendar sync (Outlook and Gmail). We migrate schedule availability data as Bullhorn Note records with type 'Availability' on the candidate record, noting that live calendar integration links do not transfer and must be re-established in Bullhorn by the customer's admin post-migration.

Paradox attachments (resumes, cover letters, portfolio files) are exported as binary files and re-uploaded to Bullhorn. We map to Bullhorn's native attachment model (CandidateAttachment for candidate-linked files, or ContentDocument via Salesforce Files for org-wide document management if the Bullhorn instance is on the Salesforce platform). File names, MIME types, and upload timestamps are preserved. File content is not re-formatted; binary integrity is validated post-upload via checksum.

Paradox custom fields on Candidates vary by customer configuration and have no standard export list. We capture the full custom field schema during pre-migration discovery, map Paradox field types (text, number, date, checkbox, dropdown) to the equivalent Bullhorn field type (Text, Number, Date, Checkbox, Picklist), and configure the Bullhorn custom fields in the destination org before any record import. Custom fields that have no Bullhorn equivalent are flagged for the customer's admin to decide whether to create a matching field or drop the data.

Paradox custom fields on Jobs migrate to Bullhorn JobOrder custom fields following the same type-mapping approach. We configure the JobOrder custom fields in Bullhorn's Job Order Custom tab during schema pre-configuration. Any conditional visibility or required-flag logic from Paradox does not transfer; Bullhorn's field-level security is configured independently.

Paradox Offer records (compensation details, status, approval workflow) map to Bullhorn Placement for candidates who reached offer stage in the Paradox pipeline. Offer status history migrates as Placement history records. Compensation amounts, start date, and job title at offer migrate as Placement fields. Note that Paradox offer templates or approval routing logic do not transfer; Bullhorn's offer approval workflow is configured by the customer's admin post-migration.

Paradox Assessment results (score, status, linked candidate) migrate as Bullhorn Note records with type 'Assessment' attached to the candidate's Lead or Contact. If the customer uses a named third-party assessment provider that is integrated with Paradox, we flag the tool and recommend exporting assessment content from the source tool directly rather than relying on Paradox as the system of record for assessment artifacts.

Paradox Groups representing departments, locations, or cost centers map to Bullhorn BusinessSector or to a custom entity depending on the customer's Bullhorn configuration. Group hierarchies with nested depth are flattened in Bullhorn if the destination org does not support multi-level grouping; we document the full Paradox group tree during discovery and advise the customer on the appropriate Bullhorn entity structure.