Migrate from Dayforce to BambooHR

Dayforce Workers are the core employee record containing biographical, employment, and assignment data. We extract Workers via the Dayforce RESTful API with all standard fields (name, DOB, hire date, termination date, employment status, manager relationship, work location). The Worker's XRefCode is used as the Employee ID in BambooHR. Note that Dayforce's undocumented API rate limiter requires us to batch Worker extraction in chunks and implement exponential backoff; we pre-scope safe batch sizes before extraction begins.

Dayforce Jobs represent role definitions (title, pay grade, FLSA status, EEO category, Workers Comp codes). We map Job.title to BambooHR's job title field and store job-level attributes (FLSA, EEO, Workers Comp) as BambooHR custom fields. Since BambooHR does not have a native Job object, the full job taxonomy from Dayforce's Org Setup module is flattened into employee-level custom fields.

Dayforce supports multiple concurrent Job Assignments per Worker with effective dates. BambooHR stores a single job title and department per employee. When a Worker has one active assignment, we map directly. When a Worker has multiple concurrent or sequential assignments, we populate the primary assignment and store secondary role history as custom fields with start and end date metadata. Any gaps in assignment effective dates are flagged as potential employment discontinuity.

Dayforce Position Management models organizational hierarchy with Positions, Position Terms, and a tree of reporting relationships. BambooHR has no Position object and uses a flat Department and Location model. We map Position.shortName to a BambooHR Department, and manager reporting chains are resolved by linking BambooHR Employee.managerId through the Dayforce Worker hierarchy. Position Terms (duration, headcount, status) do not have a native destination and are stored as custom fields on the Employee record.

Dayforce Pay Rates are effective-dated per Worker; overlapping rate entries auto end-date prior rates at the system level. We extract the full rate history, normalize it chronologically, and load the most recent active rate as BambooHR's current pay entry. If BambooHR's compensation history feature is enabled on the destination plan, we import the full historical rate sequence. BambooHR stores pay frequency, compensation type (salary/hourly), and amount per compensation row. Rate-change gaps are flagged for the customer's HR team to review before cutover.

Dayforce tracks accrual balances, carryover, and usage per Worker across multiple time-off types. We extract current balance snapshots for each accrual type (PTO, sick, personal, etc.) and map to BambooHR's corresponding Time Off types. Note that carryover rules and negative balance tolerances are Dayforce policy settings that do not migrate; these must be manually configured in BambooHR's Time Off policy setup after migration. Accrual rate configurations are documented in the migration inventory for the customer's admin to rebuild.

Dayforce Earning Groupings categorize pay components (hours-based vs. flat, reporting MTD/QTD/YTD accumulations). BambooHR's Compensation record stores a single amount per entry without native support for recurring earning categories. We map the most recent MTD/YTD accumulations as custom fields on the Employee record and document the full earning grouping taxonomy in the migration inventory. Any bonus or supplemental pay runs extracted from Dayforce Quick Entry CSV are loaded as one-time compensation entries in BambooHR.

Dayforce maps benefit plan options to Tiers based on dependent coverage levels (Employee Only, Employee+Spouse, Employee+Children, Family). BambooHR provides benefits administration through a third-party broker network rather than a native enrollment engine with carrier EDI feeds. We extract current benefit elections, coverage tiers, and carrier information from Dayforce's Benefits Data Export and deliver a structured enrollment data file. The customer's HR admin or benefits broker recreates elections in BambooHR using the extracted data as a reference. Dayforce's carrier-compatible 063/064 record files do not have a BambooHR import pathway.

Dayforce supports custom fields at the Worker level and on document entities, including computed-value custom field functions. We extract all custom field values and map them to BambooHR custom employee fields. BambooHR's custom fields support text, number, date, dropdown, and checkbox types. The destination system's custom field structure must be provisioned in BambooHR before migration begins. Any computed-value functions from Dayforce do not evaluate in BambooHR and must be replaced with static values or manual recalculation.

Dayforce's Employee National ID migration interface supports only Tax Identification Number and Social Insurance Number. Any employee records with other national ID formats (passport numbers, visa numbers, national registry IDs) cannot be migrated through the standard interface and must be manually entered in BambooHR. We flag all non-TIN/SIN IDs during pre-migration discovery, extract what is available, and deliver a reconciliation list identifying records that require manual entry. This is a Dayforce platform limitation, not a BambooHR limitation.

Dayforce supports multiple legal entities per organization for multi-jurisdiction payroll. BambooHR uses a single-entity structure. When the source has multiple Dayforce legal entities, we consolidate entity-level metadata (entity name, tax ID, address) into a custom field on the primary Employee record and document the full legal entity structure in the migration inventory. Any jurisdiction-specific payroll data does not migrate because BambooHR Payroll does not support multi-country payroll processing.

Dayforce assigns Workers Comp classification codes to Jobs via multi-select in Org Setup. BambooHR does not have a native Workers Comp field; codes are typically tracked outside the system or by the customer's broker. We extract the Job-to-code mapping from Dayforce's Job Assignments CSV and deliver it as a supplemental file. If the customer needs Workers Comp codes in BambooHR, they are stored as custom fields on the Employee record. The customer configures workers comp settings through their insurance broker or payroll setup.