Migrate from Rippling to BambooHR

Rippling Workers map 1:1 to BambooHR Employee records. The Rippling Worker is the primary record carrying name, contact details, employment status, hire date, and termination date. We extract these as the base import, resolving the BambooHR employeeId from the firstName/lastName/dateOfBirth triple. EmploymentHistoryStatus (Active, Inactive, On Leave) in Rippling maps to BambooHR's employmentHistoryStatus field.

Rippling Job records define role titles, levels, and compensation bands. The most recent effective-dated Job record at cutover determines the BambooHR jobTitle field value. Rippling's jobLevel maps to a BambooHR custom text field if the customer requires level tracking. Historical job changes are preserved as a custom long-text field in BambooHR with a chronological sequence of title and level changes for audit.

Rippling Departments are organizational units with parent-child hierarchies. BambooHR's department field is a flat string value per employee. We extract the employee's current department assignment at cutover and resolve the full department hierarchy from Rippling into BambooHR's departmental structure. BambooHR supports a secondary department field for employees split across units, which we use when the customer's Rippling data shows multi-department assignments.

Rippling distinguishes legal entity work locations from actual work sites, each with address, type, and jurisdiction flags. BambooHR's location field is a single string value per employee. We resolve the employee's primary work location from Rippling at cutover and store the full address as a custom text block in BambooHR. Multi-state or hybrid assignments are stored as a custom field listing all assigned locations.

Rippling tracks all employment changes — title changes, compensation changes, transfers — with effective dates as a chronological sequence per Worker. BambooHR does not have a native effective-dated employment history object. We capture the full employment history as a custom long-text field (employment_history__c) in BambooHR, storing a structured log of every change with effective date, type, and detail. The most recent change drives the flat-field values on the Employee record.

Pay rates, salary, bonuses, and equity information live as linked compensation records in Rippling. We map the most recent base pay rate to BambooHR's payRate and payRateType (salary, hourly) fields. Bonuses and equity require custom fields in BambooHR (bonus_amount__c, equity_type__c). We use the cutover-date compensation record as the active value, with bonus and equity history stored as a custom JSON or delimited-text block for audit. Custom compensation structures require explicit value mapping during scoping.

PTO accruals and balances are time-sensitive and depend entirely on migration cutover date precision. We extract YTD accrual totals and current balances at cutover, aligning the snapshot date to Rippling's pay period end date. We load these as explicit opening balances in BambooHR's Time Off module with a recorded snapshot date so auditors can verify accuracy. BambooHR's accrual policy must be configured before import so that the opening balance does not trigger duplicate accruals.

Benefit plan assignments and carrier details are migratable as of the cutover date. We map benefit plan name, coverage level, and carrier to custom Employee fields in BambooHR. Active claim histories and FSA/HSA balances require additional scoping and may need separate export from Rippling's benefits module before offboarding. We flag any EOR-specific benefit records tied to international employees for jurisdiction-specific handling.

Rippling Custom Objects store structured data built on top of the standard worker graph — certifications, equipment assignments, business-unit-specific fields. We export the field definitions (API names, types, required flags) via the Rippling Custom Objects API before exporting record data, then map each custom field to an equivalent BambooHR custom field. Custom field types in Rippling (text, number, date, picklist, lookup) must be mapped to BambooHR's supported custom field types. Custom Objects with lookup relationships to Workers require those lookups resolved to employeeId before import.

Employee documents — offer letters, contracts, tax forms — are stored in Rippling. We export document metadata (file name, type, upload date, associated employee) and, where Rippling's file storage is accessible via API, the actual file content. BambooHR stores documents as Employee Files attached to each employee record. We link each document to the corresponding BambooHR employee record by employeeId match. Document type (offer letter, I-9, W-4, etc.) is preserved as a tag or custom field.