Migrate from Recruitee to Bullhorn ATS & CRM

Recruitee Job records map to Bullhorn JobOrder. Job title, department, location, status (active/closed/draft), and description migrate directly. Recruitee's department classification maps to Bullhorn's JobCategory or a custom field depending on the destination edition. We flag any jobs exceeding the Recruitee Start plan's 5 active job post cap during scoping and coordinate a second import pass if needed after the customer upgrades. Bullhorn JobOrder has a 100-character limit on several fields including title; we truncate or flag records exceeding this length before import.

Recruitee Candidate records map directly to Bullhorn Candidate. Name, email, phone, social profiles (LinkedIn URL), and source attribution migrate. CV and resume files export from Recruitee's document store and re-upload to Bullhorn as ContentDocument records linked via ContentDocumentLink to the Candidate. Source attribution (referral, job board, direct) migrates to a Bullhorn custom field or the standard source picklist if values match.

Recruitee Application records (linking Candidate to Job with a specific stage and timestamp) map to Bullhorn JobSubmission. The candidate-to-job linkage is preserved by resolving both Bullhorn CandidateID and JobOrderID at migration time. Application creation date and last-modified date migrate as submission timestamps for pipeline velocity analytics. If the Recruitee application has a custom status beyond stage name, we map it to a Bullhorn JobSubmission custom field.

Recruitee's pipeline stages are customizable per Job, meaning the same stage name can exist with different order or criteria across jobs. We extract stage configurations per Recruitee pipeline during discovery, design a corresponding Bullhorn Sales Process for each unique stage sequence, and map Recruitee stage assignments to Bullhorn StageName values during migration. If multiple Recruitee pipelines share the same stage sequence, they share a Bullhorn Sales Process and Record Type. Bullhorn's Sales Process whitelists valid stages per Record Type, enforcing the stage order that Recruitee's per-job pipelines previously defined informally.

Recruitee interview scorecards contain attribute-level ratings (for example, Technical Skills: Strong Yes) attached to a specific interviewer and timestamp. Bullhorn ATS does not have a native scorecard object. We serialize scorecard data as structured Note records with parseable attribute-rating pairs (for example, [Scorecard] Technical Skills: Strong Yes | Interviewer: Jane Smith | Date: 2024-11-15). If the Bullhorn destination has Custom Objects enabled, scorecard attributes can be stored as customObject fields for a more queryable structure, but this requires Bullhorn Support ticket pre-provisioning and adds to migration timeline.

Recruitee Talent Pools (organized candidate collections for future roles) migrate to Bullhorn List records with Candidate membership preserved. Each pool name becomes the List title, and pool membership migrates as ListMember records linking each CandidateID to the List. Pool-level notes and tags attached to the pool itself migrate to Bullhorn Note records linked to the List. Bullhorn Lists are visible across the platform for targeted mailing and search segmentation.

Recruitee Offer records (status, salary details, start date, candidate linkage) map to Bullhorn Placement if the destination org includes the Placement entity (available in Bullhorn Staffing and Agency tiers). If Placement is not in scope, Offers map to Opportunity with a custom record type. Offer status history and salary details migrate to Bullhorn custom fields on the Placement or Opportunity. The offer-to-candidate relationship is preserved by resolving the CandidateID at migration time.

Recruitee custom fields on Candidates, Jobs, and Applications require field-level mapping to Bullhorn's equivalent schema. We extract the full custom field list via Recruitee's API, map each to Bullhorn standard fields (if equivalent exists) or Bullhorn custom fields on the same entity. Bullhorn Custom Objects (customObject1 through customObject10) are used only when Recruitee custom fields exceed the standard Bullhorn field limit for an entity. Bullhorn Support must provision Custom Objects via ticket before API access; we coordinate this during the schema design phase and include the provisioning timeline in our project schedule.

File attachments (resumes, cover letters, portfolio items) stored in Recruitee's document store export as binary files with filename and candidate ID metadata. We re-upload to Bullhorn as ContentDocument records and link to the corresponding Candidate via ContentDocumentLink. Bullhorn's resume parsing triggers on ContentDocument upload if enabled in the destination org settings. Original file names and MIME types are preserved for traceability.

Recruitee workflow automations (triggers, conditions, actions) are platform-native constructs that cannot be extracted via the API. We document every active automation during discovery: trigger type, conditions, actions, and affected records. This inventory is delivered as a written document with each automation mapped to a recommended Bullhorn equivalent (Bullhorn Workflows if licensed, or Salesforce Flow built by the customer's admin). Workflow rebuild is outside migration scope.

Recruitee User records (name, email, role, department assignment) map to Bullhorn User. Admin, Recruiter, and Hiring Manager roles in Recruitee map to Bullhorn userType values. We resolve users by email match during migration. Any Recruitee user without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Recruitee Departments (organizational units classifying jobs and team members) map to Bullhorn Department records. The job-to-department linkage migrates so that reporting by department is consistent after cutover. Bullhorn Department is used in conjunction with userType to control data visibility and access permissions in the destination org.

Recruitee Notes (free-text entries attached to candidate profiles) migrate to Bullhorn Note records linked via ContentDocumentLink to the Candidate. Activity history including stage changes, emails sent, and interview events migrate as Bullhorn Task records with appropriate TaskSubtype values. Timestamps and author attribution are preserved from the Recruitee activity record. Email content from Recruitee activity records migrates to Bullhorn Note with a [Email] prefix for parsing by the customer's team.

CareersHub is Recruitee's branded career site builder storing page content, job board configurations, and domain settings in a schema separate from Jobs and Candidates. This data does not live in the Recruitee API alongside core recruitment records. We export CareersHub content as a structured archive document and deliver it to the customer for manual republishing to Bullhorn Career Portal or an external CMS. CareersHub domain settings (DNS records, branded subdomain) require manual reconfiguration in the customer's DNS provider.