Migrate from Dayforce to Zoho Recruit

Dayforce Worker records map to Zoho Recruit Candidates. The Worker's first name, last name, date of birth, address, phone, and email fields map to the Candidate module's standard fields. Last Name is mandatory in Zoho Recruit; Workers without a last name in Dayforce are flagged during pre-migration discovery and given a placeholder value of 'Not Provided' per Zoho Recruit's import requirements. Any Candidate who already has a separate Zoho Recruit account cannot be imported — those accounts must be closed first or those records excluded from the migration scope.

Dayforce Job Assignments map to Zoho Recruit Job Openings. The Job title, job description, position type (full-time, part-time, contract), and department assignment from Dayforce map to Job Opening name, description, employment type, and department respectively. The Job Opening's status (open, on hold, closed, cancelled) maps from Dayforce's position status. Active Job Opening limits vary by Zoho Recruit plan: Free allows 1, Standard allows 100 per recruiter, Professional allows 250, and Enterprise allows 750. We verify the plan tier matches the customer's job opening count before migration.

For staffing agency use cases in Zoho Recruit, the hiring manager or client company associated with a Dayforce position maps to Zoho Recruit's Client module (company) and Contact module (individual). The client's company name, address, and primary contact details from Dayforce's legal entity or client configuration map to the Client record, with the primary contact person's name, title, phone, and email mapped to the Contact record linked to that Client.

Dayforce stores candidate evaluations and interview feedback as part of its Recruiting module. These map to Zoho Recruit's Interview records linked to the relevant Candidate and Job Opening. Interview date, interviewer name, interview type, and evaluation score or status migrate as structured fields. Interview feedback forms from Dayforce map to Zoho Recruit's Interview Feedback Form module.

Dayforce tracks candidate application status changes through its recruiting workflow. These status transitions map to Zoho Recruit's candidate activity timeline and pipeline stage values. The candidate's source (referral, job board, career site) from Dayforce maps to Zoho Recruit's Source field. Application date and any offer details migrate as candidate record metadata.

Dayforce supports documents attached to Workers (resumes, offer letters, certifications). We extract document metadata and binary blobs where the API exposes them and load them into Zoho Recruit's attachment system on the corresponding Candidate record. Resume files migrate as Candidate resume attachments. Zoho Recruit's Document Library supports folder sharing on Standard and above. Note that Zoho Recruit enforces per-user export permissions; the migration user must hold Export permission for the Candidates module.

Dayforce custom fields at the Worker level that relate to recruiting (skills tags, sourcing flags, screening questions) map to Zoho Recruit custom fields on the Candidate module. Custom field limits are plan-dependent: Standard allows 50 custom fields per module, Professional allows up to 300. We audit Dayforce custom fields during pre-migration discovery and flag any that exceed the customer's Zoho Recruit plan limit for resolution before import. Computed-value custom fields from Dayforce cannot be migrated as live computations and are imported as static values.

Dayforce Pay Rates are part of the HCM compensation module and have no equivalent in Zoho Recruit's ATS scope. Pay rate data, effective-dated rate history, earning groupings, and compensation bands are documented as out-of-scope for this migration. Customers who need to preserve pay rate history should export it separately from Dayforce for manual reference or a separate compensation system.

Dayforce Benefits Enrollments, tiered coverage levels, dependent information, and carrier feeds (063/064 record files) have no ATS equivalent in Zoho Recruit. Benefits data is out-of-scope for this migration and should be managed within Dayforce or a separate benefits administration platform if Dayforce is being decommissioned.

Dayforce's Employee National ID migration interface supports only Tax Identification Number (TIN) and Social Insurance Number (SIN). Passport numbers, national registry IDs, visa numbers, and other national ID types are not supported by Dayforce's export interface and cannot be migrated. We flag all non-TIN/SIN IDs during pre-migration discovery. Zoho Recruit does not have a dedicated national ID field in its Candidate module; if the customer requires ID tracking, a custom field should be created in Zoho Recruit and populated manually for compliance-sensitive roles.

Dayforce Time Off Balances, accrual rates, carryover rules, and negative balance tolerances are HCM payroll features with no ATS equivalent in Zoho Recruit. These records are out-of-scope and should be managed in Dayforce or a replacement payroll system if Dayforce is being decommissioned for HCM purposes.

Dayforce Legal Entities represent the legal employer structure for multi-jurisdiction payroll compliance. This has no ATS equivalent in Zoho Recruit. Legal entity structure is documented as out-of-scope and should be reviewed with the customer's HR and legal teams if Dayforce is being replaced entirely.