Migrate from Beehire to Recruit CRM & ATS

Beehire Job records (title, description, multilingual page copy, status, job-board distribution metadata) map to Recruit CRM Job Order records. We export all published and archived Jobs; Starter-tier accounts limited to 10 active postings require archived roles to be temporarily reactivated before export to capture their candidate pipelines. Job board distribution metadata (board name, posting date, status) exports as structured rows linked to the parent Job.

Beehire Candidate records (name, email, phone, application date, source channel, current pipeline stage) map directly to Recruit CRM Candidate records. The email address serves as the dedupe key during import. Application timestamps migrate as created_date to preserve the chronological pipeline entry record. Candidate Tags from Beehire map to Recruit CRM Tags (free-form labels) with a one-to-one preservation of the per-candidate tag list.

Beehire's fully customisable pipeline (stage names, order, automation triggers per stage) exports as a structured stage list. We reconstruct the pipeline in Recruit CRM using its kanban pipeline builder. Custom stage names and ordering migrate as labelled stages; any Beehire automation triggers referencing a stage are documented in the automation handoff spec rather than migrated as live rules.

Beehire pre-selection questions attached to a Job map to Recruit CRM custom fields on the Candidate or Job Order. Each question becomes a labelled custom field of the appropriate type (text, numeric, or picklist). The candidate's answer populates the field on the Candidate record post-application. We preserve the full question text in a separate lookup table so the Recruit CRM admin can reference the original question wording when reviewing answers.

Beehire's Compatibility Score (0–100, calculated by Beehire's proprietary algorithm against pre-selection questionnaire answers) exports as a custom numeric field on the Candidate record. The raw score migrates as-is. We also export the underlying questionnaire answer set so that Recruit CRM's AI matching can independently evaluate candidates against the same criteria. The Beehire-proprietary algorithm itself cannot be replicated; the score serves as a preserved ranking signal rather than a live calculation.

Beehire async video interview questions per Job export as text records, and candidate video response URLs export as temporary media references. We download all video files before the Beehire account is decommissioned because Beehire URLs expire when the source account lapses. Downloaded video files are re-hosted and linked to the Candidate record in Recruit CRM as external attachments or notes with the question text preserved for context. Recruit CRM does not have a native async video interview module; the video files serve as candidate-provided media artifacts rather than a structured interview workflow.

Pro-tier Beehire automated email workflows and custom email templates do not migrate as functional code. We export the template HTML body, subject line, trigger condition (e.g., 'send 3 days after application if no response'), and any Beehire-specific event references (such as Compatibility Score threshold triggers) as a written automation specification document. The Recruit CRM admin uses this spec to rebuild equivalent rules in Recruit CRM's Business-tier workflow builder. Triggers based on Beehire-specific events require field-level adaptation to Recruit CRM's available trigger conditions.

Beehire interview scheduling records (date, time, interviewer name, interview type, status, calendar link) from Pro-tier accounts export as Recruit CRM interview records or calendar Task entries. Interviewer name maps to the assigned Recruit CRM recruiter. Calendar integration links do not migrate because Beehire's Pro-tier calendar integration is a proprietary connector; we document the original scheduling data so the Recruit CRM admin can configure their own calendar connection (Gmail, Office 365) post-migration.

Beehire personalised multilingual job offer pages and career pages export as flat assets: page copy in each language as structured text, logo files (PNG/SVG), and banner images as standalone files. The page layout, styling, language-switching mechanism, and rendered HTML remain inside Beehire's renderer and cannot be transferred as a working page. We deliver the content assets in a structured format (JSON manifest with file references) so the Recruit CRM admin can repurpose copy and media on a destination careers page or CMS.

Beehire free-form candidate tags migrate to Recruit CRM Tags without transformation. The per-candidate tag list preserves fully. Recruit CRM's tag system uses the same label-based model as Beehire, making this a direct one-to-one mapping with no type conversion required.

The application source channel (job board referral, direct application, referral, etc.) stored on Beehire Candidate records migrates to the Recruit CRM Candidate Source field. If Beehire tracks granular source attribution per job board, we preserve the full attribution string to support Recruit CRM's reporting by source.

Beehire Owner (the recruiter assigned to a Job or Candidate) maps to a Recruit CRM User record resolved by email address match. Any Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before Candidate record import proceeds. The owner assignment on Candidate and Job Order records resolves at migration time once the User lookup table is validated.