Migrate from Recruitee to BambooHR

Recruitee Job records map to BambooHR Job Openings. Job title, department, location, employment type, and description migrate directly. The job status (open, closed, draft, archived) maps to BambooHR's job opening status values. We flag any migration batch exceeding the destination plan's active job post limit (Core 5, Pro 25, Elite 50) and sequence the import into compliant batches, with over-cap jobs queued for a second pass or documented for manual re-creation post-migration.

Recruitee Candidate records (name, email, phone, social profiles, CV/resume) map to BambooHR Application records linked to the corresponding Job Opening. The candidate's source attribution (where they applied from) migrates to BambooHR's application source field. Resume files export from Recruitee's document store and attach to the BambooHR Application via file upload. In BambooHR's data model, candidates who are not yet hired remain as applicants; only hired candidates become Employee records in BambooHR's core HRIS.

Recruitee Application records link a Candidate to a Job with a specific pipeline stage and timestamp. We preserve the candidate-to-job linkage and the application creation date, which is critical for rebuilding pipeline velocity analytics in BambooHR's reporting. Application status (active, rejected, withdrawn, hired) migrates to BambooHR's applicant status values.

Recruitee's customizable pipeline stages per Job require mapping to BambooHR's standardized hiring stages. BambooHR uses a template-based stage model (Applied, Screening, Interview, Offer, Hired, Rejected) that is less granular than Recruitee's per-job pipeline builder. We extract the full stage configuration per pipeline during discovery, map each stage to the closest BambooHR equivalent, and document any stages that cannot be represented natively in BambooHR for the customer's admin to handle as manual workflow steps.

Recruitee Offer records (salary, start date, status, offer letter file) migrate to BambooHR's offer letter templates and employment detail fields on the Application record. Offer status history migrates as a custom text field so offer analytics can be reconstructed. If BambooHR's ATS does not have a native Offers object, we attach the offer letter document to the Application and map structured fields (salary, start date, equity if applicable) to custom Application fields configured before migration.

Recruitee's Talent Pools (organized candidate collections) map to BambooHR's Candidate Talent Pools. Pool membership (candidate ID and pool name) migrates directly. BambooHR supports multiple talent pools per candidate, matching Recruitee's pool model. Pool-level notes and tags attached to the pool itself migrate as structured text notes on the pool record. BambooHR's talent pool feature is included at all ATS-enabled plan tiers.

Recruitee's attribute-level scorecard ratings (for example, 'Technical Skills: Strong Yes' with interviewer and timestamp) do not have a direct native equivalent in BambooHR's ATS. We serialize scorecard data as structured notes on the Application record using a parseable attribute-rating format (field: rating) so historical evaluation data survives migration and can be reviewed by the customer's admin. Scorecard templates can be rebuilt in BambooHR's configuration area post-migration using the documented Recruitee schema.

Recruitee's custom fields on Candidates, Jobs, and Applications require field-level mapping to BambooHR's custom field equivalents. We extract the full custom field list via the Recruitee API, classify each by type (text, number, date, checkbox, dropdown), and map to BambooHR's corresponding custom field types. Name conflicts are resolved with field renaming. Custom fields are configured in BambooHR's application settings before data import begins.

File attachments stored in Recruitee's document store export as binary files and re-upload to BambooHR's Application record, with the original filename and candidate linkage preserved. We use filename and candidate email as the dedupe key when multiple attachments exist per candidate. Portfolio items and portfolio files migrate as standard file attachments on the Application record.

Recruitee User records (name, email, role, department) map to BambooHR User accounts. Role terminology differs: Recruitee's Admin, Recruiter, and Hiring Manager roles map to BambooHR's Full Admin, Employee, or Manager roles depending on the permission level. We resolve users by email match. Any Recruitee user without a matching BambooHR account enters a reconciliation queue for the customer's admin to provision before record import.

Recruitee Departments migrate to BambooHR Departments for organizational consistency. Job-to-department linkages preserve so reporting by department remains accurate after migration. Department names are matched or created in BambooHR before job import to satisfy any department-based lookups.

Notes attached to candidate profiles migrate as structured notes on the BambooHR Application record with timestamp and author attribution. Stage changes, email interactions, and interview events from Recruitee's activity feed migrate as text entries in BambooHR's activity timeline. We preserve chronological ordering by timestamp so the hiring history remains legible. The BambooHR HRIS core activity model differs from Recruitee's engagement model; we map to the closest equivalent.