Migrate from Kallidus Recruit to Crelate

Kallidus Recruit Candidates map to Crelate Contacts. The Candidate record holds contact details, application history, status changes, and notes. We export all submitted application data and map the primary contact email as the Crelate Contact email field. Any candidate skill tags or source attribution stored as custom properties on the Candidate record map to Crelate Contact tags. Candidates without an associated Vacancy (sourced directly into a talent pool) import as Contacts with a 'Sourced' or 'Direct' origin tag.

Kallidus Recruit Vacancy records map to Crelate Job records. We transfer role title, department, location, opening date, closing date, and pipeline assignment. Vacancy status (Active, On Hold, Filled, Closed) maps to Crelate Job status. Custom Vacancy Fields that are exposed in the Kallidus Recruit API map to Crelate Job custom fields via Crelate's Custom Forms field-mapping tool (Settings | Custom Forms), but custom fields that are not consistently exposed in exports require manual inventory during scoping.

Kallidus Recruit Applications link a Candidate to a Vacancy and carry status, submission date, screening notes, and interview scores. We preserve the full application timeline and map application status values to Crelate Job Submission status (Applied, Screening, Interview, Offer, Hired, Rejected). The submission date migrates as the Crelate Submission Date field. Interview scores and screening notes map to Crelate's activity notes linked to the Job Submission record.

Interview scheduling and outcome records tied to Applications in Kallidus Recruit map to calendar Events in Crelate linked via the Job Submission record. We transfer interview date, interviewer assignment, interview type, duration, and outcome notes. Kallidus Recruit's candidate self-scheduling module does not have a direct Crelate equivalent; we document the scheduling setup so the customer's admin can configure a Calendly or similar integration post-migration if candidate self-scheduling is required.

Internal staff and Hiring Manager accounts in Kallidus Recruit map to Crelate User records. We export user names, emails, and role assignments. Role structures differ between platforms: Kallidus Recruit uses role-based permissions scoped to Vacancies and modules; Crelate uses team-based user management. We preserve the user's name and email as the matching key and document role equivalents for the customer's admin to assign Crelate permissions post-migration. Any user without an email match in the destination requires manual Crelate User provisioning.

External agency recruiters with contact records in Kallidus Recruit's agency portal map to Crelate Contacts with an agency or external tag. Submission history attached to the agency contact migrates as notes or activities on the Contact record, as Crelate does not maintain a separate agency portal object type. Agency name, contact details, and any associated submission notes transfer directly.

Kallidus Recruit email templates with merge fields for Candidate and Vacancy data do not migrate as reusable templates. We export template bodies and field mapping documentation so the customer's admin can recreate them in Crelate's Email Template editor. The inventory includes template name, subject, body content, and the merge field mappings (Candidate name, Vacancy title, application status, etc.) for accurate rebuild.

Custom fields added to Vacancy records in Kallidus Recruit are customer-defined and not always exposed consistently in API exports. We inventory all discovered custom vacancy fields during scoping, note their data types, and create equivalent custom fields on Crelate Job records via Crelate's Custom Forms field-mapping configuration. Fields that cannot be retrieved from the Kallidus Recruit API are flagged for manual entry or alternate sourcing from a CSV export provided by the customer's administrator.

Status changes recorded on Candidate records in Kallidus Recruit (such as 'New', 'In Review', 'Interview Scheduled', 'Offer Extended') do not have a dedicated Crelate equivalent as first-class status history objects. We migrate each status change as a timestamped activity note on the Crelate Contact record, preserving the sequence and timestamp for audit purposes. If the customer requires a structured status timeline, we recommend a custom Crelate field or a linked Job Submission history view.

Kallidus Recruit Vacancy pipelines (stages within the hiring process) map to Crelate Job pipelines or workflow stages. We transfer pipeline names, stage order, and stage probabilities. Crelate's pipeline configuration is set up during the migration's development phase so that incoming Applications map to the correct stage on first insert.

Kallidus Recruit includes built-in GDPR-compliant candidate anonymisation and redaction tooling. Crelate does not have a native anonymisation feature, but GDPR compliance is addressed through data retention settings and manual or API-triggered deletion processes. We document the Kallidus Recruit anonymisation configuration so the customer's admin can establish equivalent data retention policies in Crelate or via a scheduled data cleanup workflow.

Kallidus Recruit logs all recruitment activities to support accountability and compliance audits. These audit log entries do not have a dedicated Crelate equivalent. We preserve the audit trail by migrating the underlying activity records (status changes, notes, interview outcomes, user assignments) with their original timestamps. The customer's admin can use Crelate's activity timeline for day-to-day audit purposes; for formal compliance audits, we recommend retaining the Kallidus Recruit export as an archived reference.