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

# Rippling to Bullhorn ATS & CRM migration

We migrate Workers, Jobs, Departments, Compensation, PTO, and Custom Objects from Rippling into Bullhorn's ATS and CRM schema, resolving the unified worker graph versus candidate-contact-object split, preserving effective-dated employment history, and handling Bullhorn's tier-specific Custom Object limits before any data moves.

Short answer

FlitStack AI migrates candidate or users, contacts, candidate or job orders, client corporation or business sectors and client corporation or contact address from Rippling 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: 3-5 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/rippling/to/bullhorn#what-moves)

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

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

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

Candidate or User Contact Candidate or Job Order Client Corporation or Business Sector Client Corporation or Contact Address

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

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

Rippling and Bullhorn serve different operational models, which makes this migration a domain pivot rather than a direct record copy.

Read the full summary

Rippling's unified worker graph treats an employed individual as a single record with linked employment, compensation, and PTO data. Bullhorn splits candidate data across Candidate, Contact, and Client Corporation objects with an explicit Placement record for every staffing assignment. We resolve that structural split at scoping: Rippling Workers who are staffing firm employees migrate to Bullhorn internal Users and Contacts; any Rippling Workers who represent the staffing firm's candidate pool migrate to Bullhorn Candidate records with a parallel to the Client Corporation record. Effective-dated employment history, compensation records, and PTO balances map into Bullhorn Custom Objects or Notes depending on the customer's Bullhorn edition tier, because Bullhorn does not natively store payroll, PTO accruals, or employment-history audit trails. Rippling Custom Objects are exported via the Rippling Custom Objects API, their schemas exported field-by-field, and the destination Bullhorn Custom Object definitions created before data migration begins. Bullhorn's Custom Object limits vary by tier — 10 with 55 fields on Enterprise, 2 on Bullhorn ATS, none on ATS Growth — which we surface during scoping so the customer can confirm their destination tier before mapping begins. Workflows, automations, device enrollment, and corporate card data do not migrate because Bullhorn is a recruiting and staffing CRM, not an HRMS with payroll or IT provisioning.

1:N split

### Worker → Candidate or User (split required)

Rippling Workers represent employed individuals in the staffing firm's internal workforce and (if the firm is using Rippling ATS) their candidate pool.

How it maps

We split at scoping: internal employees of the staffing firm migrate to Bullhorn User (for system access) and Bullhorn Contact (for HR records); any Rippling Workers representing the firm's candidate pool migrate to Bullhorn Candidate records. The split is determined by the customer's business model and is documented before any data movement begins.

1:1

### Worker → Contact

Rippling Workers who are internal employees of the staffing firm migrate to Bullhorn Contact records.

How it maps

Name, email, phone, work location, start date, and employment status transfer as Contact fields. The Worker's Rippling employee ID is preserved in a custom field for reconciliation.

configuration

### Job → Candidate (title field) or Job Order

Rippling Job records define titles, levels, and pay bands.

How it maps

For internal staffing firm employees, the Job title migrates as a Contact field or custom Contact field. For candidate-facing migration, Rippling Job titles map to Bullhorn Candidate preferred\_title or to Bullhorn Job Order records depending on whether the customer is migrating historical job preferences or active job orders.

1:1

### Department → Client Corporation or Business Sector

Rippling Departments map to Bullhorn Client Corporation records if the department represents a client organization of the staffing firm.

How it maps

Internal organizational departments (HR, Finance, Recruiting Operations) map to Bullhorn internal Corporate fields or are stored as Notes attached to the relevant Contact records. The mapping depends on whether the staffing firm uses Rippling to track their own org structure or their client roster.

lookup

### Work Location → Client Corporation (address) or Contact Address

Rippling Work Locations carry legal entity and actual work-site addresses.

How it maps

We extract address fields (street, city, state, zip, country) and map them to Bullhorn Client Corporation address fields for client locations or Contact address fields for candidate work preferences. Jurisdiction flags are preserved in custom fields if regulatory reporting depends on them.

mapping

### Employment History → Candidate (custom fields) or Note

Rippling tracks title changes, compensation changes, and transfers with effective dates as a chronological sequence.

How it maps

Bullhorn has no native employment history object. We sequence the changes by effective date and load them as Bullhorn Custom Object records (on Enterprise or Bullhorn ATS tier) or as Note records with a structured body (on ATS Growth tier). Each history entry carries the original effective date, change type, and prior and new values.

******What moves 12 objects

Rippling Bullhorn ATS & CRM

- Worker Candidate or User split
- Worker Contact 1:1
- Job Candidate or Job Order transformed
- Department Client Corporation or Business Sector 1:1
- Work Location Client Corporation or Contact Address transformed
- Employment History Candidate or Note transformed

