Migrate from Cadient to Bullhorn ATS & CRM

Cadient Candidate records map directly to Bullhorn Candidate. Standard fields (firstName, lastName, email, phone, address, workHistory, education, source, tags) transfer cleanly. Resume content migrates as a text blob or structured JSON depending on what the Cadient export produces; we normalise to a plain-text resume body attached to the Bullhorn Candidate record. Candidate status values from Cadient (active, screening, interviewed, offered, hired, rejected) map to Bullhorn Candidate status or a custom status field depending on the customer's stage naming convention.

Cadient Requisition records map to Bullhorn JobOrder. The Requisition title, department, location, open date, hiring manager, and employment type fields transfer to equivalent JobOrder fields. Custom Requisition properties (industry-specific fields, department-specific criteria) migrate as Bullhorn custom fields on JobOrder. We flag any Requisition with a status of 'filled' or 'cancelled' for potential placement record creation in Bullhorn if the customer wants historical placement history preserved.

Cadient Application records (Candidate-to-Requisition links) map to Bullhorn Application. Apply date, status, source, referral source, and any custom application properties migrate directly. The Application record resolves its parent Candidate and JobOrder lookups at migration time using email-based Candidate matching and JobOrder title-plus-location deduplication. Any application sub-status fields (offer extended, background check pending) migrate as custom fields if they cannot map to a standard Bullhorn Application status value.

Cadient Scorecard responses follow a structured question-and-answer format per reviewer. We preserve the full response history as a Bullhorn custom object (PlacementCustomObject or a named custom object if Bullhorn schema allows) linked to the Application or Candidate record. The custom object schema (question text, answer value, reviewer name, review date) is pre-built in Bullhorn before migration. Scorecard question sets vary by Requisition type; we capture the template name during scoping for the admin to decide which Bullhorn custom object applies per JobOrder type.

Cadient Interview records (interviewer, date/time, type, disposition) map to Bullhorn Interview records if the destination Bullhorn instance has the Interview module enabled, or to a custom Interview object we pre-build. Interview type (phone, video, onsite) and disposition status transfer as typed fields. Interview notes attached at the record level migrate as Note records linked to the Interview custom object. We preserve the original interview schedule ordering by setting the date fields to match the Cadient source timestamps.

SmartScore is a composite signal synthesised from screening, references, and tenure prediction. The composite numeric score transfers as a static custom field on the Bullhorn Candidate record. The component-level score breakdown (screening sub-score, reference sub-score, tenure sub-score) is not separable from the Cadient export because Cadient does not expose these as distinct fields; we transfer only the aggregate number. Bullhorn Amplify AI will generate fresh candidate intelligence scores in the destination system using Bullhorn's own model.

SmartTenure is a proprietary ML model that outputs a stay-risk score. The model weights, training data, and component signals are not exposed via any documented export mechanism. We transfer the numeric tenure score as a read-only informational custom field on the Bullhorn Candidate record, labelled as a historical Cadient signal. Bullhorn does not reproduce this score; any retention-prediction capability requires running Bullhorn Amplify or a third-party AI tool on the transferred candidate data.

Cadient Requisitions may carry custom fields beyond the standard title/department/location set. We audit these during discovery, pre-create matching custom fields on Bullhorn JobOrder before migration, and map them during the Requisition import phase. Any multi-select or checkbox fields from Cadient map to Bullhorn multi-select picklist or checkbox fields depending on which Bullhorn field type is available in the customer's Bullhorn edition.

Cadient candidate tags (source tags, skill tags, flag tags) migrate to Bullhorn Candidate Categories if the Bullhorn instance uses the standard category taxonomy, or to a custom multi-select picklist field if the customer uses a non-standard tagging model. Tag strategy is confirmed during scoping because Bullhorn's category taxonomy is configurable at the org level.

SmartRefer tracks which employee referral programme generated a candidate. The referral source field in the Cadient export migrates to the Candidate source or a custom referral tracking field on Bullhorn Candidate. We preserve the original referral attribution but note that the SmartRefer programme logic (points, notifications, incentive triggers) requires reimplementation in Bullhorn's native referral tracking or a Bullhorn Automation flow.

Cadient offer letter templates and issued offer records can be exported as documents. Offer status (accepted, pending, declined) may be stored as an application sub-status rather than a standalone object. We map accepted offers to Bullhorn Placement records, pending offers to a custom Offer object or Opportunity record, and declined offers to a Note with disposition. The offer document itself migrates as a ContentDocument attached to the relevant Placement or Candidate record.

Assessment results depend on the screening tool Cadient integrates with (AccurateNow, Paycor, or other). We migrate raw assessment scores as custom fields on the Bullhorn Candidate record. Assessments that require re-scoring in the destination system (because the original assessment tool is not connected to Bullhorn) are flagged during discovery with a recommendation to configure the relevant Bullhorn-native or third-party screening integration post-migration.