Migrate from Cadient to Crelate

Cadient Candidate records map to Crelate Contact as the primary person record. Standard fields (name, email, phone, work history, source, tags) migrate directly. Cadient's SmartScore composite value migrates as a static numeric custom field on the Contact record since the component-level breakdown is not available. SmartTenure predictions migrate as a static informational field (stay-risk score only, no model recalculation in Crelate). Resume parsing output normalises to plain text or structured JSON for Crelate's Resume Toolbox.

Cadient Requisition records map to Crelate Opportunity. Requisition metadata (title, department, location, open date, hiring manager) maps directly to Opportunity fields. Status from Cadient (open, filled, cancelled) maps to Crelate Opportunity Stage values. A Crelate Opportunity represents the hiring requisition as a pipeline record against which Applications are tracked as activity submissions.

Cadient Application records are linked to a Candidate and a Requisition. In Crelate, Applications map to Activity Forms submitted against the Contact (from Cadient Candidate) and the related Opportunity (from Cadient Requisition). The apply date, status, source, and referral data migrate as form response fields. Custom application properties are reviewed during scoping and mapped to Crelate custom question fields on the Activity Form.

Cadient Scorecard responses follow a structured question-and-answer format per reviewer. These migrate to Crelate Activity Forms with individual field mappings to Contact or Opportunity records per the form configuration. Crelate's field mapping capability (one field per form question, mapped to a column on Contact, Company, or Opportunity) is used to route scorecard ratings to structured custom fields. The composite SmartScore aggregate migrates as a numeric value; component-level breakdowns are not separable for independent mapping.

Cadient Interview records (interviewer, date/time, type: phone/video/onsite, disposition status) migrate to Crelate Event records linked to the Contact and Opportunity. Interview notes attached at the record level migrate as Crelate Activity Form entries or as Event description text. Attendance or scheduling integration depends on the customer's calendar setup at migration time.

SmartTenure is a proprietary ML model that outputs a stay-risk score based on signals Cadient does not expose. Model weights, training data, and component signals are not available via any documented export mechanism. We migrate the numeric score as a static custom field on the Contact record. Crelate's AI Co-Pilot and Agents on Business Plus and Enterprise can be configured by the customer's admin to generate new retention signals from candidate data post-migration; this is outside our migration scope.

SmartScore is a composite signal synthesised from screening responses, reference checks, and tenure prediction. The composite score transfers as a numeric field on the Contact record. The component-level breakdown (screening subscore, reference subscore, tenure subscore) is not separated in Cadient's export, so we cannot map these independently. The composite value is informational only in Crelate; it does not trigger any Crelate automation without manual workflow configuration.

Cadient's hiring workflow stages (screening, assessment, interview, offer, hire) and automated routing rules are stored in platform configuration but do not export as structured data. We capture stage names and disposition values from application records during data review and document the current stage map in the discovery deliverable. The customer rebuilds these stages as Crelate Opportunity pipeline stages manually. Custom Recruiting Workflow limits are 20 on Crelate Business tier.

Cadient integrates with screening tools such as AccurateNow and Paycor for structured assessments. Assessment scores are stored in Cadient as custom fields or application properties. We migrate raw assessment scores as Crelate custom fields on Contact or as fields within an Activity Form. Any assessments that require re-scoring through a new vendor integration are flagged during scoping for the customer's admin to re-implement post-migration.

Cadient offer letter templates and issued offer records can be exported as documents. In Crelate, these migrate as document attachments to the related Opportunity or Contact record using Crelate's Resume Toolbox or custom document attachment capability. Offer status (accepted, pending, declined) may be stored as an application sub-status in Cadient rather than a standalone field; we map it to a Crelate custom Opportunity field or Activity Form response.

Cadient SmartRefer tracks referral sources as a performance channel within the hiring funnel. Referral source data migrates as a standard Contact source field or custom field in Crelate. The referral attribution model (which employee referred which candidate) maps to Crelate's Candidate Source Tracking and can be used in Crelate's reporting and analytics.

Cadient Owner records (hiring managers, recruiters) are resolved by email match against Crelate User records during migration. Any Cadient Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import. User provisioning in Crelate is a customer-admin action; we flag gaps before production migration begins.