Migrate from Beehire to Crelate

Beehire Job records map to Crelate Job records. The job title, description, status (active/archived), and distribution metadata transfer directly. Beehire Starter plan customers with 1-10 active jobs may have archived jobs that were not visible in the UI export; we identify these during discovery and recommend reactivating each archived job temporarily to capture its associated candidate pipeline before migration. The job posting distribution history (which boards received the listing) exports as a custom text field because Crelate manages job board distribution through its own integrations (Indeed, LinkedIn, Monster, Dice, CareerBuilder) at the destination.

Each Beehire Candidate maps to a Crelate Contact record. Name, email, phone, application date, source channel, and current pipeline stage transfer to the corresponding Crelate Contact fields. Beehire's unlimited candidate storage on all tiers means large candidate volumes transfer cleanly to Crelate Business and above, which carries no per-contact storage ceiling on paid plans. Application history (which jobs a candidate applied to) is preserved through Activity records attached to the Contact.

Beehire's custom pipeline stages (stage names, order, and automation triggers defined per pipeline) map to Crelate's Pipeline configuration. We export the pipeline as a structured list of stage names and order positions and configure Crelate Pipelines during the schema design phase. Stage-specific Pro-tier automation triggers (e.g., 'send email when moved to Interview stage') are documented as written trigger-condition specifications rather than migrated as working automation, because Crelate's workflow engine has its own event model.

Beehire's Compatibility Score (0-100, calculated by Beehire's own algorithm from pre-selection questionnaire answers) migrates as a Crelate custom numeric field on Contact named beehire_compatibility_score. The underlying question-answer pairs export as structured custom text fields per question so the destination team can apply their own matching or weighting logic in Crelate's custom field framework. Crelate does not have a native Beehire-equivalent scoring engine; the score is preserved as data, not as functionality.

Beehire async video interview questions and candidate responses are stored as temporary 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 file attachments on the corresponding Crelate Contact records. The question text exports as a custom long-text field on the Contact. Crelate has no native async video interview feature; the team uses the re-hosted video files as reference attachments post-migration.

Beehire Pro-tier custom email templates export as HTML content and are documented with their trigger conditions (e.g., 'send after 3 days if no response') and any Beehire-specific merge fields. The template HTML is delivered as a structured document with field mappings for Crelate's Email Template system. Any trigger condition referencing a Beehire-specific event such as a Compatibility Score threshold must be adapted to Crelate's workflow conditions using the migrated custom field (eehire_compatibility_score) as the trigger field. Beehire Pro automated workflows do not migrate as code.

Beehire free-form candidate tags transfer directly to Crelate's Tag system on Contact records. Tags export with their category context where Beehire uses tag categories; Crelate supports tags with category keys via the Tags object in its API. The full tag list per candidate is preserved to maintain candidate segmentation and sorting after migration.

Beehire Pro interview scheduling records (date, time, interviewer, status, location, candidate) export as Crelate Event records linked to the relevant Contact. Beehire's calendar-integration metadata (calendar provider, meeting link) transfers as custom text fields on the Event. Crelate's Outlook Client Extension and calendar integration handles ongoing scheduling post-migration; the historical interview records are preserved as Event history.

Beehire career page URLs, job offer page copy, logos, and banner images export as flat file assets (text documents and image files). Page layout, styling, and language-switching mechanism are Beehire-specific rendered HTML and cannot transfer as working pages. We deliver the content assets in a structured format for the destination team to rebuild pages on Crelate's Branded Job Portal and custom CSS module, or on a separate CMS.

Beehire application metadata (application date, source channel such as LinkedIn, Indeed, direct, or multipost board) is captured as Crelate Activity Form entries linked to the Contact. Source tracking in Crelate (Candidate Source Tracking feature on Business and above) is populated from this data to preserve recruitment channel analytics.

The Beehire Sourcing Chrome Extension is a Pro-tier browser-based candidate discovery tool that runs against Beehire's own database. It has no exportable data and no equivalent in Crelate's migration scope. We document the extension's functionality (LinkedIn profile import, candidate sourcing into Beehire) and recommend Crelate's native Chrome Extension for LinkedIn sourcing as the post-migration replacement. The team must install the Crelate Chrome Extension and re-authorize LinkedIn sourcing on the destination platform.

Beehire recruiter Owners map to Crelate User records by email address match. Any Beehire Owner without a corresponding Crelate User is held in a reconciliation queue before migration; the customer's Crelate admin provisions the missing User. User provisioning must complete before any record load because OwnerId references are required on Contact, Job, and Opportunity records.