Migrate from Kallidus Recruit to Zoho Recruit

Kallidus Candidate records map to Zoho Recruit Candidates. The Kallidus CandidateGuid field serves as the dedupe key during import to prevent duplicate records. First Name and Last Name transfer directly, but Zoho Recruit enforces Last Name as mandatory: any Kallidus Candidate record with a blank Last Name must receive a placeholder value ('not provided', 'none', or similar) before import or the record will be silently rejected. We inventory all candidates with missing last names during discovery and apply the placeholder before the import run. Custom candidate fields from Kallidus (sector-specific screening fields, compliance flags) map to Zoho Recruit custom fields on the Candidate module if the destination plan supports them (Standard tier and above); Free tier recipients receive these values as notes on the record.

Kallidus Vacancy records map to Zoho Recruit Job Openings. Role title, department, location, opening date, and closing date transfer directly. The Kallidus pipeline stage assignment maps to a Zoho Recruit Hiring Process that we configure before migration. Active versus inactive vacancy status carries over; vacancies past their closing date are migrated with a Closed status in Zoho Recruit. Vacancy posting configurations (board-specific settings, job board distribution flags) do not transfer as structured data and are documented separately for manual reconfiguration in Zoho Recruit's job board integration settings.

Kallidus Application records link a Candidate to a Vacancy and carry submission date, screening notes, interview scores, and status history. We preserve the full application timeline in Zoho Recruit's Candidate subform tied to the Job Opening. Application status values (e.g., Applied, Shortlisted, Interview, Offer, Rejected) map to the corresponding Zoho Recruit Candidate subform status values that match the configured Hiring Process stages. Interview scores transfer as custom fields on the subform record. We resolve parent references (CandidateId, JobOpeningId) at migration time to maintain the relationship integrity.

Kallidus backoffice User accounts (internal staff, hiring managers, agency contacts) export by name, email, and role assignment. We match by email against Zoho Recruit User accounts. If a Kallidus User corresponds to an existing Zoho Recruit User record, Zoho's import will reject the duplicate; those records require the existing Zoho account to be closed or the Kallidus user to be remapped before the migration run. Role structures differ between platforms: Kallidus role groups (Recruiter, Hiring Manager, Agency, Super User) do not map directly to Zoho Recruit roles; we map to the closest Zoho Recruit role (Recruiter, Hiring Manager, Staff) and document any gap for the customer's admin to configure post-migration.

Kallidus interview scheduling and outcome records are tied to Applications. We export interview dates, interviewer assignments, interview type, and outcome notes. In Zoho Recruit, interviews attach to the Job Opening and link to the Candidate record via the Candidate subform. Candidate self-scheduling configurations in Kallidus do not transfer as settings; we document the self-scheduling setup for manual configuration in Zoho Recruit's interview scheduling module. Interview outcomes and scores attach as notes or custom fields on the interview record depending on the destination plan tier.

Kallidus email templates used for candidate communications export with merge fields for Candidate and Vacancy data. We export template bodies and field mappings as a written inventory. Zoho Recruit has its own template editor with merge field support; the customer or a Zoho partner rebuilds the template content in Zoho Recruit's editor using the exported bodies as reference. Automated email workflows (triggers, send conditions) do not migrate; we document each automation's trigger and action for rebuild in Zoho Recruit's Workflows or Blueprint builder.

Kallidus agency portal contacts store external recruiter name, agency, contact details, and submission history. We export agency name and contact details as Zoho Recruit Client records (using the Staffing Agency module or generic Client). Any candidate submissions tied to an agency contact reunify with the migrated Candidate records during the Application import phase. Agency-specific submission preferences (required fields, formatting rules) are documented as text for manual reconfiguration in Zoho Recruit's staffing portal settings on Enterprise tier.

Kallidus organisations can add custom fields to Vacancy records to capture sector-specific data. These fields are customer-defined and not always exposed consistently in exports. We inventory every custom vacancy field during discovery: field name, data type, picklist values, and which vacancies use it. Custom fields transfer to Zoho Recruit custom fields on the Job Opening module if the destination plan supports them (Standard tier and above). On Free or Standard tier without custom field access, values transfer as notes on the Job Opening record with a structured prefix (e.g., '[Custom: Sector] Manufacturing'). The customer chooses the strategy during scoping.

Kallidus Application status change timestamps are preserved in the Application migration as historical subform entries. We set the Created Date on each subform row to the original Kallidus timestamp so that the hiring timeline is auditable in Zoho Recruit. Status transitions (Applied, Screening, Interview, Offer, Rejected, Withdrawn) carry the original Kallidus status label mapped to the equivalent Zoho Recruit Hiring Process stage value.

Kallidus notes attached to Candidate records migrate as Zoho Recruit Notes linked to the Candidate. Note body, author, and creation timestamp transfer. We resolve the author reference to the migrated User record where possible; notes with unresolvable authors attach with the original author name in the note body text.

Kallidus GDPR-compliant candidate anonymisation and redaction records (where a candidate has exercised a right to be forgotten or requested partial anonymisation) transfer as a note on the Candidate record indicating the anonymisation status and date. Full GDPR record deletion requests cannot be fulfilled by migration: we document any candidate with a deletion flag so the customer can decide whether to exclude the record, partially migrate it, or honour the deletion before migration begins.

Kallidus integrations to Xref reference checks and Adobe Sign document flows attach documents and check results to Candidate or Application records. These linked records do not export as structured data and may reference third-party systems that will not be connected post-migration. We flag every Xref and Adobe Sign attachment during discovery, document the integration configuration, and provide the customer with a Zoho Recruit-native replacement plan (e.g., Verified First for background checks, Zoho Sign for document flows) for manual reconfiguration after migration.