Migrate from Kula to Crelate

Kula Candidate records map directly to Crelate Person records. The Candidate's contact information, work history, sourced profile data, and AI-generated scores migrate as Person fields. We run deduplication by email before inserting, flagging duplicate Person records for admin review. The full candidate activity timeline migrates as Tasks and Activities linked to the Person record.

Kula Job records map to Crelate Job records with pipeline stages and active versus closed status preserved. Stage names and ordering extract from the source instance and are recreated as Crelate pipeline configurations before Job records are imported. We validate stage count against Crelate's Business plan limit of 20 custom recruiting workflows and flag any excess stages requiring consolidation.

Kula Application records link a Candidate to a Job and track stage progression, source attribution, and submission date. These map to Crelate Application records with current stage, rejection or offer outcome, and submission timestamp preserved. We resolve the parent Person and Job references at migration time to satisfy Crelate's required lookups.

Kula Interview records store scheduled rounds, interviewer assignments, and reviewer notes. We map these to Crelate Tasks and Activities with the interviewer assignment, scheduled date/time, and reviewer feedback preserved. The interview sequence (round ordering) is maintained via the Activity date ordering on the parent Person and Job Application records.

Kula generates AI-powered interview summaries and candidate scores as structured fields on the interview record. These import into Crelate as read-only text fields on the Task record and custom fields on the Person record. We preserve the original scores as reference data but flag that live re-scoring requires running Crelate's AI Co-Pilot or a fresh manual evaluation on the destination platform.

Kula's customizable pipeline stages per job extract as stage names, ordering, and probability values. We recreate these as Crelate pipeline stage configurations, mapping stage probability percentages to Crelate's stage probability fields. Non-standard stage types (assessment, background check, offer) may require custom field creation in Crelate to preserve all stage metadata.

Both Kula and Crelate support custom fields on Candidates, Jobs, and Applications. We extract all custom field definitions and values from Kula, then create matching custom fields in Crelate using the Crelate field API before record import begins. Field data types are mapped (text to text, number to number, date to date) and validated during the sandbox migration phase.

Tags applied to candidates in Kula (e.g., referral, sourced-linkedin) carry sourcing context and are preserved as Crelate tags or custom text properties depending on the tag's purpose. Tag limits on Crelate's Business plan (tag count varies by plan) are validated during scoping, and any overflow tags are mapped to custom multi-select fields.

Recruiter owners, hiring managers, and interviewers assigned to Jobs and Applications in Kula are mapped by email to Crelate User records. We run email-based matching against Crelate's User table before migration and flag any Kula owners without a matching Crelate User for admin provisioning. Unresolved assignments are held in a reconciliation queue until the admin completes User provisioning.

Kula outreach templates used in automated candidate communication are documented as a text export with field mapping notes. Rich formatting and conditional logic from Kula templates may require manual reconstruction in Crelate's template builder. We deliver a template inventory document that lists each Kula template, its merge fields, and the recommended Crelate equivalent for the customer's admin to rebuild.

Kula's interviewer pool feature balances scheduling load across team members. Pool membership records migrate as Crelate User assignments to the Job, but scheduling rules and availability settings are destination-dependent and do not carry over. We document the original pool structure so the admin can recreate interviewer availability settings in Crelate's scheduling tool post-migration.

Kula's candidate activity timeline (calls, emails, meetings, notes) maps to Crelate Tasks and Activities linked to the Person record. Call duration, email content, meeting attendee lists, and note body text migrate directly. Activity timestamps preserve ordering so the candidate's engagement history is complete in Crelate's activity feed. Large engagement histories use Crelate's API with batch chunking and rate-limit handling.