\+ 6 more in the mapping below

## How Rippling 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                | Rippling                                                                                       | Bullhorn ATS & CRM                                                                                                                                        |
| ------------------------ | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Primary object model     | Unified worker graph — one Worker record with linked employment, compensation, and PTO data    | Split ATS/CRM model — Candidate for job seekers, Contact for client contacts, Client Corporation for client companies, Placement for staffing assignments |
| Payroll and time-off     | Native US and Global Payroll, PTO tracking, and benefits enrollment as core modules            | No native payroll or PTO — Bullhorn handles billing for placed candidates but not employer-side payroll or employee time-off                              |
| Custom objects           | Custom Objects API with per-customer schema definitions at all active module tiers             | Enterprise tier allows 10 Custom Objects with 55 fields each; Bullhorn ATS tier allows 2; ATS Growth tier has none                                        |
| Pricing model            | Per-employee per month anchored by mandatory Unity Platform ($8/employee) with modular add-ons | Per-user per month starting at $99/user on ATS & CRM Core, up to $315/user on Enterprise, billed annually                                                 |
| Employment history       | Effective-dated employment changes tracked chronologically as a first-class data model         | Placement history tracks assignments at client companies; no native employment audit trail for internal staff                                             |
| IT and device management | Full MDM, IAM, device inventory, and app provisioning in the IT Module                         | No IT or device management capabilities — staffing-focused ATS and CRM only                                                                               |
| Workflow automation      | Workflow engine triggers HR, IT, and Finance actions across modules from a single rule builder | Bullhorn Automation (formerly Herefish) is a separate product; standard Bullhorn lacks native workflow automation                                         |

## What to watch for in a Rippling 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

### Rippling workers and Bullhorn candidates are not the same record type

Rippling Workers represent employed individuals in a unified graph; Bullhorn splits candidate data across Candidate, Contact, and Client Corporation.

How we handle it

If the staffing firm was using Rippling to track both their internal employees and their candidate pool, we must split at migration time: internal staff become Bullhorn Users and Contacts; candidates become Bullhorn Candidates. We determine the split rule during scoping based on the customer's business model. Migrations that skip this step end up with all Rippling Workers landing as Bullhorn Candidates, which creates duplicate records for internal employees who also appear in Bullhorn as staffing firm staff.

high

### Bullhorn edition limits cap Custom Object count before migration begins

Bullhorn enforces a Custom Object tier ceiling: Enterprise allows 10 Custom Objects with 55 fields each; Bullhorn ATS allows 2; ATS Growth allows 0.

How we handle it

Rippling Custom Objects have no equivalent ceiling. If the customer is on Bullhorn ATS or ATS Growth and has more than 2 or 0 Rippling Custom Objects respectively, we cannot map all of them during migration. We surface the tier mismatch during scoping and recommend a Bullhorn Enterprise upgrade or a Notes-based fallback before any data movement begins.

medium

### PTO and compensation require Bullhorn-side schema or Notes fallback

Bullhorn has no native PTO accrual or compensation history object.

How we handle it

Rippling's PTO balances and compensation records cannot map to a native Bullhorn field. We load these as Bullhorn Custom Object records on Enterprise or Bullhorn ATS tier, or as structured Notes on ATS Growth tier. If the customer is on a Bullhorn tier that cannot accommodate these as Custom Objects, we document the Notes mapping and flag that any downstream reporting on PTO or compensation requires manual reconciliation or a third-party integration.

medium

### Rippling Custom Object schema must be exported before record data

Rippling Custom Objects are defined per-customer with no standardized field schemas.

How we handle it

If the customer relies on Custom Objects for certifications, equipment assignments, or business-unit-specific fields, we must export field definitions (field API names, types, required flags, data types) before exporting any record data. Without the schema export, Bullhorn field mappings will be incomplete and field type mismatches will cause import rejections. We request schema access via the Rippling Custom Objects API during discovery so mapping is complete before data movement begins.

medium

### Workflows, automations, device enrollment, and spend data do not migrate

Rippling workflows, IT module automations, device enrollment records, and corporate card spend data are out of scope for Bullhorn migration.

How we handle it

Bullhorn is a recruiting and staffing CRM, not an HRMS with IT provisioning or financial spend management. We do not migrate Rippling Workflows because Bullhorn's automation model (Bullhorn Automation as a separate product) requires separate configuration. We deliver a written inventory of active Rippling Workflows and IT automations for the customer's admin to evaluate for Bullhorn Automation or manual process replacement post-migration.

## How the migration runs

