Migrate from Beehire to Bullhorn ATS & CRM

Beehire Job records map to Bullhorn JobOrder. We extract the job title, description, status (active/archived), multilingual page copy, and job-board distribution metadata from Beehire's UI export. Bullhorn's JobOrder uses a structured status model (Open, Pending, Closed) that maps directly from Beehire's active/inactive job state. If a Starter-tier Beehire account has archived jobs that need their candidate pipelines captured, we reactivate those jobs temporarily in Beehire before extraction (which temporarily consumes a posting slot and may prompt a tier-upgrade notification from Beehire's billing system). Archived jobs without reactivation are not exported under Starter plan limits.

Each Beehire Candidate record (name, email, phone, application date, source channel, current pipeline stage) maps to Bullhorn Candidate. We use Bullhorn's REST API to insert candidates in batches with rate-limit handling and exponential backoff. Bullhorn's Candidate entity supports a large number of standard fields; any Beehire custom candidate properties migrate as Bullhorn custom fields on the Candidate entity (up to the edition limit). We run a dedupe check on email address before insert to prevent duplicate candidate records.

Beehire's customisable pipeline stage names and order map to Bullhorn as Candidate custom label values or a custom pipeline stage field. Bullhorn ATS has a Pipeline field on JobOrder that associates candidates with hiring stages, but the stage names are not as freely customisable as Beehire's. We document the exact Beehire stage sequence during scoping and configure Bullhorn's pipeline accordingly, using custom fields if the stage count exceeds Bullhorn's standard stage set.

Beehire pre-selection questions per job map to Bullhorn as question text stored in a custom field (Bullhorn Candidate) plus the answer value stored against each candidate. The Beehire Compatibility Score (0-100, calculated by Beehire's own algorithm) has no native Bullhorn equivalent and is exported as a custom numeric field compatibilityScore__c alongside the raw questionnaire answers. Bullhorn's own scoring logic is applied by the Bullhorn admin post-migration using Bullhorn Automation or custom fields.

Beehire async video interview questions map to Bullhorn as question text in a custom field. Candidate recorded video responses are Beehire-hosted media URLs that expire when the Beehire account lapses. We download all video files before the source account is decommissioned and re-host them as Bullhorn Candidate file attachments. If the destination Bullhorn environment has Bullhorn Automation, the video questions can be reconfigured there; otherwise the videos are delivered as downloadable files attached to the candidate record.

Beehire Pro-tier custom email templates are exported as HTML with their trigger-condition logic documented. Bullhorn Automation (formerly Herefish) has its own email template format. We do not convert Beehire templates directly; we deliver a written specification of each Beehire template (HTML content, trigger conditions, delay logic, and recipient segment) that the Bullhorn admin uses to re-create the template in Bullhorn Automation. Automated workflows tied to Beehire-specific events (e.g., a Compatibility Score threshold) must be adapted to Bullhorn's trigger model.

Beehire free-form candidate tags map to Bullhorn Candidate Category field or custom multi-select fields. Tags are preserved as label-value pairs per candidate with the full tag history exported. Bullhorn supports category assignment per candidate, and the tag list is delivered as a structured import file for bulk assignment during migration.

Beehire interview records (date, time, interviewer, status) from Pro-tier interview scheduler map to Bullhorn as candidate activity records. If the customer uses Bullhorn's Placement module, interview history can be linked as notes or tasks against the placement record. Bullhorn's calendar integration (Outlook, Gmail) is configured post-migration as a separate admin step; we document the original Beehire interview schedule for the Bullhorn admin to re-establish.

Beehire's multilingual career pages and job offer pages are rendered HTML inside Beehire's page builder and are not exportable as working page files. We extract page copy (text content), logos, and banner images as flat assets. The page layout, styling, and language-switching mechanism remain in Beehire's renderer. The Bullhorn admin rebuilds the career portal page structure in Bullhorn's Career Portal builder or an external CMS; we deliver the content assets in a structured format to accelerate the rebuild.

Each Beehire candidate's application to a specific job maps to Bullhorn JobSubmission. The submission links the Candidate record to the JobOrder record and records the application date, source, and current stage. Bullhorn's JobSubmission object supports status tracking, submission history, and assignment to a recruiter user; we map Beehire's application date and pipeline stage directly to these fields.

Beehire instant messaging threads with candidates (from Beehire's built-in messaging module) are exported as message content with timestamps. These map to Bullhorn Candidate Notes or Activity Tasks. Bullhorn does not have a native threaded messaging model equivalent to Beehire's; we flatten the message history into chronologically ordered notes for readability in Bullhorn.

Beehire users are exported by email address and mapped to Bullhorn User records by email match. Beehire's Starter and Pro plans include unlimited users, but Bullhorn's per-user pricing means the customer must provision Bullhorn User licenses before migration. Owners without a matching Bullhorn User are held in a reconciliation queue for the admin to provision before record import resumes.