Migrate from Greenhouse to BambooHR

Greenhouse Candidates are the person record with contact details, social URLs, tags, and custom field values. BambooHR Applicants are flat records tied to a specific job opening. We split Greenhouse's one-to-many Candidate-to-Application relationship by creating one BambooHR Applicant per Application and linking contact fields to the same underlying person record where applicable. Email deduplication across applications is handled by the customer-configured applicant matching rules in BambooHR.

Each Greenhouse Application (a Candidate's candidacy for a specific Job) maps directly to a BambooHR Applicant record. We preserve the application date, rejection or hire status, stage history timestamps, and source attribution. Note that BambooHR does not expose a dedicated Application object in the same way Greenhouse does; the applicant record itself carries the application state.

Greenhouse Jobs (requisition-level records) map to BambooHR Jobs. We preserve job title, department, office location, open/closed status, opening date, and job description. BambooHR does not support job boards, careers page hosting, or job distribution as native ATS features, so any Greenhouse-sourced job board URLs are preserved as a metadata reference list for the customer's team to re-create in BambooHR's job posting tool or external careers page.

Greenhouse's dedicated Offer object stores compensation, start date, equity details, and offer status (pending, accepted, declined, retracted). BambooHR has no formal offer object; offer data must be captured as custom fields on the applicant record or managed manually after the hire is recorded. We migrate offer values as custom fields on the BambooHR Applicant and flag offer status fields that the customer must define in BambooHR's custom field builder before migration.

Greenhouse stores structured scorecard ratings (interviewer, date, question, selected rating, optional free-text notes) as nested objects under Applications. BambooHR has no scorecard or structured evaluation feature. We extract each scorecard rating as a separate custom field on the BambooHR Applicant (scorecard_interviewer_name, scorecard_date, scorecard_rating_value) and document the full scorecard structure in the rebuild inventory. Free-text feedback and evaluation rubric metadata cannot be preserved because BambooHR has no structured notes or form builder for interview feedback.

Greenhouse Interview Kits store structured interview questions and evaluation rubrics scoped to specific jobs. BambooHR has no equivalent feature for defining structured interview questions or rating rubrics per job. We map the kit title and key question themes as custom text fields on the BambooHR Job record and document the full interview kit structure in the rebuild inventory for the customer's team to set up manually in BambooHR's job requirements or custom field builder.

Greenhouse supports custom fields across value types including short_text, long_text, yes_no, single_select, multi_select, currency, number, date, url, and user reference. We map each Greenhouse custom field to an equivalent BambooHR custom field of matching type. Multi-select fields are stored as comma-separated text in BambooHR. Currency fields use BambooHR's currency field type. User reference fields (pointing to Greenhouse users) are stored as the user's name in a text field unless a matching BambooHR employee record exists.

Greenhouse Offices and Departments (flat or tiered hierarchical structures) map to BambooHR Locations and Departments. Exact value matching is required for the integration to function. We validate that all Greenhouse department and office values exist as exact-match values in BambooHR's Location and Department fields before migration. Any values that do not match are flagged for the customer's admin to pre-create in BambooHR or remap to an existing value.

Tags on Greenhouse Candidates and Applications migrate as comma-separated text values in a custom field on the BambooHR Applicant record. BambooHR does not have a native tag or label system for applicant records. We preserve the tag labels and note any tag-to-category mapping the customer has defined in Greenhouse for manual recreation in BambooHR's custom field structure.

Resumes, cover letters, and portfolio files attached to Greenhouse Candidates or Applications migrate as files linked to the corresponding BambooHR Applicant record. We extract files via Greenhouse's Harvest API, handle base64 encoding, and upload to BambooHR's document management via its file upload API. Resume files are associated with the applicant record using BambooHR's document folder structure. Any binary file type not supported by BambooHR's upload API is flagged in the migration report.