Migrate from Workday HCM to Zoho Recruit

Workday Workers map to Zoho Recruit Candidates. The Worker's legal first name and last name map to Zoho Recruit's First Name and Last Name fields; these are mandatory in Zoho and records without a last name are skipped during import. We pre-flag any Worker records missing a last name and supply 'Not Provided' as a default value during transform. Email, phone, address, and employment status migrate to the corresponding Zoho Recruit Candidate fields. The Worker's worker_type (employee, contractor, contingent worker) is preserved in a custom field for segmentation.

Workday Job Profiles (skills, qualifications, competencies tied to a Position) map to Zoho Recruit Job Openings. The job title, description, and required skills migrate to the Zoho Recruit job fields. Competency ratings and profile categories map to custom Candidate fields if the customer's Zoho Recruit instance has skills taxonomy configured. Job Profiles with no associated Position still generate a Zoho Recruit Job Opening as a standalone requisition.

Workday Positions define the organizational 'boxes' independent of who holds them, with job classifications and supervisory org linkage. Zoho Recruit does not have a position object; we map Positions to Zoho Recruit Departments for organizational context and optionally to custom Role picklist fields. Multi-level position hierarchies are flattened into one level of department membership in Zoho Recruit.

Workday Supervisory Organizations define manager-to-worker chains and reporting hierarchies. We extract the supervisor chain and map it to Zoho Recruit's department structure or to the Agency hierarchy if the customer is a staffing firm. Recursive org trees are flattened to a single parent-child level because Zoho Recruit does not support multi-level org hierarchies. Manager assignments become the Hiring Manager field on Job Openings and the Assigned Recruiter field on Candidates.

Workday Organizations (cost centers, business units, regions) form a hierarchical graph. Zoho Recruit uses a flat department list. We map the top-level Workday Organizations to Zoho Recruit Departments, and subordinate org units to custom department-level fields. The full hierarchy is preserved in a migration artifact document for future reference or for import into Zoho People if the customer adopts a full HRMS later.

Workday Worker documents (offers, contracts, performance reviews, resumes if stored in Workday) are stored as attachments against the Worker object. We export documents as binary blobs with their document category and attach them to the corresponding Zoho Recruit Candidate record. Document category maps to a Zoho Recruit custom picklist (Offer Letter, NDA, Resume, Performance Review) so the customer can filter by type. Files are uploaded via Zoho Recruit's attachment API during the document phase of migration.

Workday Custom Objects are tenant-locked user-defined extensions tied to Worker or Position. We discover the full custom object graph via Workday WQL API before migration. Each discovered Custom Object is evaluated: if a matching Zoho Recruit custom field exists (same data type and acceptable value range), we map to that field; if no match exists, we create a custom field in Zoho Recruit's Setup. Custom objects with complex multi-field structures may require a Zoho Recruit Custom Module, which we pre-create before data load. Undiscovered custom objects result in data loss; WQL discovery mitigates this risk.

Workday Job Profile attributes (skills, certifications, competencies, qualifications) map to Zoho Recruit's Skills list. Skills are stored as individual values in Zoho Recruit's skills module and linked to Candidates and Job Openings. Competency ratings from Workday map to numeric custom fields on the Candidate if the customer's Zoho Recruit instance supports custom field ratings. We deduplicate skill values during transform to avoid creating duplicate entries in the Zoho Recruit skills list.

Worker's primary contact details (email, phone, mobile, address) map to the corresponding Zoho Recruit Candidate fields. Multi-email addresses on a Workday Worker are consolidated: the primary email goes to the primary field and secondary emails go to a custom text field. Physical addresses with country-specific formatting are normalized to a single-line address format compatible with Zoho Recruit's address field structure.

If Workday stores employment history as a related record set on the Worker (previous employers, job titles, dates), we map each employment event to a Zoho Recruit Candidate's Work History entries. Job title, company name, start date, end date, and description migrate. Employment history without an explicit Workday object is captured from the Candidate's resume parsing during the Zoho Recruit onboarding phase.

Workday education records (degree, institution, field of study, graduation date) map to Zoho Recruit Candidate education entries. Education records without an explicit Workday object follow the same path as employment history: captured from resume parsing in Zoho Recruit post-migration.

Workday Benefits Enrollment records (benefit plan elections, coverage tiers, dependent information, effective dates) have no equivalent in Zoho Recruit. Zoho Recruit is an ATS and does not contain benefit plan, health plan, or dependent management objects. We document each Workday benefit plan and enrollment as a CSV export delivered alongside the migration, flagging that this data must move to a separate HRMS (Zoho People, Workday HCM retained module, or another benefits platform) if benefits data continuity is required. We do not load benefit data into Zoho Recruit.

Workday effective-dated pay changes, bonuses, stock grants, and compensation entries tied to a Worker have no destination in Zoho Recruit. Zoho Recruit does not have a compensation, payroll, or salary object. We export compensation history as a dated CSV with worker ID, effective date, compensation type, amount, and currency. This export is delivered as a migration artifact for the customer's payroll or finance team to load into their payroll system or retained HRMS module. We do not load compensation records into Zoho Recruit.

Workday payroll summaries (gross pay, deductions, taxes, net pay, direct deposit) are available via payroll reporting APIs with Payroll system role access. Zoho Recruit has no payroll object and cannot receive this data. We deliver payroll summaries as a structured CSV export (pay period, worker ID, gross, deductions, net, currency) as a migration artifact. We flag that payroll data requires a dedicated payroll migration scope if the customer is also moving off Workday payroll. Historical payroll data export requires payroll-reader API credentials; we verify access before scoping.

Workday leave accruals, balances, pending requests, and accrual plan configurations have no equivalent in Zoho Recruit. Zoho Recruit does not contain time-off tracking, absence management, or accrual calculation. We export leave balances and pending requests as a CSV deliverable. The customer must adopt Zoho People (if staying in Zoho ecosystem) or another HRMS for time-off management. Leave balances are out of scope for the Zoho Recruit migration.