---
title: "Greenhouse to BambooHR Migration: Field Mapping & Rollback"
description: "Migrate Greenhouse to BambooHR with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/hrms/greenhouse/to/bamboohr"
---

# Greenhouse to BambooHR migration

We migrate Candidates, Applications, Jobs, and Offers from Greenhouse into BambooHR with the relational-to-flat schema split handled upfront, document attachments preserved through the BambooHR file API, and every stage, scorecard rating, and custom field mapped to a typed BambooHR field before cutover.

Short answer

FlitStack AI migrates applicants, applications, jobs, custom fields on applicants and custom fields on jobs from Greenhouse to BambooHR, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 1-3 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/hrms/greenhouse/to/bamboohr#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Greenhouse ![](https://flitstack.ai/platforms-trim/greenhouse.webp)

Destination BambooHR ![](https://flitstack.ai/platforms-trim/bamboohr.webp)

Applicant Application Job Custom fields on Applicant Custom fields on Job

Mapped field by field · sample run · one-click rollback

## What moves from Greenhouse to BambooHR?

Moving from Greenhouse to BambooHR is a schema simplification, not a field-for-field copy.

Read the full summary

Greenhouse separates Candidates from Applications with a one-to-many relationship; BambooHR uses a flat applicant record attached to each job opening. We split Greenhouse's relational model into BambooHR's flat structure at migration time, preserving candidate profiles, application history, job data, and compensation fields. Scorecards, interview kits, and Greenhouse's structured hiring workflows do not have a BambooHR equivalent and are delivered as a written rebuild inventory. We use Greenhouse's Harvest API v3 to extract data, transform records through the schema split, and load into BambooHR via its REST API with chunking and error reporting. Active candidates in-flight at migration cutover require a manual export step in the Greenhouse UI, which we plan and document as part of the migration schedule.

1:N split

### Candidate → Applicant

Greenhouse Candidates are the person record with contact details, social URLs, tags, and custom field values.

How it maps

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.

1:1

### Application → Application

Each Greenhouse Application (a Candidate's candidacy for a specific Job) maps directly to a BambooHR Applicant record.

How it maps

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.

1:1

### Job → Job

Greenhouse Jobs (requisition-level records) map to BambooHR Jobs.

How it maps

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.

configuration

### Offer → Custom fields on Applicant

Greenhouse's dedicated Offer object stores compensation, start date, equity details, and offer status (pending, accepted, declined, retracted).

How it maps

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.

configuration

### Scorecard → Custom fields on Applicant

Greenhouse stores structured scorecard ratings (interviewer, date, question, selected rating, optional free-text notes) as nested objects under Applications.

How it maps

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.

configuration

### Interview Kit → Custom fields on Job

Greenhouse Interview Kits store structured interview questions and evaluation rubrics scoped to specific jobs.

How it maps

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.

******What moves 10 objects

Greenhouse BambooHR

- Candidate Applicant split
- Application Application 1:1
- Job Job 1:1
- Offer Custom fields on Applicant transformed
- Scorecard Custom fields on Applicant transformed
- Interview Kit Custom fields on Job transformed

\+ 4 more in the mapping below

## How Greenhouse and BambooHR differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension            | Greenhouse                                                                               | BambooHR                                                                                        |
| -------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Platform type        | Dedicated ATS with structured hiring workflows, scorecards, and interview kits           | HRIS with built-in ATS; recruiting is one module within a unified HR platform                   |
| Candidate schema     | Separate Candidate and Application objects with one-to-many relationship                 | Flat applicant record per job opening; no separate candidate object                             |
| Interview evaluation | Native scorecards tied to interview plans and structured rating rubrics                  | No scorecard or structured evaluation feature; interview feedback handled as free-form notes    |
| Offer management     | Dedicated Offer object with salary, equity, start date, and approval workflow            | No formal offer object; hire date and job title pushed when candidate is marked as hired        |
| Pipeline stages      | Multi-stage pipeline with configurable stage order, questions, and dependent tasks       | Simple hire/reject/withdraw status per applicant with basic pipeline filtering                  |
| Pricing model        | Custom annual contract starting $10K-$15K for mid-market; scales with headcount and tier | Per-employee-per-month ($10-$250/employee) with volume discounts; no annual contract required   |
| Integration model    | Harvest API v3 with OAuth 2.0 and published rate limits                                  | REST API with per-employee monthly rate tiers; one-way sync integration from Greenhouse on hire |

## What to watch for in a Greenhouse to BambooHR migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Department and Location values must exactly match between systems

The Greenhouse-to-BambooHR integration (and our migration) requires exact value matching for Department and Office fields.

How we handle it

If a Greenhouse Department is 'Engineering' and BambooHR's Department field has 'Eng' or 'R\&D', the export or import silently skips that field. We pre-validate all department and office values against BambooHR's configured options before migration and remap any mismatched values to the closest existing BambooHR field value or flag them for the customer's admin to pre-create in BambooHR under Settings > Employee Fields.

high

### Job titles must be pre-created in BambooHR before candidate export

BambooHR only accepts candidate job title values that already exist in the BambooHR job title list.

How we handle it

New job titles must be added under Settings > Employee Fields before any candidate record containing that title is imported. We validate every Greenhouse job title against BambooHR's pre-existing job title list during scoping and create a pre-migration checklist of any new titles the customer must add in BambooHR before the production migration runs. Records with unlisted job titles will be rejected or imported with a blank title field.

high

### Scorecard and interview kit structure has no BambooHR equivalent

Greenhouse's structured scorecards, interview plans, and evaluation rubrics are a core part of its structured hiring philosophy and cannot be mapped to any BambooHR feature.

How we handle it

BambooHR has no form builder for interview questions, no structured rating rubric, and no evaluator feedback collection tied to specific jobs or applications. We extract the scorecard ratings as custom fields on the applicant record, but the evaluation framework, rubric structure, and free-text feedback are not migratable. The customer must rebuild their structured hiring framework in BambooHR's job requirements custom fields or accept a less structured interview process.

medium

### Candidate document extraction requires base64 encoding and API chunking

Greenhouse stores candidate attachments (resumes, cover letters, portfolio files) as binary file objects.

How we handle it

BambooHR's document upload API accepts file content as base64-encoded binary in the request body. We handle the extraction, base64 encoding, and chunked upload for each attachment, but file size limits and encoding overhead can slow migration for candidates with multiple large attachments. We extract attachments in parallel batches and flag any files exceeding BambooHR's upload size limit for manual handling.

medium

### Active candidate migration requires manual export from Greenhouse UI

Greenhouse's documented migration process designates active candidate migration as a manual step performed by the customer's team in the Greenhouse UI, not via API.

How we handle it

Candidates in-flight at migration cutover (not yet marked as hired, rejected, or withdrawn) must be exported from Greenhouse using the bulk candidate export and re-imported manually into BambooHR. We plan the cutover window to minimize the number of active candidates requiring manual handling, export them in a structured format matched to BambooHR's import template, and provide step-by-step instructions for the customer's team to complete the re-import post-go-live.

## How the migration runs

1. ### Discovery and tier validation

   We audit the source Greenhouse account across subscription tier (Core, Plus, Pro), candidate and application record counts, job volume, custom field definitions and value types, scorecard and interview kit presence, attachment count and file size distribution, and any tier-gated objects (bulk candidate import availability, tiered office/department hierarchy).

   What this step covers

   We use Greenhouse's Harvest API v3 to enumerate all records and their field schemas before designing the mapping. The discovery output is a written migration scope and a pre-migration checklist of values that must exist in BambooHR (job titles, departments, locations) before production migration begins.

2. ### BambooHR pre-configuration checklist

   We work with the customer's BambooHR admin to validate and pre-create every value required for exact-match migration: all Greenhouse department values mapped to BambooHR Departments, all Greenhouse office values mapped to BambooHR Locations, all Greenhouse job titles pre-created in BambooHR under Settings > Employee Fields, and all Greenhouse custom field value types defined in BambooHR's custom field builder (text, date, currency, dropdown, multi-select).

   What this step covers

   This step is a hard prerequisite for the production migration because mismatched values result in silent field skips or record rejection.

3. ### Schema design and relational-to-flat transformation

   We design the migration schema to split Greenhouse's Candidate and Application objects into BambooHR's flat applicant model.

   What this step covers

   The transformation includes: one BambooHR applicant record created per Greenhouse Application, contact fields mapped from the parent Greenhouse Candidate, scorecard ratings extracted as custom fields on the applicant, offer values mapped to custom fields on the applicant, and Greenhouse job linked as a reference field on the applicant record. We also define the custom field mapping table for all Greenhouse custom fields by type, noting multi-select collapse strategy and user reference conversion.

4. ### Sandbox migration and reconciliation

   We run a full migration into BambooHR using a test job and test applicant records to validate the field mapping, custom field creation, document attachment upload, and error handling before any production records move.

   What this step covers

   The customer's BambooHR admin reviews the test applicants, validates field content against the Greenhouse source, confirms document readability, and signs off the schema and mapping. Any mapping corrections, custom field type changes, or value mismatches are resolved here.

5. ### Production migration in dependency order

   We run production migration in record order: Jobs first (required for applicant linking), then Applicants (with candidate contact fields, application history, and custom fields), then offer data and scorecard ratings (as custom fields on the applicant record), then candidate documents and attachments (parallel batched uploads with base64 encoding and chunking).

   What this step covers

   Each phase emits a row-count reconciliation report showing records loaded, records skipped, and records requiring manual review. Active candidates in-flight at cutover are exported in a separate structured file for manual re-import by the customer's team.

6. ### Cutover, validation, and rebuild handoff

   We freeze Greenhouse writes at cutover, migrate any records modified during the migration window as a delta pass, then enable BambooHR as the recruiting system of record.

   What this step covers

   We deliver the full rebuild inventory covering: Greenhouse scorecard structure and evaluation rubrics requiring manual rebuild in BambooHR, Greenhouse interview kit themes requiring manual recreation in BambooHR job custom fields, Greenhouse pipeline stage and automation configuration outside migration scope, and a reference list of Greenhouse job board posting URLs for manual re-creation in BambooHR's job posting tool. We provide a one-week hypercare window for data discrepancy resolution.

![](https://flitstack.ai/platforms/greenhouse.svg) Greenhouse ![](https://flitstack.ai/platforms/bamboohr.svg) BambooHR

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · BambooHR Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**1-3 weeks** Typical, smaller accounts

**3-6 weeks** Large or heavily customised accounts

A quote scales with candidate and application record volume, attachment count, and custom field complexity. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Greenhouse to BambooHR →](https://flitstack.ai/contact)

## Why teams move from Greenhouse to BambooHR

- Annual Greenhouse contracts scale steeply with headcount and feature tier, and mid-market teams often find they are paying for structured hiring capabilities they do not use consistently. BambooHR's per-employee-per-month model ($10-$250/employee) with no annual contract requirement and automatic volume discounts is significantly more predictable and cost-effective for teams under 150 employees who do not run panel interviews or structured scorecards at scale.
- BambooHR consolidates HRIS, payroll, benefits administration, onboarding, and applicant tracking into a single platform with a shared employee database. Teams managing separate HRIS and ATS systems pay for two subscriptions and maintain point-to-point integrations. Migrating recruiting to BambooHR eliminates the integration overhead, removes duplicate employee records, and gives HR teams one system to manage for all people operations from hire through retirement.
- Greenhouse's 1-3 month implementation timeline, ongoing scorecard and interview kit configuration, and API-based integration setup demand dedicated HRIS or recruiting operations resources that smaller HR teams do not have. BambooHR is designed for teams without a dedicated administrator, with a UI that non-technical HR staff navigate without formal training or implementation partner engagement.
- Organizations already running BambooHR for HR operations frequently find Greenhouse's ATS redundant once they have configured the mark-as-hired integration that pushes candidate data back to BambooHR. Moving all recruiting into BambooHR simplifies the vendor stack, reduces seat licensing across two platforms, and eliminates the training overhead of managing separate ATS and HRIS workflows for the same hiring team.
- BambooHR's native payroll, time tracking, and benefits administration modules integrate directly with the employee record without middleware or third-party sync tools. Teams migrating from Greenhouse to BambooHR gain a unified system where new hire data flows from the applicant record into payroll and benefits without manual re-entry, which is not possible when ATS and HRIS are separate platforms with point integrations.

Questions, answered

## Greenhouse to BambooHR migration questions

How long does a Greenhouse to BambooHR migration take?

Most migrations land between one and three weeks for accounts under 5,000 candidates with no attachments or scorecard data. Migrations with large attachment libraries (resumes, cover letters, portfolio files), extensive custom fields, or scorecard rating data requiring per-rating field extraction push to three to six weeks because of base64 encoding overhead, custom field type mapping validation, and the BambooHR pre-configuration checklist work. Active candidate migration at cutover adds a separate manual step estimated at one to two days depending on volume.

Do Greenhouse scorecards, interview kits, and structured hiring workflows migrate to BambooHR?

No. BambooHR has no structured interview evaluation feature, no scorecard object, and no interview kit builder. We extract scorecard ratings (interviewer name, date, and selected rating value) as custom fields on the BambooHR applicant record, but the evaluation rubric structure, question definitions, and free-text feedback cannot be preserved. Greenhouse workflows and pipeline automations similarly have no BambooHR equivalent. We deliver a written rebuild inventory documenting every scorecard, interview kit, and workflow requiring manual rebuild in BambooHR's job configuration and hiring settings. The customer's HR team rebuilds these post-migration.

Can we keep our Greenhouse to BambooHR integration running after migration?

The Greenhouse-to-BambooHR integration is a one-way sync from Greenhouse to BambooHR triggered when a candidate is marked as hired. Once recruiting moves entirely to BambooHR, the integration use case (pushing hired candidate data to BambooHR) is replaced by the native BambooHR applicant-to-employee workflow. If the customer retains Greenhouse for any period during a dual-system transition, the integration continues to function for hired candidates, but in-flight applicants and new applications created in BambooHR after go-live will not sync back to Greenhouse.

How do we handle offer letters and compensation data during migration?

Greenhouse's Offer object stores salary, equity, start date, and offer status as structured fields. BambooHR has no formal offer object; offer data must be managed as custom fields on the applicant record or as separate documents. We migrate offer values as custom fields on the BambooHR Applicant and flag any offer status values the customer must define in BambooHR's custom field builder. The actual offer letter document (PDF) migrates as an attachment to the applicant record. Approval workflows configured in Greenhouse for offer routing have no BambooHR equivalent and are documented in the rebuild inventory.

Do we lose historical candidate activity data (notes, emails, calls, meeting logs)?

Greenhouse stores candidate activity as CRM events (calls, emails, notes, meetings) linked to the candidate or application record. BambooHR's applicant record supports free-form notes and document attachments but has no native activity timeline or engagement history object. We migrate available notes as text entries in the BambooHR applicant notes field or as attached documents. Full engagement history (call logs, email threads, meeting records) does not migrate because BambooHR has no equivalent object model. The customer should review Greenhouse reports for historical hiring analytics before go-live.

Why do department and location values need to match exactly between Greenhouse and BambooHR?

Both the Greenhouse-to-BambooHR integration and our migration process require exact value matching for Department and Location fields. If Greenhouse has a department named 'Engineering' and BambooHR's Department field has 'Eng' or 'R\&D', the field is silently skipped during import. We pre-validate all Greenhouse department and office values against BambooHR's configured lists during scoping and either remap mismatched values to existing BambooHR fields or deliver a checklist of new values the customer must pre-create in BambooHR under Settings > Employee Fields before migration.

How do we migrate candidate documents and attachments?

We extract candidate attachments (resumes, cover letters, portfolio files) from Greenhouse via the Harvest API, base64-encode the binary content, and upload to BambooHR's employee document API. Resume files are associated with the applicant record in a dedicated resume folder. We batch the uploads in parallel and chunk large files to handle BambooHR's upload size limits. Any files that exceed BambooHR's size limit or unsupported file type are flagged in the migration report for manual handling. All migrated documents are linked back to the correct BambooHR applicant record before validation begins.

## Related migrations

[![](https://flitstack.ai/platforms-trim/bamboohr.webp) Migrate to **BambooHR** Every source we move into BambooHR, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/hrms/bamboohr) [**Rippling to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/rippling/to/bamboohr) [**Keka to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/keka/to/bamboohr) [**Personio to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/personio/to/bamboohr) [**Workable to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/workable/to/bamboohr) [**Crelate to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/crelate/to/bamboohr) [**Greenhouse to Bullhorn ATS & CRM** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/greenhouse/to/bullhorn)

## Sources: official documentation

1. [Import Tool Training — BambooHR Partners](https://partners.bamboohr.com/reseller-training-resources/import-tool-training/)
2. [Custom Dashboards: Import CSV Data — BambooHR Product Updates](https://www.bamboohr.com/product-updates/custom-dashboards-import-csv-data)
3. [Importing Data into BambooHR — BambooHR Support](https://help.bamboohr.com/hc/en-us/articles/115004527547-Importing-Data-into-BambooHR)
4. [Field Types — BambooHR Documentation](https://documentation.bamboohr.com/docs/field-types)
5. [Add or Update Values for List Fields — BambooHR Documentation](https://documentation.bamboohr.com/reference/metadata-add-or-update-values-for-list-fields)
6. [Sync HRIS Data from BambooHR — Culture Amp Support](https://support.cultureamp.com/en/articles/7048549-sync-hris-data-from-bamboohr)
7. [Customize Your BambooHR Account — BambooHR Help Center](https://help.bamboohr.com/s/article/960685)

Get a quote

## Moving from Greenhouse to BambooHR?

Tell us roughly how many records and objects you have. We scope the mapping and the BambooHR setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
