Migrate from Dayforce to Crelate

Dayforce Worker records are the core employee object holding biographical, employment, and assignment data. We extract Workers via the Dayforce RESTful API and map them to Crelate Candidate records. The mapping includes employee number (as Crelate External ID), legal name fields (first, middle, last), date of birth, hire date, employment status, and contact information. Note that Crelate is an ATS/recruiting platform; internal employee records (active payroll employees) that are not part of the recruiting pipeline should be flagged for a separate HRIS if the customer requires both recruiting and internal HR management post-migration.

Dayforce Job Assignments associate Workers to Jobs with effective dates and assignment-level details. We map Job Assignments to Crelate Job Orders, using the Dayforce Job title as the Job Order title, the Job Assignment start and end dates as the placement period, and the assignment status as the Job Order status. Multiple concurrent assignments for the same Worker map to separate Job Orders in Crelate. Dayforce's Workers Comp classification codes on Job Assignments map to custom fields on the Crelate Job Order.

Dayforce Job records are role definitions separate from the Worker-to-Job association. We extract Job records as a reference dataset and link them to Crelate Job Orders via a custom field (dayforce_job_id__c) so that the customer can maintain the relationship between placements and their source job titles in Dayforce. Job descriptions, job codes, and FLSA classification migrate as read-only reference fields.

Dayforce Position Management models organizational hierarchy and maps to Crelate Job Orders as organizational context fields. The Position ShortName (used as the sort key in Dayforce PositionTerm exports) migrates as a custom field on Crelate Job Order. Position Terms (defining position duration and status) map to Job Order status and end-date fields. We preserve the position hierarchy path as a custom field chain (position_level_1__c through position_level_5__c) to retain organizational reporting context.

Dayforce supports multiple legal entities per organization (relevant for multi-jurisdiction payroll). The API returns LegalEntityXRefCode in payroll and benefits exports. We map Dayforce Legal Entities to Crelate Client Companies, using the legal entity name as the company name and the LegalEntityXRefCode as the external ID for reconciliation. If the customer is migrating internal Dayforce data where Legal Entities represent internal business units rather than external clients, we map them to a Client Company named after the entity and flag the distinction for the customer.

Dayforce Pay Rates are effective-dated on Workers with auto end-dating on overlap. We extract the current active pay rate and any rate history, then map the current hourly/salary rate to a Crelate custom field (pay_rate__c) on the Candidate record. Crelate does not have a native payroll module; pay rate history is stored as a custom text or currency field rather than a native payroll object. We flag rate gaps and out-of-sequence dates during extraction and advise the customer on manual payroll verification post-migration.

Dayforce tracks accrual balances, carryover, and usage per Worker. We extract current balance snapshots as custom fields on Crelate Candidate records (pto_balance__c, sick_balance__c, etc.). Note that carryover rules and negative balance tolerances are payroll-configured and do not migrate to Crelate's recruiting data model. The customer should retain a Dayforce read-only export or a separate HRIS for ongoing time-off management if these balances are critical to internal workforce management.

Dayforce Earning Groupings categorize pay components (hours-based vs. flat, reporting accumulations). The API passes MTD/QTD/YTD hours accumulations in 063 record type format for benefits integration. We map Earning Grouping labels to custom fields on Crelate Candidate records for reference. These do not affect Crelate's recruiting functionality and are preserved as historical payroll context only.

Dayforce supports custom fields at the Worker level and on document entities, including computed values via custom field functions. We extract all custom field values and replicate them as custom fields on Crelate Candidate records using the Dayforce field label as the Crelate field label and the closest matching Crelate field type (text, number, date, picklist, checkbox). Fields using Dayforce computed functions are stored as their last-computed values with a note that the computation logic does not migrate and must be re-implemented if required.

Dayforce's Employee National ID migration interface supports only Tax Identification Number (TIN) and Social Insurance Number (SIN). We extract these as a masked custom field (national_id__c) on Crelate Candidate records with TIN or SIN as the ID type label. Other national ID formats (passport numbers, national registry IDs, visa numbers) cannot be migrated through Dayforce's standard interface and are flagged during pre-migration discovery for manual entry in Crelate or a separate compliance system.

Dayforce maps benefit plan options to Tiers (coverage levels based on dependents) with Tiered Rates Rules governing pricing. Benefits Data Export produces carrier-compatible 063/064 record files. We extract the current benefit election summary (plan name, tier, coverage level) as a text block in a custom field on Crelate Candidate records. Crelate does not have a benefits enrollment module; benefit election data is preserved as read-only reference only and must be maintained in a separate HRIS or benefits administration system.

Dayforce manages documents attached to entities (Workers, Jobs, Positions) with document types assigned via the Entities configuration. We extract document metadata (document type, filename, upload date, attached entity) and binary blobs where accessible, and load them as Crelate Documents attached to the corresponding Candidate record. We use the Dayforce document type as the Crelate document category. Documents without a binary blob (e.g., external links) are stored as a text field with the URL.

Workers Comp classification codes are assigned to Jobs in Dayforce Org Setup. Multiple jobs can share a single code via multi-select. We extract the code-to-job mapping from the Workers Comp export and map relevant codes to custom fields on Crelate Candidate records based on the Candidate's associated Job Order. The customer should verify that workers comp requirements for their industry and state are supported in their HRIS post-migration.