Migrate from JOIN to BambooHR

JOIN Jobs (title, description, department, location, employment type, posting status) map to BambooHR ATS Job postings if the customer activates BambooHR's optional ATS module. If BambooHR ATS is not active, Jobs map to a structured Department plus a custom Position field that captures employment type and location metadata. We extract the full job record during scan, identify which Jobs are still open versus archived, and configure the destination accordingly during scoping. OPEN jobs migrate first; closed jobs migrate as historical reference records.

JOIN Candidate records (contact info, work history, education, skills tags, source attribution, custom fields) map to BambooHR Employee records or BambooHR ATS Applicants depending on whether the candidate was hired. Hired Candidates become BambooHR Employees with employment start date populated from the JOIN offer or hire-stage date. Unhired candidates who need to be preserved become BambooHR ATS Applicants linked to the corresponding Job. We resolve the hired-versus-not-hired flag from the JOIN pipeline stage (Offer, Rejected, or Application status fields) before import.

JOIN Applications (Candidate-to-Job join record with applied date, referral source, status) map to BambooHR ATS Application records if the customer uses BambooHR ATS, or to Employment History entries on the BambooHR Employee record if the candidate was hired. Applied date migrates as hire application date; referral source migrates as a custom Employee field. Status mapping uses the JOIN stage name (Applied, Screening, Interview, Offer, Rejected) to set the corresponding BambooHR ATS status or Employment status field.

JOIN stage sequences (which vary per Job and per plan) migrate as metadata attached to the Job or Employee record rather than as native stage gates, because BambooHR's ATS module does not enforce a custom stage pipeline the way JOIN does. We preserve the full stage-entry date sequence as a custom field group (stage_1_entry_date, stage_2_entry_date, etc.) so that timing context is not lost. Where the destination is BambooHR without ATS, stage history lands as a free-text notes block on the Employee record.

Structured interview scorecards and free-text evaluation notes migrate as a custom Employee field (long-text type) or as a linked Document record in BambooHR's document storage, depending on the scorecard complexity. Rubric-based scorecards with numeric ratings are flattened into text format (Interviewer, Rating, Comments per criterion) and preserved in reading order. The destination format is agreed during scoping.

JOIN Candidate custom fields (employer-defined, no standardised schema) map to BambooHR Employee custom fields created via BambooHR's Custom Field Builder (available from Essentials plan). We extract the full JOIN custom field schema during scan, surface each field at scoping, and the customer confirms the intended BambooHR equivalent (text, number, date, dropdown, checkbox). Fields with no clear BambooHR equivalent land as free-text custom properties and can be restructured post-migration. JOIN custom fields on Jobs map to Job (ATS) custom fields or Department metadata.

Candidate resume files export from JOIN and upload to BambooHR as Employee Documents with the Document Type set to Resume. JOIN returns files with non-standard filenames derived from internal IDs; we rename to the convention CandidateName_Position_ApplicationDate before ingestion to prevent filename collisions in bulk uploads and ensure files are identifiable in BambooHR's document list. Supporting documents (portfolios, cover letters) migrate as separate Document records with appropriate type labels.

JOIN Owners (recruiters, hiring managers) referenced on Candidates and Applications map to BambooHR Employees who correspond to the same individuals. We match by email address. Any JOIN Owner without a matching BambooHR Employee record is held in a reconciliation queue for the customer's admin to provision the corresponding Employee record before migration continues, because BambooHR Employee is a required parent for document and document-type assignments on records.

JOIN's internal email threads, scheduled interview events, and activity log entries cannot migrate because JOIN does not expose a documented bulk export endpoint for activity data. We flag this gap at scoping, instruct the customer on the manual CSV export path from the JOIN dashboard, and ingest that CSV as a reference document attached to the Employee or ATS Applicant record. Email templates from JOIN's communication tools are inventoried separately as a text handoff for the customer to rebuild in BambooHR's email template system.

JOIN's job board distribution configuration (which of the 250+ boards each Job is posted to, posting dates, and status) has no direct BambooHR equivalent. BambooHR ATS supports a limited built-in job board and optional paid job board integrations but does not replicate JOIN's multi-board distribution model. We deliver a written inventory of each JOIN Job's distribution list as a handoff document for the customer's admin to recreate manually or through a third-party job aggregator.