Migrate from Beehire to Zoho Recruit

Beehire Job records map to Zoho Recruit Job Opening. The job title, description, requirements, and status (published, archived, draft) migrate directly. Beehire's multilingual job page copy is extracted as structured text fields. Active job count in Zoho Recruit is constrained by plan tier (1 on Free, 10 on Standard per recruiter, 100 on Professional, 750 on Enterprise), so we flag any migration where Beehire active job count exceeds the target Zoho Recruit plan limit and recommend upgrading before migration or archiving roles that are no longer active.

Beehire Candidate records map directly to Zoho Recruit Candidate. We map first name, last name, email address, phone, source channel (Indeed, LinkedIn, direct, etc.), application date, and current pipeline stage. Zoho Recruit's Candidate object is the primary record type for all applicants. Note that Zoho Recruit requires Last Name as a mandatory field; Beehire records without a last name are flagged and imported as 'not provided' per Zoho Recruit's migration requirements.

Beehire's customisable pipeline stages map to Zoho Recruit's Hiring Pipeline stages. We export the full stage list with names, order, and automation trigger conditions from Beehire, then reconstruct the equivalent Zoho Recruit Hiring Pipeline. Stage names and order migrate as-is; Beehire's automation trigger logic (e.g., 'move to Interview stage after questionnaire completed') is documented as a Workflow Rule specification for Zoho Recruit rebuild.

Beehire's proprietary Compatibility Score (0–100, calculated from pre-selection questionnaire answers) has no native equivalent in Zoho Recruit. We export the raw score as a custom numeric field on the Candidate record in Zoho Recruit, along with the underlying questionnaire answer set as multi-select or text custom fields. Zoho Recruit's Professional and Enterprise tiers offer Zia AI matching, which the admin can configure to replicate matching logic against the imported questionnaire data.

Beehire pre-selection questions and answer options migrate as labelled custom fields on the Job Opening or Candidate record in Zoho Recruit. The question text and available answer choices are stored in a structured format. Beehire's Compatibility Score calculation (which weights each question) is documented separately as a written specification so the Zoho Recruit admin can configure equivalent screening criteria using Zoho Recruit's Assessment tools on Professional and Enterprise plans.

Beehire async video interview responses store as temporary media URLs on the candidate record. We download all video files from Beehire before the source account is decommissioned and re-host them as external media links in Zoho Recruit Candidate records (via a URL custom field) or as Note attachments. Note that Zoho Recruit's video interview add-on ($12/license/month) is a separate feature from video migration; the videos migrate as hosted assets rather than native Zoho video interview records.

Beehire's free-form candidate tags migrate to Zoho Recruit Tags, which attach to Candidate records. Tag assignment per candidate is preserved as a one-to-many relationship. Tags that were applied at scale (e.g., 'high-priority', 'revisit', 'referral-source') map directly; Zoho Recruit's tagging system supports multi-tag assignment on Candidate records.

Beehire's multilingual career page and job offer page copy, logos, and banner images export as flat content assets. We store the extracted text (in original languages), logo files, and banner images in Zoho Recruit's Document Library and attach them as notes to the relevant Job Opening record. The page layout, styling, and language-switching mechanism are Beehire-proprietary and cannot be migrated as a working page; the content assets are delivered in structured format to accelerate rebuilding in Zoho Recruit's branded careers site builder (Standard and above).

Beehire Pro-tier custom email templates and the HTML content of automated email workflows are exported as template documents. We deliver a written workflow specification for each Beehire Pro workflow that describes the trigger condition, delay logic, and email content. The Zoho Recruit admin rebuilds the equivalent using Zoho Recruit's Email Templates (5 on Standard, 100 on Professional, unlimited on Enterprise) and Workflow Rules. Automated workflow logic tied to Beehire-specific Compatibility Score thresholds must be adapted to Zoho Recruit's criteria-based Workflow Rules.

Beehire interview records (date, time, interviewer, status, interview type) map to Zoho Recruit Interview records. Beehire Pro's calendar integration metadata (linked to the recruiter's professional calendar) migrates as structured interview scheduling fields; calendar sync itself (Google Calendar, Outlook) is reconfigured post-migration using Zoho Recruit's native integrations on Standard and above.

Beehire's in-app candidate messaging threads (instant messages and automated email logs) are exported as structured conversation records. These migrate to Zoho Recruit as either Comments on the Candidate record or as Email records in the candidate's communication history, depending on thread type. We flag any automated email log entries that were sent by Beehire workflows (Pro-tier) and note them in the workflow specification document.

Beehire stores the original application timestamp, stage-change history, and 'applied via' channel as metadata on the Candidate record. We migrate these as structured custom fields (application_date, previous_stage_timestamps, source_channel) on the Zoho Recruit Candidate record. Stage-change history is preserved as a structured JSON or multi-line text field appended to the candidate profile.