Migrate from Cadient to Recruit CRM & ATS

Cadient Candidate records map to Recruit CRM Candidate with direct field correspondence for name, contact information, work history, source, and tags. Resume files export as document attachments and are re-uploaded to Recruit CRM. SmartScore migrates as a static numeric custom field; SmartTenure stay-risk score migrates as a read-only informational field only. We normalize contact phone and email formats during ingestion to match Recruit CRM field validation requirements.

Cadient Requisition records (title, department, location, open date, hiring manager) map to Recruit CRM Job records. Stage definitions and routing rules migrate as metadata documentation only; Recruit CRM's Job pipeline stages must be configured manually in the platform. Any custom requisition properties (cost center, security clearance, remote policy) are mapped to Recruit CRM custom fields created during schema design.

Cadient Application records link Candidate to Requisition and include apply date, status, source, and referral information. These map directly to Recruit CRM Application records with the parent-lookup resolution (CandidateId and JobId) resolved at import time. Offer status migrates as an application sub-field; if offer status is stored as a separate Cadient record, it is migrated as a custom Application field.

Cadient Scorecard responses follow a structured question-and-answer format per reviewer. The full response history migrates to Recruit CRM as structured custom fields on the Candidate or Application record. SmartScore aggregates migrate as a numeric field; component-level score breakdowns are not separately exported from Cadient and therefore cannot be reconstructed in Recruit CRM.

Cadient Interview records (interviewer, date/time, type, disposition status) map to Recruit CRM Interview records with StartDateTime, EndDateTime, and Location preserved. Interview type (phone, video, onsite) migrates as a custom picklist. Notes attached at the interview record level migrate as Candidate notes in Recruit CRM. Interviewer resolution is done by email matching against Recruit CRM users.

SmartScore is a composite signal synthesized from screening, references, and tenure prediction. The composite numeric value transfers as a static custom field on the Candidate record. The component-level breakdown (screening score, reference score, tenure signal) is not exposed in Cadient's export and therefore cannot be separated in Recruit CRM. Recruit CRM does not have a native equivalent SmartScore field.

SmartTenure is a proprietary ML model that outputs a stay-risk score using signals Cadient does not expose. Model weights and raw component signals are not available via any documented export mechanism. We migrate the tenure-prediction value as a read-only informational custom field on the Candidate record with a label indicating it was derived from Cadient's proprietary model and cannot be regenerated in Recruit CRM without re-running an equivalent model on the transferred candidate data.

Cadient hiring workflow stages (screening, assessment, interview, offer, hire) and automated routing rules do not export as structured automation data. We capture stage names and disposition values from application records during data extraction and produce a written stage map documenting the current Cadient workflow. Recruit CRM's workflow automation is rebuilt manually from this documentation by the customer's admin team post-migration.

Assessment results depend on the screening tool Cadient integrates with (AccurateNow, Paycor, or other). We migrate raw assessment scores as custom fields on the Candidate record in Recruit CRM. Any assessments requiring re-scoring in a Recruit CRM-native or integrated screening tool are flagged with a re-score recommendation documented in the migration inventory.

Cadient Owners map to Recruit CRM User records resolved by email match. Any Cadient Owner without a matching Recruit CRM User goes to a reconciliation queue for the customer's admin to provision before record import resumes. User provisioning in Recruit CRM is handled by the customer directly and validated before migration proceeds.