Migrate from ADP Workforce Now to BambooHR

ADP Workers map directly to BambooHR Employees. The Worker identifiers (associateOID) become the BambooHR employee ID field. We map Worker Person demographics (legal name, date of birth, gender, address, contact information) into BambooHR's Employment Info and Personal Info tabs. Employment status, hire date, termination date, and worker type (employee, contractor) map to BambooHR employment fields. The ADP hire date (businessCommunication.terminationDateDetails is used for term date if present) maps to BambooHR's hireDate and terminationDate fields. ADP's Worker Status (Active, Inactive) maps to BambooHR's employmentStatus field.

ADP Locations map to BambooHR Locations. ADP's Location validation table exposes locationCode, locationName, address, and status. We map these to BambooHR Location records and use the location association as the department proxy since BambooHR does not have a separate Departments object. For organizations with distinct ADP Locations and Departments (common in multi-state employers), we create a BambooHR Location per ADP Location and use the name field to encode both location and department context. Location assignment per Worker migrates to BambooHR's employee.location field.

ADP Departments map to BambooHR Locations with a naming convention that preserves the department hierarchy. Since BambooHR Locations function as the primary organizational unit and there is no separate Departments object, we map ADP departmentCode and departmentName into BambooHR Location records using a {department_code} - {department_name} format. If the organization uses a flat org structure, we use a single BambooHR Location per ADP Department Code. If Locations are used for geographic entities and Departments for functional units, we recommend using BambooHR's custom fields feature on the Location object to distinguish between location-type and department-type records.

ADP voluntary Deduction Instructions (health, dental, vision, retirement, FSA, HSA contributions) map to BambooHR Benefit records with the deduction type preserved. We map deductionCode, deductionDescription, and the deduction amount or percentage. BambooHR supports benefit plans with coverage tiers (employee only, employee plus spouse, employee plus children, family). We map ADP coverage election codes to BambooHR coverage tier values. Pre-tax and post-tax designations from ADP map to BambooHR's deductionType field (before-tax, after-tax, or subject to taxes). Deduction effective dates map to benefit start dates in BambooHR.

ADP Involuntary Withholding Orders (garnishments) and Company Loans are explicitly excluded from the Deduction Instruction API and cannot be exported programmatically. We flag all active garnishment orders during scoping, document the garnishment type, court order reference, withholding amount or percentage, and maximum deduction threshold for each affected employee. We deliver a manual reconciliation checklist that the customer's BambooHR admin uses to recreate each garnishment order as a manual deduction record in BambooHR after migration. This step requires HR involvement and cannot be automated.

ADP Benefit Plan enrolments map to BambooHR Benefit records. We map plan name, coverage level, employer contribution, employee contribution, and enrollment date. ADP's beneficiary and dependent data (Beneficiaries and Benefit Dependents endpoints) map to BambooHR's dependent fields on each benefit record. We note that BambooHR supports dependents on benefit records; if dependents are not enrolled in BambooHR as distinct records, we create a custom field on the Benefit record to capture beneficiary information.

ADP Time Off history maps to BambooHR Time Off records. We map time off type, request dates, approval status, and accrued balance at the time of migration. The ADP Time Off Requests API exposes current balances and leave event records. We map each leave event as a BambooHR Time Off entry with the original date, type, and hours. Leave plan configurations (accrual rates, carryover limits, negative balance rules) from ADP do not migrate programmatically; we deliver a leave plan configuration document listing each ADP leave plan with its settings so the admin can configure corresponding leave types in BambooHR.

ADP compensation data (pay rate, pay frequency, compensationPackage entries) maps to BambooHR Employment History records. We map the most recent pay rate and pay frequency into BambooHR's payRate and payRateType fields. If ADP contains historical compensation changes, we map these as Employment History entries with effective dates. ADP's compensationCurrencyCode maps to BambooHR's currency field. Bonuses, commissions, and one-time compensation entries map to BambooHR's pay extras as one-time entries with effective dates. Note that BambooHR's core pay fields support one active pay rate; historical compensation is stored as separate Employment History entries.

ADP Worker Custom Fields (8 types: amount, code, date, indicator, number, percentage, string, telephone) applied at the Worker and Worker Person levels cannot be read via the ADP API. During scoping, we request that the customer provide a reference file (CSV export from ADP reports) containing custom field values for each Worker. We map each ADP custom field to a BambooHR custom field of the corresponding type. String fields map to BambooHR Text custom fields; indicator maps to BambooHR Checkbox; date maps to Date; number and percentage map to Number; amount maps to Currency; code maps to Text. The customer must validate custom field values against the reference file post-migration.

ADP Validation Tables store domain values for Job Titles, Cost Numbers, Locations, and other reference data. We map Job Titles from ADP's validation table to BambooHR's job title field on the Employee record. Cost Numbers (project or department cost codes) from ADP do not have a direct BambooHR equivalent; we map these to a BambooHR custom text field on the Employee record for cost allocation tracking. If the organization uses multiple cost numbers per employee (labor distribution), we create a custom field with multiple values or recommend using BambooHR's time tracking add-on for granular cost allocation.