Migrate your Kula data

Candidates is the primary record in Kula, holding contact info, work history, sourced profile data, and AI-generated scores. We migrate candidate profiles with their full activity timeline intact, preserving email/SMS engagement history and AI notes.

Jobs represent open requisitions with associated pipeline stages, team members, and interviewers. We transfer job records with their configured stage pipeline and preserve active vs. closed status during import.

Applications link a Candidate to a Job and track stage progression. We map application records including source, submission date, current stage, and any rejection or offer outcome recorded in the source system.

Interviews store scheduled rounds, interviewer assignments, and评分 feedback. We transfer interview records along with scorecards and reviewer notes, preserving the sequence of interview rounds.

Kula generates AI-powered interview summaries and candidate scores. These are stored as structured fields on the interview record. We preserve AI summaries as text fields; scorecard templates may need field-mapping review depending on the destination's schema.

Kula uses customizable pipeline stages per job. We extract the stage names and ordering from the source instance and recreate an equivalent stage configuration in the destination ATS, flagging any non-standard stage names for manual review.

Both source and destination instances may have custom fields on Candidates, Jobs, or Applications. We extract the custom field definitions and values, then map them to destination fields, creating new ones where no matching field exists.

Tags applied to candidates (e.g., 'referral', 'sourced-linkedin') carry sourcing context. We preserve tag assignments as custom properties or native tags in the destination system, noting any tag limits that apply.

Recruiter owners, hiring managers, and interviewers are assigned to jobs and applications. We map user email addresses between systems and flag any orphaned assignments where the user does not exist in the destination.

Kula includes a branded career site builder with drag-and-drop templates. Career site content, styling, and URL structure are not transferable via API and are excluded from standard migration scope.

Outreach templates used in automated candidate communication can be exported and mapped to the destination's template format, though rich formatting and conditional logic may require manual reconstruction.

Kula's interviewer pool feature balances scheduling load across available team members. We transfer pool membership records but note that scheduling rules and availability settings are destination-dependent and may need reconfiguration.