Migrate from Kallidus Recruit to BambooHR

Kallidus Candidate records map to BambooHR Candidate records when BambooHR ATS (Hiring) is enabled on the destination account. We map first name, last name, email, phone, address, and any structured profile fields. Candidate status history (active, archived, hired) migrates to BambooHR's candidate stage values. If the destination account does not have BambooHR ATS enabled, candidates map to the employee's pre-hire applicant record or are flagged for the customer to enable the module before import.

Kallidus Application records link a Candidate to a Vacancy and carry submission date, screening notes, interview scores, and status transitions. We preserve the full application timeline and map Kallidus status values (applied, shortisted, interview, offer, rejected, withdrawn) to the nearest BambooHR Hiring stage. Screening notes and structured scores migrate to BambooHR's scorecard fields and candidate notes sections.

Kallidus Vacancy records map to BambooHR Job postings. Role title, department, location, employment type, salary range, and opening and closing dates transfer directly. Vacancy pipeline configurations (custom stages beyond the standard apply-interview-offer-hire flow) require manual reconstruction in BambooHR Hiring because BambooHR uses a fixed stage model that admins can extend but not fully replicate from Kallidus's pipeline builder.

Kallidus Interview records carry interview date, interviewer assignment, and outcome. We map interview dates and interviewer names to BambooHR Hiring interview records attached to the relevant Candidate. Interview scores and interviewer feedback notes migrate to BambooHR scorecard fields. Candidate self-scheduling configuration from Kallidus does not transfer; we document the self-scheduling workflow for the admin to configure in BambooHR's interview scheduling settings.

Kallidus internal user accounts (HR administrators, hiring managers) map to BambooHR Employee records. We export user name, email, and role assignment. Kallidus role permissions (admin, hiring manager, agency) do not map directly to BambooHR's permission groups; we flag role discrepancies so the customer maps them to BambooHR's HR Admin, Manager, or Employee permission tiers during configuration.

External agency recruiter contacts and their submission history in Kallidus do not have a dedicated BambooHR object. We map agency contact details to a custom BambooHR Candidate field (externalAgency__c) and preserve any associated candidate submissions under the same candidate record. The customer manually configures any preferred-agency relationships in BambooHR's ATS settings if the BambooHR ATS add-on supports that feature.

Kallidus custom vacancy fields capture sector-specific data beyond the standard vacancy record. These are customer-defined and not always consistently exposed in Kallidus exports. We inventory all active custom vacancy fields during discovery, map them to BambooHR custom candidate fields where the data type is compatible (text, number, date, dropdown), and flag any unsupported field types for manual entry or alternative handling.

Kallidus email templates with merge fields for Candidate and Vacancy data are exported as template bodies with field mappings. BambooHR Hiring supports candidate communication templates with merge fields. We export the template bodies and field references and provide a written mapping guide for the customer to recreate templates in BambooHR's email template editor. Active email automation rules tied to these templates are inventoried and flagged for rebuild in BambooHR Workflows.

Kallidus records every Candidate status transition with a timestamp and optional note. We preserve the complete status change log as a structured set of entries appended to the BambooHR Candidate record's history section. Status timestamps are preserved as metadata fields on each stage entry to maintain the original timeline fidelity.

Kallidus application-level notes and file attachments (CVs, cover letters, reference documents) migrate to BambooHR candidate notes and file attachments respectively. We use BambooHR's file upload API to transfer attachments directly, preserving original file names and MIME types. If third-party document integrations such as Adobe Sign are attached to applications, we flag these during discovery for manual reconfiguration in BambooHR's document settings.