1. ### Discovery and business model clarification

   We audit the source Rippling portal across active modules (Unity Platform tier, HCM, Payroll, IT, Spend), worker record count, Custom Object count and schemas, and any ATS integration data.

   What this step covers

   The critical scoping question for Rippling to Bullhorn is whether the Rippling instance tracks the staffing firm's internal employees, their candidate pool, or both. We confirm the split rule (Worker to internal Contact vs Worker to Bullhorn Candidate) with the customer's primary contact before any data movement begins. We also confirm the customer's Bullhorn edition tier to validate Custom Object capacity against the Rippling Custom Object count.

2. ### Schema export and destination provisioning

   We export Rippling Custom Object field definitions via the Custom Objects API, confirm field types and required flags, and provision the equivalent Bullhorn Custom Objects (or Notes fallback) based on the destination Bullhorn edition.

   What this step covers

   If the Rippling Custom Object count exceeds Bullhorn's tier limit, we escalate to the customer for tier upgrade or schema consolidation before proceeding. We also create any required Bullhorn custom Contact or Candidate fields for compensation, PTO, and employment history before record migration begins.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Bullhorn Sandbox (or staging environment) using production-like data volume.

   What this step covers

   The customer's Bullhorn admin reconciles record counts (Workers in, Candidates and Contacts in), spot-checks 25-50 random records against the Rippling source, and confirms the Worker-to-Candidate versus Worker-to-Contact split is working as designed. Any field mapping corrections, Custom Object schema mismatches, or tier-limit issues surface here before production migration begins.

4. ### Owner and user reconciliation

   We extract every distinct Rippling Owner referenced on Worker, Job, Department, and Compensation records and match by email against the Bullhorn destination's User table.

   What this step covers

   Any Rippling Owner without a matching Bullhorn User goes to a reconciliation queue. The customer's Bullhorn admin provisions missing Users (active or inactive depending on whether the original Rippling user is still active). Migration cannot proceed past this step because Bullhorn's record model requires a valid Owner reference on most standard objects.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Bullhorn Users (validated), Client Corporations (from Rippling Departments that represent client relationships), Contacts (internal staffing firm employees from Rippling Workers), Candidates (candidate pool from Rippling Workers where applicable), Job Orders (if migrating active job data), Custom Objects (after standard object records are loaded, because they may have lookup dependencies), Compensation and PTO snapshots (as Bullhorn Custom Objects or Notes), and Document metadata (as Notes or file attachments).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins.

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

   We freeze Rippling writes during cutover, run a final delta migration of any records modified during the migration window, then enable Bullhorn as the system of record.

   What this step covers

   We deliver the Workflow and Automation inventory document to the customer's admin team, flagging that Rippling workflows require Bullhorn Automation configuration or manual rebuild as a separate engagement. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not configure Bullhorn Automation, rebuild Rippling workflows in Bullhorn, or set up Bullhorn integrations with job boards or background check providers as part of the standard migration scope.

