Migrate your Rippling data

The primary object in Rippling's data model. Workers represent employed individuals with all associated employment data. We migrate Worker records 1:1 including employment status, start date, and personal details. Source system Employee records map directly to Rippling Workers via standard field correspondence.

Job records define role titles, levels, and compensation bands. We preserve job titles and associated pay rates. Where the destination system uses a flat role field, we collapse Job into a string value and preserve the original Rippling Job title in a custom field.

Organizational units in Rippling that map directly to standard department objects in most target HRMs. We migrate department hierarchies and maintain parent-child relationships. Where the destination flattens org structure, we map children under the primary department.

Rippling distinguishes legal entity work locations from actual work sites. We migrate Work Locations with address, type, and jurisdiction flags. Legal entity assignments are preserved as separate location records to maintain payroll entity context.

Rippling tracks all employment changes — title changes, compensation changes, transfers — with effective dates. We sequence these chronologically in the migration. If the destination does not support a change-log, we write the current effective record and flag the historical log for manual verification post-migration.

Pay rates, salary, bonuses, and equity information live as linked compensation records. We map these to equivalent fields in the destination. Custom compensation structures require value mapping, especially for currency fields and bonus plan references.

PTO accruals and balances are time-sensitive data that depend on the migration cutover date. We snapshot balances at cutover and load them as opening balances in the destination. The destination's accrual method (front-loaded vs. accrual-based) may differ, requiring adjustment.

Benefit plan assignments and carrier details are migratable, but active claim histories and FSA/HSA balances require additional scoping. We migrate enrollment records as of the cutover date and flag open claims for manual handling.

Rippling Custom Objects store structured data that customers have built on top of the standard worker graph. We export Custom Object records and field definitions via the Custom Objects API. Field types — text, number, formula, summary — are mapped to equivalent destination types where possible; unsupported types are noted in the field map.

Rippling's device inventory and MDM enrollment records are tightly coupled to Rippling's IT stack and do not have a clean export path to general-purpose HRMs. We do not migrate device records. Laptop and equipment assignments are noted as organizational context, not transferred.

Spend management data — corporate card transactions, expense reports, bill pay records — lives in Rippling's finance module. These are financial records rather than HR data and are out of scope for HRMS migrations.

Rippling's workflow definitions are configuration objects, not employee records. They do not migrate directly to other platforms, which have different workflow engines. We document active workflows for the customer to re-implement post-migration.

Employee documents such as offer letters, contracts, and tax forms are stored in Rippling. We export document metadata and links. Actual file content depends on whether Rippling's file storage is accessible via API; if not, we flag documents for manual retrieval.