Migrate from Beehire to BambooHR

Beehire Job records map to BambooHR Job Postings with title, description, employment type, and location preserved. Job status (active, paused, archived) migrates as BambooHR job status. Beehire's multilingual page copy and job-board distribution metadata export as structured text files; the layout and styling remain Beehire-specific and must be rebuilt on the destination careers site. If the source account is on Starter (1-10 active jobs), we flag any archived or inactive jobs and advise whether to reactivate them before export to capture their candidate pipelines.

Beehire Candidate records map directly to BambooHR Applicant records. Core fields (name, email, phone, application date, source channel) migrate as standard BambooHR fields. Beehire's custom Candidate fields (including Compatibility Score and tag-based labels) migrate as custom Applicant fields created in BambooHR before migration. Candidate records are imported after Job Postings so that the job_reference lookup is satisfied at the moment of Applicant insert.

Beehire's customisable pipeline stages (stage name, order, automation triggers) export as a structured stage list and are reconstructed in BambooHR's Hiring pipeline configuration. Stage ordering and any stage-gated automation triggers export as a written specification; BambooHR's stage automation is separate and must be rebuilt. Custom stage names that use Beehire-specific terminology are preserved as-is in BambooHR stage labels.

Beehire's proprietary Compatibility Score (0-100) calculated from pre-selection questionnaire answers migrates as a custom numeric field on the BambooHR Applicant record. The raw questionnaire answer data exports separately as a structured JSON or CSV file attached to the applicant for audit. BambooHR does not have a native compatibility-scoring engine; the customer's admin can use the exported questionnaire data to build a BambooHR custom formula or third-party integration for ongoing candidate ranking.

Question text and answer options export as structured data. Question answers attached to Candidate records migrate as custom Applicant fields. If the questionnaire structure is reusable, we document the form schema so the customer's BambooHR admin can rebuild it using BambooHR's application form builder. Questions with Beehire-specific scoring logic are flagged as requiring manual adaptation in BambooHR.

Async video interview questions (question text) and candidate response URLs export as structured metadata. Video files download from Beehire's temporary media URLs before account decommissioning and are re-hosted as file attachments on the corresponding BambooHR Applicant record. Video response media URLs expire when Beehire accounts lapse; we execute media download before the source account is closed. BambooHR does not have native async video interviewing; the customer's team uses BambooHR's built-in calendar scheduling for live interviews instead.

Beehire free-form tags applied to Candidates migrate as BambooHR Tags on the Applicant record. Tags are a native BambooHR Applicant feature and map cleanly without transformation. The tag taxonomy is preserved exactly as it appears in Beehire.

Pro-tier email templates export as HTML with the trigger-condition logic documented in a written automation inventory. Template HTML is delivered as a file package; the customer's BambooHR admin rebuilds the template in BambooHR's email template editor. Any Beehire-specific merge field syntax is translated to BambooHR's equivalent variable syntax. Workflow triggers (e.g., send after 3 days if no response) document as a recommended BambooHR Workflow configuration specification for the admin to implement.

Interview records (date, time, interviewer, status) export from Beehire as scheduling objects. They migrate as calendar event metadata (date, time, interviewer name, status) attached to the corresponding BambooHR Applicant record. Beehire's calendar integration (Google Calendar or Outlook) is Beehire-specific; BambooHR's scheduling relies on BambooHR's own calendar integration and does not import historical calendar sync data.

Multilingual job offer pages and career page copy, logos, and banner images export as flat files (text, PNG, JPEG). Page layout, styling, and language-switching mechanism are Beehire-rendered and not migratable as working pages. We deliver the content assets in a structured format (copy as text files, images as named assets with metadata) so the customer's web team can rebuild the careers site on their own CMS. This is a content handoff, not a page migration.