![](https://flitstack.ai/platforms/rippling.svg) Rippling ![](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

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

**7-12 weeks** Large or heavily customised accounts

A quote scales with worker record volume, Custom Object complexity, and whether employment history requires transformation into Bullhorn Notes or Custom Objects. Every quote is scoped with you; there is no self-serve pricing.

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

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

- Staffing and recruiting agencies require purpose-built ATS and CRM capabilities that Rippling's all-in-one workforce platform does not provide. Bullhorn offers native candidate pipeline management, client relationship tracking, job order workflows, placement tracking, and staffing-specific reporting that Rippling lacks as an HRMS focused on employed workforces. Agencies switching from Rippling cite the absence of candidate-centric features — job board posting, resume parsing, placement tracking, and commission billing — as the primary driver.
- Rippling's mandatory Unity Platform prerequisite ($8/employee/month) plus module add-ons can exceed Bullhorn's per-seat pricing for staffing firms that do not need global payroll, EOR, or IT provisioning. Teams that onboard Rippling for ATS functionality and subsequently pay for the full platform layer report cost misalignment when the platform's primary value — unified HR, payroll, and IT — is not being used by a recruiting-focused firm.
- Bullhorn's native integrations with staffing job boards (Indeed, LinkedIn, ZipRecruiter, Broadbean), background check providers (Checkr), and staffing-specific tools exceed Rippling's integration catalog for recruiting workflows. Recruiting agencies cite Bullhorn's ecosystem of staffing-focused connectors as a reason to consolidate on Bullhorn rather than maintain Rippling alongside a separate ATS.
- Reported implementation bugs in Rippling — including ATS integration sync duplicates, HSA/FSA display errors, and MS365 recognition failures — have caused recruiting firms to lose confidence in data reliability. One Reddit thread in r/humanresources described the platform as 'held together with bandaids and chewing gum,' citing a pattern of unresolved issues during implementation that prompted internal teams to evaluate alternatives.
- Rippling's customer support responsiveness is a recurring complaint in G2 reviews, with users scoring Rippling's support at 9.3 versus Bullhorn's 8.3 on the G2 comparison. Recruiting firms operating in fast-moving candidate markets report that delayed support responses during critical issues — such as payroll errors or integration failures — directly impact placement revenue and client satisfaction.

Questions, answered

## Rippling to Bullhorn ATS & CRM migration questions

How long does a Rippling to Bullhorn migration take?

Most Rippling to Bullhorn migrations land between three and five weeks for firms under 2,000 Workers with fewer than 5 Custom Objects and no employment history sequencing requirements. Migrations that include compensation record history, PTO balance snapshots, multiple Custom Objects with complex field schemas, or a large candidate pool alongside internal employees move to seven to twelve weeks because of schema export, Custom Object tier confirmation, and transformation logic. Bullhorn's own guidance for staffing firms ranges from two to six weeks for standard ATS/CRM setup, and our Rippling-specific scope adds discovery and transformation work on top of that baseline.

Do Rippling Workflows, IT automations, and PTO accrual rules migrate to Bullhorn?

No. Rippling Workflows and IT automations do not migrate to Bullhorn because Bullhorn's automation model (Bullhorn Automation as a separate product) requires separate configuration from scratch. We do not migrate them as code. We deliver a written inventory of every active Rippling Workflow and IT automation with its trigger, conditions, and actions, and the customer's Bullhorn admin or a Bullhorn partner evaluates Bullhorn Automation for rebuild. Bullhorn also has no native PTO accrual engine; Rippling PTO balances are migrated as Custom Object records or Notes with a cutover date snapshot, but the customer's admin must configure a third-party time-off integration or manual process post-migration.

Can we keep Rippling for internal HR and use Bullhorn for recruiting?

Yes. A hybrid stack is a common pattern for staffing firms that onboarded Rippling for internal workforce management and now need a purpose-built recruiting ATS. Rippling continues to manage internal employee payroll, benefits, and HR records; Bullhorn handles the candidate pipeline, client relationships, job orders, and placements. We can migrate the Rippling Worker records as Bullhorn Candidates and Contacts in parallel with the customer maintaining Rippling for their employed staff. The two systems would require a manual sync process or a third-party integration for any shared data (such as placed candidates who become Rippling employees), because Rippling and Bullhorn do not have a native bidirectional sync.

Do we lose historical employment history, compensation, and PTO data?

No. We migrate employment history, compensation records, and PTO balances as Bullhorn Custom Object records (on Enterprise or Bullhorn ATS tier) or as structured Notes (on ATS Growth tier). Each record carries the original effective date, change type, and values so the history is preserved and auditable. Active claim histories and FSA/HSA balances are flagged as out of scope because they are financial records requiring carrier portability documentation rather than HR record data. Bullhorn does not natively render these records in a timeline view; the customer accesses them as Custom Object or Note data attached to the relevant record.

How do we handle Rippling Custom Objects in Bullhorn?

Rippling Custom Objects are exported field-by-field via the Rippling Custom Objects API, their schemas confirmed during discovery, and the destination Bullhorn Custom Object definitions created before data import. Bullhorn's Custom Object limits are confirmed during scoping: Enterprise allows 10 Custom Objects with 55 fields each; Bullhorn ATS allows 2; ATS Growth allows 0. If the customer's Rippling Custom Objects exceed the destination tier's limits, we escalate during scoping and recommend either a Bullhorn Enterprise upgrade or a Notes-based fallback. The customer chooses the approach before migration begins.

What Rippling data does FlitStack AI not migrate?

We do not migrate Rippling Workflows, IT automations, device enrollment records, corporate card data, or expense reports. Rippling device inventory and MDM enrollment records are tightly coupled to Rippling's IT stack and have no clean export path to Bullhorn's ATS/CRM model. Corporate card transactions and expense reports are financial records rather than HR data and are out of scope for Bullhorn migration. Workflow definitions are configuration objects that do not transfer across platforms with different automation engines. We deliver a written inventory of all active Rippling Workflows and IT automations for the customer's admin to rebuild in Bullhorn Automation or replace with manual processes.

## 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) [**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 Bullhorn ATS & CRM** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/greenhouse/to/bullhorn) [**Rippling to BambooHR** Mapping · history · rollback](https://flitstack.ai/migrations/hrms/rippling/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 Rippling 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)
