Migrate your Dayforce data

The Worker record is Dayforce's core employee object, holding biographical, employment, and assignment data. We extract Workers via the RESTful API and map them to the destination system with full field fidelity including employment status, hire date, and organizational assignment.

Jobs represent role definitions; Job Assignments associate Workers to Jobs with effective dates. Dayforce exports these via CSV (Job Assignment.csv, Job.csv) with all fields including Workers Comp classification codes. We ingest the exported CSV and preserve the assignment hierarchy during migration.

Position Management models organizational hierarchy. Position Terms define the duration and status of a position. Exports produce PositionTerm.csv with ShortName as the sort key. We map Position Terms to the destination's equivalent org-unit structure while preserving effective date ranges.

Dayforce supports multiple legal entities per organization (relevant for multi-jurisdiction payroll). The API returns LegalEntityXRefCode in payroll and benefits exports. We map legal entities but note that payroll tax configuration (federal, state/provincial, local) must be manually re-established in the destination system.

Rates are effective-dated on Workers. When a new rate overlaps an existing rate's start date, Dayforce auto end-dates the prior rate. We sequence rate history chronologically during migration and flag any gaps that would require a rate restart in the destination system.

Earning Groupings categorize pay components (hours-based vs. flat, reporting accumulations). The API passes MTD/QTD/YTD hours accumulations to benefits in 063 record type format. We map groupings but note that destination payroll systems may use different earning code taxonomies requiring manual mapping review.

Dayforce tracks accrual balances, carryover, and usage per Worker. We extract current balance snapshots and accrual rate configurations. Note that carryover rules and negative balance tolerances are plan-level settings that must be manually reconfigured in the destination system.

Dayforce supports custom fields at the Worker level and on document entities. Custom field functions allow computed values. We extract all custom field values but note that the destination system may not support the same data types or function libraries, requiring field-level review per custom field.

Dayforce maps benefit plan options to Tiers (coverage levels based on dependents). Tiered Rates Rule governs pricing. Benefits Data Export produces carrier-compatible 063/064 record files. We extract enrollment elections and tier assignments but note that carrier-specific export configurations must be replicated or rebuilt in the destination benefits module.

Employee National ID migration supports Tax Identification Number and Social Insurance Number only — other ID types are not supported by the Dayforce migration interface. We flag any non-supported ID types and advise manual re-entry or alternative verification in the destination system.

Dayforce manages documents attached to entities (Workers, Jobs, Positions). Document types are assigned to entities via the Entities configuration. We extract document metadata and binary blobs where accessible, but document retention policies and entity associations must be verified post-migration.

Workers Comp classification codes are assigned to Jobs in Org Setup > Jobs and Job Assignments. Multiple jobs can share a single code via multi-select. We extract the code-to-job mapping from the Workers Comp tab export and preserve it in the destination system.