Migrate from Kallidus Recruit to Recruit CRM & ATS

Candidates in Kallidus Recruit are the primary recruiting record holding contact details, application history, status changes, and notes. We export candidates including name, email, phone, address, CV, source, and any active custom candidate fields. In Recruit CRM, Contacts are the central entity. We map candidates to Recruit CRM Contacts with the original Kallidus candidate status preserved in a custom field kr_original_status__c for reconciliation. Agency-submitted candidates are flagged with a note on the contact linking to the agency record for deduplication against the agency contact migration.

Vacancies in Kallidus Recruit hold role title, department, location, opening date, closing date, and pipeline stage. We map Vacancy to Recruit CRM Job, converting the Kallidus vacancy closing date to the Recruit CRM application deadline. Custom vacancy fields migrate as Job custom fields (see Custom Vacancy Fields mapping). The Kallidus pipeline stage assignment maps to a Recruit CRM Deal Pipeline stage only if the customer is actively managing vacancy progress through a deal-style workflow; otherwise the Job status (Open, On Hold, Filled, Cancelled) replaces the pipeline stage as the primary status indicator.

Applications link a Candidate to a Vacancy in Kallidus Recruit and carry submission date, status, screening notes, and interview scores. We map Applications to the Candidate-Job association in Recruit CRM, preserving the full application timeline and mapping Kallidus status values to Recruit CRM application status equivalents (Applied, Screening, Interview, Offer, Hired, Rejected). We inventory all non-standard status values during scoping and configure matching status options in Recruit CRM before the application import phase.

User accounts in Kallidus Recruit exist in the backoffice with role-based permissions (internal staff, hiring managers, agency contacts). We export user names, emails, and role assignments. In Recruit CRM, internal recruiters map to Team Members with appropriate role assignments. Hiring managers who do not log in to Recruit CRM are provisioned as Clients so that the Owner reference on candidate and job records resolves correctly. Role structures differ between the two platforms, so we inventory all Kallidus role types during scoping and map them to the closest Recruit CRM permission group.

Interview scheduling and outcome records in Kallidus Recruit are tied to Applications and include date, time, interviewer assignment, location or meeting link, outcome, and notes. We export interview records and map them to Recruit CRM Activities attached to the relevant Contact (candidate). We preserve the original interview date and interviewer assignment. Note that Kallidus self-scheduling and calendar invite features do not have a direct Recruit CRM equivalent; we flag this scheduling workflow for manual reconfiguration in Recruit CRM's calendar integration settings during the post-migration handoff.

Notes and comments attached to Candidates and Applications in Kallidus Recruit migrate to Notes in Recruit CRM. We export the note body, author, and timestamp and link each Note to the relevant Contact record via the candidate migration. Rich text formatting in Kallidus notes is preserved where the export preserves HTML; plain-text fallbacks are applied where formatting is not preserved in the source export.

External agency recruiters who submit candidates via the Kallidus agency portal have separate contact records with agency name, contact details, and associated submission history. In Recruit CRM there is no separate agency contact object; agency information merges into the Contact record. We export agency contacts and their submission history, then during the candidate import we attach agency attribution as a note or custom field on each candidate record. Where a candidate has been submitted by multiple agencies, we create separate candidate records with a shared agency reference note to avoid contact deduplication conflicts.

Organisations can add custom fields to Vacancy records in Kallidus Recruit to capture sector-specific or client-specific data. These are customer-defined and not always exposed consistently in exports. We inventory all active custom vacancy fields during scoping, identify which are actually populated on records versus which are empty templates, and configure matching custom fields on the Recruit CRM Job object before vacancy data is imported. Fields with no data are noted in the inventory document for the customer to assess whether they are still needed.

Email templates in Kallidus Recruit use merge fields for Candidate and Vacancy data and are stored in the backoffice. We export template bodies and merge field mappings so they can be recreated in Recruit CRM's unlimited email template editor. Templates do not migrate as code; the customer or their onboarding contact rebuilds them in Recruit CRM using the exported content as the source copy.

Kallidus Recruit uses a Kanban-style vacancy pipeline with configurable stages within the Vacancy object. Recruit CRM uses Deal Pipelines as a separate workflow object attached to Jobs. If the customer is actively tracking vacancy progress through pipeline stages (rather than using simple status values), we configure the Deal Pipeline in Recruit CRM during the schema setup phase, mapping each Kallidus stage to a corresponding Deal Pipeline stage with equivalent probability and status labels.