Migrate your Kallidus Recruit data

Candidates are the primary record in Kallidus Recruit, holding contact details, application history, status changes, and notes. We export candidate profiles including all submitted application data and map them to the destination ATS's contact or candidate object. We flag candidates with anonymised or redacted records (as supported by the platform's GDPR tooling) so their re-identification is handled with appropriate consent during import.

Vacancies are job postings tied to specific pipelines and pipeline stages within the backoffice. We map Vacancy records including role title, department, location, opening date, and closing date. Custom vacancy fields are exported as supplemental columns and mapped to equivalent custom fields in the destination.

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 status values to the destination's closest equivalent stage name, flagging any non-standard statuses that may require manual review.

User accounts (internal staff, hiring managers, agency contacts) exist in the backoffice with role-based permissions. We export user names, emails, and role assignments. Role structures differ between platforms so we map to the nearest equivalent permission model in the destination, noting any elevated-access accounts that require special handling.

Interview scheduling and outcome records are tied to Applications. Kallidus Recruit supports candidate self-scheduling via its interview management module. We export interview dates, interviewer assignments, and outcome notes. Where interview slots are calendar-linked, we flag the dependency so calendar integration is re-established in the destination system.

Email templates used for candidate communications are stored in the backoffice with merge fields for Candidate and Vacancy data. We export template bodies and field mappings so they can be recreated or replicated in the destination's email system. Custom merge-field logic requires manual review to ensure parity.

External agency recruiters who submit candidates via the agency portal have separate contact records. We export agency name, contact details, and any associated submission history. Agency-to-candidate relationships are preserved as tags or associations in the destination.

Organisations can add custom fields to Vacancy records to capture sector-specific data. These are customer-defined and not always exposed consistently in exports. We inventory custom vacancy fields during discovery and map each to the destination's equivalent custom field or store as structured metadata alongside the vacancy record.