Migrate from Cadient to Zoho Recruit

Cadient Candidate records (name, contact info, work history, source, tags) map directly to Zoho Recruit Candidates. Zoho Recruit enforces Last Name as a mandatory field; any Cadient record without a last name is flagged during scoping and set to 'not provided' in the import file per Zoho Recruit's documented requirement. Resume content migrates as a text field or parsed structure depending on the source export format; we normalise to plain text or structured JSON before Zoho Recruit's resume parsing runs on ingest.

Cadient Requisition metadata (title, department, location, open date, hiring manager) maps to Zoho Recruit Job Opening fields. Stage definitions from Cadient (screening, assessment, interview, offer, hire) are captured as status labels in the export but the automation logic does not transfer; we document the current stage map for manual Zoho Recruit Workflow Rules rebuild. Custom requisition properties are reviewed during scoping and mapped to Zoho Recruit custom fields on the Job Opening module (Standard: 50/module, Enterprise: 300/module).

Cadient Application records (linked to a Candidate and a Requisition) map to Zoho Recruit's candidate-to-job-association. The apply date, status, source, and referral information transfer as fields on the Candidate record or as a custom application-status field depending on the customer's Zoho Recruit edition configuration. Application sub-statuses (accepted, pending, declined) that Cadient stores separately migrate as custom picklist fields in Zoho Recruit.

Cadient Scorecard responses follow a structured question-and-answer format per reviewer and per interview. These map to Zoho Recruit's Interview Feedback Form on Professional and Enterprise plans. The reviewer name, date, and each response pair transfer; the composite SmartScore aggregate migrates as a numeric custom field (informational only). Component-level score breakdowns from Cadient are not separable from the aggregate and do not map to individual Zoho Recruit feedback fields.

Cadient Interview records (interviewer, date/time, type, disposition status) map directly to Zoho Recruit Interview records. Interview type (phone, video, onsite) maps to Zoho Recruit's Interview Type picklist. Notes attached at the interview record level migrate as Zoho Recruit Notes linked to the Interview. On Zoho Recruit Enterprise, Google Meet and Microsoft Teams integrations auto-create calendar events from Interview records; these are configured post-migration.

Cadient user accounts (recruiters, hiring managers, administrators) map to Zoho Recruit Users. Migration follows Zoho Recruit's documented prerequisite: at least one user must already exist in Zoho Recruit before the bulk user import runs, and users who already have a separate Zoho Recruit organization account must close it before they can be imported into the company's Recruit account. Owner assignments on Candidate and Job Opening records resolve via email match to the imported User records.

If the Cadient deployment stores client or staffing-agency client records alongside candidate data, these map to Zoho Recruit's Client and Contact modules. Client companies map to Client records; client contact persons map to Contact records linked to the Client. Zoho Recruit's Lookup fields link Contacts to the parent Client, and additional fields (location, phone, email) map from the corresponding Cadient fields. Staffing agencies using Cadient in an agency context migrate client records to the Client module; in-house HR teams may skip this module entirely.

Cadient SmartScore is a composite signal synthesised from screening responses, references, and tenure prediction. The composite numeric score transfers as a static custom field on the Candidate record in Zoho Recruit. The component-level breakdown (screening subscore, reference subscore, tenure subscore) is not exposed via Cadient's export and therefore cannot be split into separate Zoho Recruit fields. The transferred SmartScore is informational only; Zoho Recruit's Zia AI candidate matching runs on its own model against the migrated candidate data to generate a separate Zia relevance score.

SmartTenure is a proprietary ML model outputting a stay-risk score based on signals Cadient does not expose (model weights, training data, component scores). We cannot extract anything beyond the output number. We migrate it as a static custom field on the Candidate record. Destination systems will not reproduce the score without re-running an equivalent model on the transferred data. Zoho Recruit's Zia AI or a third-party assessment integration can serve as the post-migration retention-forecast tool if the customer selects one.

Assessment results depend on the screening tool Cadient integrates with (AccurateNow, Paycor, or another provider). Raw assessment scores transfer as custom fields on the Candidate record or into the Zoho Recruit Assessments module if the customer uses Zoho Recruit's built-in assessment feature on Professional or Enterprise. Any assessment that requires re-scoring by a third-party tool (rather than re-taking) is flagged during scoping with a recommendation for the customer's HR team to coordinate with the assessment provider post-migration.

Offer letter templates and issued offer records can be exported from Cadient as documents. These transfer as attachments to the associated Candidate or Job Opening record in Zoho Recruit. Offer status (accepted, pending, declined) is often stored as an application sub-status in Cadient rather than a standalone object; we map it to a custom picklist field in Zoho Recruit to preserve the status label. Zoho Recruit's Offer Letter Templates feature (50 templates on Standard, 100 on Enterprise) is configured post-migration as a replacement for Cadient's template management.

Cadient's hiring workflow stages, routing rules, and automated trigger conditions are stored in platform configuration but do not export as structured data. We capture stage names and disposition values from the application records during data extraction and produce a written stage map (source stage label, implied automation, recommended Zoho Recruit Workflow Rule equivalent). The customer rebuilds Workflow Rules manually in Zoho Recruit (5 rules/module on Standard, 50 rules/module on Enterprise, with Assignment Rules and Blueprint automation available on Enterprise). This is explicitly a rebuild scope, not a data migration.

Cadient Notes attached to Candidate, Application, or Interview records map to Zoho Recruit Notes linked via the related record's ID. Note body content transfers as plain text; attachments on notes transfer as Zoho Recruit Attachments linked to the Note record. We preserve the original creation timestamp for audit ordering.

Cadient task records (status, priority, due date, assigned owner) map to Zoho Recruit Tasks linked to the corresponding Candidate or Job Opening. Task assignment resolves via email match to the imported User record. Recurring task patterns from Cadient do not export as structured automation; if the customer relied on recurring task generation in Cadient, that logic must be rebuilt as a Zoho Recruit Workflow Rule post-migration.

Resume files, cover letters, portfolio documents, and other file attachments linked to Cadient Candidate or Application records migrate as Zoho Recruit Attachments linked to the equivalent record. We handle file encoding (UTF-8) during the export-to-import transition and flag any files exceeding Zoho Recruit's attachment size limits for manual handling.