Migrate from Kula to Bullhorn ATS & CRM

Kula's unified Candidate record maps to Bullhorn's Lead and Contact based on recruitment stage. Candidates who have been sourced but not submitted to a client map to Bullhorn Lead. Candidates who have been submitted to a client or have an active application map to Bullhorn Contact attached to a Business (client company). We preserve the original Kula candidate ID as a custom field bh_kula_candidate_id__c on both Lead and Contact for audit traceability.

Kula Job records map directly to Bullhorn JobOrder. The job title, description, location, employment type, and salary fields transfer to equivalent Bullhorn JobOrder fields. We extract the Kula job status (Open, Closed, Draft, On Hold) and map to Bullhorn status (Open, Closed, Cancelled). The Kula job owner maps to the Bullhorn JobOwner by email resolution.

Kula Application records link a Candidate to a Job and track stage progression. We map Application records to Bullhorn JobSubmission for candidates in interview or offer stages. For placements that have been made in Kula, we map to Bullhorn Placement with the appropriate employment and billing details. The application submission date, current stage, and rejection or withdrawal outcome transfer as structured fields.

Kula Interview records (scheduled rounds, interviewer assignments, and feedback) map directly to Bullhorn Interview records. We transfer interviewer assignments by resolving Kula user email addresses to Bullhorn User records. Interview date, time, type (phone, video, onsite), and outcome (passed, failed, no-show) migrate as structured fields. The sequence of interview rounds is preserved by ordering on the interview start timestamp.

Kula generates AI-powered interview summaries and candidate scores stored as structured text fields on the interview record. We migrate these as read-only text fields in Bullhorn. Bullhorn does not have a native AI scoring equivalent, so we preserve the original Kula AI summary as a long-text custom field interview_notes__c on the Interview record and flag for the customer's admin that manual or third-party AI re-scoring is required post-migration. Scorecard templates from Kula are documented for rebuild in Bullhorn's custom form builder.

Kula's customizable per-job pipeline stages (e.g., Applied, Phone Screen, Technical, Final, Offer) map to Bullhorn's six-step standard hiring workflow or to custom workflow stages if the customer's Bullhorn instance has custom workflow configuration enabled. We extract the Kula stage names and ordering from each job's pipeline, then configure matching workflow stages in Bullhorn JobOrder before migration. Stage probabilities from Kula transfer to Bullhorn's custom probability fields if configured.

Kula preserves a full candidate activity timeline (sourcing events, outreach, status changes, interview rounds, feedback). We migrate activity records to Bullhorn Note records attached to the candidate's corresponding Lead or Contact. Activity type, timestamp, and description transfer as structured fields. We preserve the activity sequence by ordering on the original Kula timestamp to maintain the timeline view in Bullhorn.

Kula custom fields on Candidates (beyond the standard profile fields) migrate to Bullhorn custom fields on Lead and Contact. We pre-create the destination schema in Bullhorn with matching field types (text, number, date, picklist, multi-select picklist) before migration. Custom field definitions are extracted from Kula during discovery and mapped one-to-one with type conversion applied where field types differ between platforms.

Kula custom fields on Job records migrate to Bullhorn JobOrder custom fields. Bullhorn JobOrder supports custom fields for additional job attributes (e.g., department code, hiring manager name, security clearance requirements). We extract the custom field schema from Kula, create matching Bullhorn fields, and migrate values during the JobOrder import phase.

Kula tags (e.g., 'referral', 'sourced-linkedin', 'passive-candidate') carry sourcing and classification context. We preserve tag assignments as Bullhorn multi-select picklist values on the candidate record. The original Kula source attribution (where the candidate was sourced) maps to Bullhorn's CandidateSource field on Lead or Contact. Tag limits in Bullhorn (maximum 500 values per picklist) are checked during discovery.

Recruiter owners, hiring managers, and interviewers assigned to Kula Jobs and Applications are mapped by email address to Bullhorn User records. We extract every distinct user email from Kula assignments and match against the Bullhorn destination org's User table. Any Kula user without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Kula's interviewer pool feature (balancing scheduling load across team members) maps to Bullhorn's Candidate Pool feature for talent pools or User group assignments for interviewer management. We transfer pool membership records with the caveat that Bullhorn's scheduling rules and availability settings are destination-specific and require manual configuration post-migration.

Kula outreach templates used in automated candidate communication can be exported as text and mapped to Bullhorn Email Templates or Bullhorn Automation (Herefish) sequences. Rich formatting and conditional logic from Kula templates may require manual reconstruction in Bullhorn's template editor. We deliver a template mapping document listing each Kula template and its recommended Bullhorn equivalent.

Kula's integrated sourcing from LinkedIn and GitHub stores profile URLs, connection counts, and skill data on the candidate record. We migrate these as custom fields on the Bullhorn Lead or Contact: linkedin_url__c, github_url__c, and skill tags mapped to a multi-select picklist. Bullhorn does not have native LinkedIn or GitHub sourcing integration, so these fields are preserved as reference data rather than live links.