Migrate from Rippling to Bullhorn ATS & CRM

Rippling Workers represent employed individuals in the staffing firm's internal workforce and (if the firm is using Rippling ATS) their candidate pool. 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.

Rippling Workers who are internal employees of the staffing firm migrate to Bullhorn Contact records. 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.

Rippling Job records define titles, levels, and pay bands. 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.

Rippling Departments map to Bullhorn Client Corporation records if the department represents a client organization of the staffing firm. 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.

Rippling Work Locations carry legal entity and actual work-site addresses. 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.

Rippling tracks title changes, compensation changes, and transfers with effective dates as a chronological sequence. 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.

Rippling Compensation Records include pay rates, salary, bonuses, and equity information linked to Workers. Bullhorn stores placement pay rate and commission structure on Placement records but does not natively store internal employee compensation. We load compensation data as Bullhorn Custom Object records (Enterprise or Bullhorn ATS tier) or as structured Notes attached to the Contact, preserving pay type, amount, currency, and effective date.

PTO accruals and balances are time-sensitive. We snapshot balances at the migration cutover date, load them as Bullhorn Custom Object records with a balance date field, and flag whether the destination Bullhorn instance has a time-off tracking integration active. Bullhorn does not natively manage PTO accruals; if the customer needs this post-migration, a third-party integration or manual process is required. The snapshot date is recorded so auditors can verify the migration cutover point.

Benefit plan assignments and carrier details are migratable from Rippling as of the cutover date. 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. We migrate enrollment records as Bullhorn Notes with a structured template or as Custom Object records depending on the destination Bullhorn edition.

Rippling Custom Objects store structured data built on top of the standard worker graph. We export Custom Object records and field definitions via the Rippling Custom Objects API, pre-create the equivalent Bullhorn Custom Object schema (with field types mapped: text to text, date to date, number to number, picklist to picklist), and load records after schema validation. Bullhorn's Custom Object limits by tier are confirmed during scoping: Enterprise allows 10 Custom Objects with 55 fields each; Bullhorn ATS allows 2; ATS Growth allows none. If the customer's Rippling Custom Objects exceed the destination tier's limits, we recommend a tier upgrade or a Notes-based alternative during scoping.

Employee documents — offer letters, contracts, tax forms — are exported from Rippling as file metadata and links. Actual file content depends on whether Rippling's file storage is accessible via API. We migrate document metadata as Bullhorn Notes with a URL reference to the original file, or as file attachments on the relevant Candidate or Contact record if the Bullhorn instance has document storage enabled.

Rippling Owners (HR admins, team managers) map to Bullhorn User records. We resolve owners by email match. Any Rippling Owner without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.