---
title: "Greenhouse to Bullhorn ATS & CRM Migration | FlitStack AI"
description: "Migrate Greenhouse to Bullhorn ATS & CRM 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/bullhorn"
---

# Greenhouse to Bullhorn ATS & CRM migration

We migrate Candidates, Applications, Jobs, Scorecards, and Offers from Greenhouse into Bullhorn ATS with scorecard ratings preserved through custom fields, the Candidate-to-Contact-and-Lead model split resolved during scoping, and every Greenhouse custom field mapped to a Bullhorn-typed equivalent before cutover.

Short answer

FlitStack AI migrates candidates, jobsubmissions, joborders, custom fields and users from Greenhouse to Bullhorn ATS & CRM, 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: 4-6 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/bullhorn#what-moves)

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

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

Destination Bullhorn ATS & CRM ![](https://flitstack.ai/platforms-trim/bullhorn.webp)

Candidate JobSubmission JobOrder Custom Fields User

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

## What moves from Greenhouse to Bullhorn ATS & CRM?

Moving from Greenhouse to Bullhorn is a shift from an in-house structured-hiring ATS to a staffing-agency CRM-first ATS platform.

Read the full summary

Greenhouse organizes hiring around structured interview scorecards, job requisitions, and pipeline stages; Bullhorn organizes around Candidates, Clients, JobOrders, and Placements with a built-in CRM for candidate and client relationship tracking. The most significant schema difference is that Greenhouse's interview scorecards are first-class nested objects, while Bullhorn has no native scorecard entity — we migrate scorecard ratings and interviewer feedback into Bullhorn custom fields on the Candidate or JobSubmission record. We preserve every Candidate, Application, Job, Offer, and custom field value through Bullhorn's REST API with batch chunking, and we handle the multi-week parallel-run window that Greenhouse's documented historical migration process requires.

1:1

### Candidate → Candidate

Greenhouse Candidate records map to Bullhorn Candidate.

How it maps

We preserve all standard fields (firstName, lastName, email, phone, social URLs) and custom field values across Greenhouse value types (single\_select, multi\_select, currency, date, user reference). Phone number formatting is normalized to E.164 before insert. Tags migrate as Bullhorn Tags. Active candidate records require manual export from Greenhouse for bulk import if the customer is on Core tier; Plus and Pro customers can use the Greenhouse bulk import method guided by our exported CSV template.

1:1

### Application → JobSubmission

Greenhouse Application records (linking Candidate to Job) map to Bullhorn JobSubmission.

How it maps

We preserve application date, rejection or hire status, current stage, and all stage history timestamps. Rejection reasons migrate to a custom field on JobSubmission. The migration of interviewer feedback and notes requires a separate decision: either entered in the bulk import spreadsheet at import time or added manually post-import; Greenhouse's documentation states this is a customer-performed step.

1:1

### Job → JobOrder

Greenhouse Job records map to Bullhorn JobOrder.

How it maps

We preserve job title, department, office location, open/closed status, opening date, and job description. Job posting URLs migrate as reference links rather than republished postings. Bullhorn JobOrder has a different stage model from Greenhouse: Greenhouse stages are application-stage steps while Bullhorn stages track placement workflow. We map Greenhouse stages to Bullhorn JobOrder status values and document any unaligned stage names for the customer's Bullhorn admin to configure post-migration.

configuration

### Scorecard → Custom Fields (Candidate or JobSubmission)

Greenhouse scorecards are nested objects under Applications containing structured evaluator ratings and interview kit questions.

How it maps

Bullhorn has no native scorecard entity. We flatten each scorecard into named custom fields on the Candidate or JobSubmission record: one field per rating (e.g., technical\_skills\_rating, communication\_rating) and one field for overall recommendation. We use Bullhorn's custom field API (customObject1s through customObject10s or custom fields on Candidate) based on the customer's Bullhorn edition. The interview kit structure (questions, rubric, scoring scale) is preserved as a JSON blob in a long-text custom field for admin reference. Scorecard migration requires Bullhorn Support to create any custom fields beyond standard Candidate fields.

configuration

### Offer → Custom Fields (JobSubmission)

Greenhouse Offers store compensation packages attached to an Application: start date, salary, equity, and custom offer fields.

How it maps

Bullhorn has no native offer entity for the ATS tier; offers are tracked through custom fields or, in Bullhorn Growth/Enterprise, through custom objects. We migrate start date, base salary, equity values, and custom offer fields into Bullhorn custom fields on JobSubmission. Bullhorn Support must create these custom fields before migration. Offer status (pending, accepted, declined, retracted) migrates as a picklist field.

lookup

### User / Hiring Team → User

Greenhouse Users (recruiters, hiring managers, admins) map to Bullhorn User records.

How it maps

We resolve owners by email match against the Bullhorn destination org. Users without a matching Bullhorn User go to a reconciliation queue for the customer's Bullhorn admin to provision. Role and permission mapping (Greenhouse permission levels to Bullhorn role-based security) is documented in the migration scope but not enforced programmatically.

******What moves 12 objects

Greenhouse Bullhorn ATS & CRM

- Candidate Candidate 1:1
- Application JobSubmission 1:1
- Job JobOrder 1:1
- Scorecard Custom Fields transformed
- Offer Custom Fields transformed
- User User transformed

\+ 6 more in the mapping below

## How Greenhouse and Bullhorn ATS & CRM 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                                                                          | Bullhorn ATS & CRM                                                                              |
| -------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Core orientation     | Structured hiring ATS for in-house recruiting teams with scorecard-first evaluation | Staffing-agency CRM-first ATS with candidate, client, and placement tracking                    |
| Interview scorecards | First-class nested objects under Applications with structured ratings               | No native scorecard entity; ratings migrate to custom fields on Candidate or JobSubmission      |
| CRM capability       | Basic CRM events (single type in Core; unlimited in Plus/Pro)                       | Built-in Candidate CRM with client corporations, opportunities, and placement tracking          |
| Onboarding module    | No native onboarding; Greenhouse relies on integrations                             | Integrated onboarding module for managing new hire info, dates, and tasks                       |
| Pipeline model       | Jobs with configurable stages and stage-specific scorecards                         | JobOrders with stages plus Placements tracking placed candidates                                |
| Custom objects       | Custom fields across all value types from Core upward                               | Custom Objects (customObject1s-10s) gated by edition: ATS Growth 0, ATS 2, Growth/Enterprise 10 |
| Pricing model        | Custom annual, tier-gated (Core/Plus/Pro), add-ons increase TCO                     | Per-user monthly ($99-$315/user/mo) with separate add-ons for automation and analytics          |

## What to watch for in a Greenhouse to Bullhorn ATS & CRM migration

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

high

### Bullhorn custom fields require Bullhorn Support to create

Bullhorn's standard REST API exposes customObject1s through customObject10s on Candidate, ClientContact, ClientCorporation, JobOrder, Opportunity, and Placement, but these objects must be initially set up by Bullhorn Support using a Custom Object Setup Spreadsheet.

How we handle it

Unlike Greenhouse's self-service custom field creation (available from Core tier), Bullhorn requires a support ticket and administrative setup before any migration can write to custom fields. We coordinate with the customer's Bullhorn admin to submit the custom object setup request early in the migration timeline, as Bullhorn Support turnaround can add 5-10 business days to the project schedule.

high

### Greenhouse's 4-6 week historical data migration runs concurrently

Greenhouse's documented historical data migration process takes 4-6 weeks from data handoff to completion, during which the customer continues using their old ATS for new candidates while Greenhouse processes the historical records.

How we handle it

For the Greenhouse-to-Bullhorn migration, this means the customer may be running Bullhorn (for new hires) alongside Greenhouse (for historical data processing) during that window. We coordinate the data export timing with this window to avoid gaps. Any candidate records created during the migration window must be captured separately as part of the active candidate migration step, which Greenhouse's documentation states is a manual customer-performed process.

medium

### Scorecards have no native Bullhorn equivalent

Greenhouse interview scorecards are structured evaluator feedback records with questions, ratings, and recommendations stored as nested objects under Applications.

How we handle it

Bullhorn has no scorecard entity; scorecard data must be flattened into custom fields on Candidate or JobSubmission. This transformation requires Bullhorn Support to pre-create the custom fields (which are gated by Bullhorn edition: 0 on ATS Growth, 2 on Bullhorn ATS, 10 on Growth/Enterprise), and the flattened structure loses some Greenhouse-native context such as per-interviewer breakdown versus aggregated scores. We document the scorecard structure in our migration scope and advise customers on the best flattening strategy based on their evaluation rubric.

medium

### Bullhorn edition limits constrain custom object availability

Bullhorn's edition-based custom object limits directly affect migration scope.

How we handle it

ATS Growth tier supports zero custom objects, meaning scorecard ratings, offer details, and any custom Greenhouse fields must either be discarded, mapped to standard Bullhorn fields where available, or the customer must upgrade to Bullhorn ATS (2 custom objects), Growth, or Enterprise (10 custom objects each with 55 fields per object) before migration. We validate the customer's Bullhorn edition at scoping and flag this as a migration-blocking constraint if the edition does not support the customer's required custom field count.

medium

### Greenhouse Plus/Pro bulk import restriction affects active candidate migration

Greenhouse's bulk candidate import feature — the guided CSV-based import method — is gated to Plus and Pro subscription tiers.

How we handle it

Core customers must perform active candidate migration manually, one record at a time, which is impractical for organizations with hundreds or thousands of in-flight candidates. We validate the customer's Greenhouse tier during scoping and, for Core customers, recommend an alternative approach: we export all active candidates and their associated application history in a structured CSV format, and the customer uses Greenhouse's bulk import spreadsheet (which they can access manually even on Core) with our export as the source. This requires customer action and is documented in our migration scope as an out-of-scope manual step.

## How the migration runs

1. ### Discovery and edition validation

   We audit the source Greenhouse portal across tier (Core/Plus/Pro), active job count, candidate volume, application history depth, custom field count and value types, scorecard and interview kit configurations, office/department hierarchy, and offer field structure.

   What this step covers

   We pair this with Bullhorn edition validation: confirming the customer's Bullhorn tier, reviewing existing custom object configuration (if any), and identifying which custom objects Bullhorn Support must create before migration. The discovery output is a written migration scope document with object counts, custom field inventory, and Bullhorn edition gap analysis.

2. ### Scorecard and custom field schema design

   We design the destination schema in Bullhorn for all custom fields that cannot map to standard Bullhorn entities.

   What this step covers

   This includes identifying the correct Bullhorn entity for each Greenhouse scorecard rating field (Candidate vs JobSubmission), mapping Greenhouse custom field value types to Bullhorn field types (single\_select to picklist, multi\_select to multi-select picklist, currency to currency field), and submitting the Bullhorn Custom Object Setup Spreadsheet to Bullhorn Support for any custom object creation. Bullhorn Support turnaround is typically 5-10 business days and must complete before any migration data writes to custom fields.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Bullhorn sandbox environment using production-like data volume.

   What this step covers

   The customer's Bullhorn admin reconciles record counts (Candidates in, Applications in, Jobs in, Scorecards in), spot-checks 25-50 random candidate records against Greenhouse source, and validates scorecard field population in Bullhorn. Any custom field mapping corrections, stage mapping issues, or attachment failures are resolved in sandbox before production migration begins. Scorecard transformation is validated here by comparing Greenhouse scorecard ratings against Bullhorn custom field values.

4. ### Owner and user reconciliation

   We extract every distinct Greenhouse User (recruiter, hiring manager) referenced on Candidate, Application, Job, and Offer records and match by email against Bullhorn User records.

   What this step covers

   Users without a matching Bullhorn User are held in a reconciliation queue for the customer's Bullhorn admin to provision. Bullhorn role-based security is documented for each mapped user but is not enforced programmatically during migration; the customer's admin configures Bullhorn permissions post-migration.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Bullhorn Users (validated, not created by migration), JobOrders (from Greenhouse Jobs), Candidates (with tags, custom fields, and source attribution), JobSubmissions (linked to Candidate and JobOrder with stage history), custom field data (scorecards, offers) on Candidate or JobSubmission, attachments (resumes, cover letters), and custom objects (after Bullhorn Support has confirmed setup).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. The Greenhouse historical migration runs concurrently; we coordinate the cutover date to capture any records created during the 4-6 week window.

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

   We freeze Greenhouse writes at cutover and run a final delta migration of any Greenhouse records created or modified during the migration window, including any active candidate records the customer imported via bulk import.

   What this step covers

   We enable Bullhorn as the system of record and deliver the scorecard transformation documentation, workflow inventory, and automation rebuild guide to the customer's Bullhorn admin. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Greenhouse interview kits, scorecard templates, or automations as Bullhorn configurations; those are documented for the customer's admin to rebuild.

![](https://flitstack.ai/platforms/greenhouse.svg) Greenhouse ![](https://flitstack.ai/platforms/bullhorn.svg) Bullhorn ATS & CRM

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 · Bullhorn ATS & CRM 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

**4-6 weeks** Typical, smaller accounts

**10-14 weeks** Large or heavily customised accounts

A quote scales with record volume, scorecard complexity, and Bullhorn edition selection. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Greenhouse to Bullhorn ATS & CRM →](https://flitstack.ai/contact)

## Why teams move from Greenhouse to Bullhorn ATS & CRM

- Greenhouse was built for in-house tech and startup recruiting teams, not staffing agencies. Reviews cite repetitive manual workflows, limited CRM-style candidate nurture, and poor tools for proactive outreach and client relationship tracking. Bullhorn's CRM-first architecture natively supports candidate and client records, placement tracking, and business development workflows that agency recruiters depend on, reducing the need for workarounds or third-party integrations.
- Greenhouse's offer currency defaults to USD, requiring manual correction for requisitions in the UK, India, and other non-US markets — a gap with no platform-level fix. Reviewers on Reddit and G2 note this creates a human-error risk on offer letters. Bullhorn supports multi-currency configuration at the org level without per-record manual overrides.
- Staffing agencies cite Bullhorn's integrated onboarding module as a time-saver for managing new hire information, onboarding dates, and associated tasks without switching platforms. Greenhouse does not offer a native onboarding module, requiring agencies to rely on third-party tools or manual processes to manage the post-placement workflow.
- Greenhouse's Business Intelligence Connector, AI-powered filters, sourcing automation, and advanced analytics are Plus and Pro add-ons that significantly increase total cost of ownership for mid-market teams. Bullhorn Analytics (Canvas) and Bullhorn Automation are separately priced but available within a unified platform without requiring a tier upgrade for core ATS and CRM functionality.
- Greenhouse's reporting requires manual interpretation in Core tier and custom report building. Bullhorn's reporting, while also requiring configuration, is positioned toward agency KPIs (placements, billable hours, client revenue) rather than structured hiring process metrics, which better matches how staffing firms measure success.

Questions, answered

## Greenhouse to Bullhorn ATS & CRM migration questions

How long does a Greenhouse to Bullhorn migration take?

Most migrations land between four and six weeks for accounts under 10,000 Candidates, 500 Jobs, and no complex custom object requirements. Migrations with complex scorecard transformations, large application histories (over 50,000 Application records), multi-office Greenhouse structures requiring department remapping, or Bullhorn Growth/Enterprise tier with custom objects move to ten to fourteen weeks. The Greenhouse historical data migration window (4-6 weeks per Greenhouse's documentation) runs concurrently and extends the effective parallel-run period, so customers should plan for ongoing dual-system usage during that window.

Do Greenhouse interview scorecards migrate to Bullhorn?

Greenhouse scorecards do not have a native Bullhorn equivalent and must be transformed into custom fields. We flatten each scorecard into named custom fields on the Bullhorn Candidate or JobSubmission record (one field per rating dimension plus overall recommendation). The interview kit structure and rubric are preserved as a JSON blob in a long-text custom field for admin reference. This approach requires Bullhorn Support to pre-create the custom fields before migration, and the customer's Bullhorn edition must support the required number of custom fields (ATS Growth = 0, Bullhorn ATS = 2 custom objects, Growth/Enterprise = 10 custom objects with 55 fields each). We document the scorecard structure and recommended Bullhorn configuration during scoping.

Do Greenhouse workflows, automations, and interview kits migrate to Bullhorn?

No. Greenhouse workflows, automations, interview kits, and offer templates do not migrate to Bullhorn as code. Greenhouse's automation model (property-triggered workflows, interview kits with structured scorecards) has no direct Bullhorn equivalent. We deliver a written inventory of every Greenhouse automation and interview kit with its trigger, conditions, and actions, along with a recommended Bullhorn configuration approach. The customer's Bullhorn admin rebuilds these post-migration. Greenhouse's job board integrations and careers page configurations do not migrate; we preserve the job posting URLs as reference metadata on Bullhorn JobOrder records.

Can we migrate candidate source attribution and UTM data?

Yes. Greenhouse candidate source tracking (referral, job board, direct apply) migrates as a custom field on Bullhorn Candidate. Sourcing campaign UTM parameters stored in Greenhouse custom fields migrate alongside as text fields. Source history for candidates with multiple sources over time is preserved as a structured string in the source field. We document the source mapping during scoping so the customer's Bullhorn admin can configure filtering and reporting on source data in Bullhorn.

How do we handle the parallel-run window during Greenhouse's historical migration?

Greenhouse's documented historical data migration takes 4-6 weeks, during which the customer continues using their old ATS (in this case, Greenhouse) for new candidates while Greenhouse processes historical records. We coordinate the Bullhorn go-live date to begin before this window closes: Bullhorn receives new hires and new candidate submissions from the go-live date forward, while Greenhouse processes historical data. Any candidates created in Greenhouse during the migration window are included in the final delta migration step at cutover. Active candidate migration (Greenhouse's manual bulk import step) runs concurrently and is a customer-performed action that we document and support.

What happens to Greenhouse's tiered office and department structure in Bullhorn?

Greenhouse Plus and Pro customers may use hierarchical tiered offices and departments. Bullhorn has no native hierarchical office structure; the standard approach is to flatten into Bullhorn's Category or Business Sector taxonomy, or to represent the hierarchy in a custom object. We flag tiered structures during scoping, document the flattening strategy, and deliver a mapping table in the migration scope. Core tier customers using flat Greenhouse office structure map directly to Bullhorn categories without hierarchy loss.

Do we migrate candidate attachments (resumes, cover letters)?

Yes. Resume files, cover letters, portfolio documents, and other attachments on Greenhouse Candidates and Applications migrate as Bullhorn Attachment records linked to the corresponding Candidate. We handle file type detection, preserve original file names, and map binary blobs to Bullhorn's attachment storage. Bullhorn's file size limit (typically 25 MB per attachment) applies; files exceeding this limit are flagged in the migration scope for the customer's Bullhorn admin to handle manually post-migration.

## Related migrations

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

## Sources: official documentation

1. [Understanding Custom Objects — Bullhorn ATS](https://kb.bullhorn.com/ats/Content/BHATS/Topics/understandingCustomObjects.htm)
2. [Understanding Bullhorn Field Edit Types](https://kb.bullhorn.com/ats/Content/BHATS/Topics/understandingBHFieldEditTypes.htm)
3. [A guide to data hygiene for staffing firms — Bullhorn](https://www.bullhorn.com/spring-clean-your-data/)
4. [How to Import Data into Bullhorn — Bullhorn ATS](https://kb.bullhorn.com/ats/Content/BHATS/Topics/importingDataToBullhorn.htm)
5. [Custom Import Troubleshooting — Bullhorn ATS](https://kb.bullhorn.com/ats/Content/BHATS/Topics/customImportTroubleshooting.htm)
6. [How to get the correct default value of date time fields — Bullhorn Support Forums](https://supportforums.bullhorn.com/viewtopic.php?t=33686)
7. [File size limit for email and record file attachments — Bullhorn](https://help.bullhorn.com/article/What-is-the-file-size-limit-for-email-and-record-file-attachments)

Get a quote

## Moving from Greenhouse to Bullhorn ATS & CRM?

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

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