Migrate from Kula to Recruit CRM & ATS

Kula Candidate records map directly to Recruit CRM Candidate records. Contact information, work history, sourced profile data, and tags transfer as standard fields. Kula's AI-generated resume scores transfer as read-only text fields (not live metrics) because Recruit CRM has no equivalent scoring engine. Candidate status from Kula (active, archived, disqualified) maps to Recruit CRM's status field with a custom status_reason field preserving the original Kula value.

Kula Job records (requisitions) map to Recruit CRM Job records with stage pipeline, assigned team members, and interviewer pool references transferred. Active versus closed status is preserved. Job type, location, and salary range fields map to Recruit CRM's equivalent structured fields. Kula's job-specific custom fields transfer to Recruit CRM job-level custom fields, created during the schema configuration phase before data import.

Kula Application records (linking a Candidate to a Job) map to Recruit CRM's candidate-job association model. Source attribution (direct, referral, sourced-linkedin), submission date, current stage, and any rejection or offer outcome transfer as structured fields on the candidate-job link. Stage progression history is preserved as a series of status-change timestamps on the link record.

Kula Interview records (scheduled rounds, interviewer assignments, and feedback) map to Recruit CRM Interview records. We transfer interviewer names, scheduled date and time, interview type, and reviewer notes. Note that Kula's availability-aware scheduling engine does not have a Recruit CRM equivalent; scheduling rules and interviewer availability settings are destination-dependent and must be reconfigured post-migration. Deleted meetings do not sync back from Google Calendar to Recruit CRM; this is a known limitation documented in Recruit CRM's own community forums.

Kula scorecard templates and submitted evaluations map to Recruit CRM interview evaluation records. We transfer reviewer name, evaluation date, rating values, and reviewer notes as structured text. Scorecard templates themselves (the rating criteria definitions) do not have a direct Recruit CRM equivalent and are documented as a configuration requiring manual rebuild in Recruit CRM's evaluation setup area.

Kula AI-generated interview summaries transfer as static Note records attached to the candidate or interview in Recruit CRM. These are preserved as reference text, not as linked metrics or scores. The original Kula AI score (numeric or tiered) transfers to a custom number field on the candidate record for reporting purposes, but the score does not trigger any Recruit CRM workflow or ranking behavior.

Kula customizable pipeline stages per job are extracted from the source instance. We recreate an equivalent stage configuration in Recruit CRM by creating matching job stages in the order defined in Kula, preserving stage names and probability values where Kula exposes them. Any non-standard stages (stages with custom skip logic or conditional advancement rules) are flagged for manual review because such rules do not transfer.

Both Kula and Recruit CRM support custom fields on Candidates, Jobs, and Applications. We extract the custom field definitions and values from Kula, then map them to Recruit CRM custom fields created during schema configuration. Field types are mapped (Kula text to Recruit CRM text, Kula number to Recruit CRM number, Kula date to Recruit CRM date). Custom fields without a clear Recruit CRM equivalent are flagged and stored as text notes for customer review.

Kula tags applied to candidates (referral, sourced-linkedin, screening-pass, etc.) transfer as tags or custom properties in Recruit CRM. We preserve the tag label and apply it to the corresponding candidate record. Recruit CRM imposes tag name and count limits at certain subscription tiers; we flag any tag that exceeds those limits for customer review and tag consolidation strategy.

Kula recruiter owners, hiring managers, and interviewers map to Recruit CRM User records resolved by email match. We extract every distinct user referenced on Jobs, Applications, Interviews, and Scorecards and match against the Recruit CRM user list. Any Kula user without a matching Recruit CRM account is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Kula interviewer pool membership records transfer as individual interviewer assignments on the relevant job or interview in Recruit CRM. Scheduling rules and availability windows managed in Kula's interviewer pool do not transfer because Recruit CRM lacks an equivalent scheduling-balance feature. The customer's Recruit CRM admin rebuilds interviewer availability settings post-migration.

Kula outreach templates used in automated candidate communication can be exported and mapped to Recruit CRM email templates. Rich formatting and conditional merge field logic may require manual reconstruction in Recruit CRM's template editor. We document the original template structure and flag any templates with complex conditional logic for admin rebuild.