Migrate from Workday Recruiting to Zoho Recruit

Workday Supervisory Organizations form the org chart hierarchy and are a prerequisite for every Position write. Zoho Recruit has a flat department structure without the supervisory chain concept. We map each Workday Supervisory Organization to a Zoho Department using the org chart data you provide, preserving the hierarchical parent-child relationship as a department Parent Department reference where supported. This is the first object we migrate because Zoho Jobs must reference a Department at creation time.

Workday Positions represent headcount slots and must belong to a Supervisory Organization. Zoho Recruit does not have a separate Position object; jobs are created independently. We map Workday Position records to Zoho Job records with the Position's job title, FTE, and headcount flags preserved in Zoho job custom fields. Position supervisory relationships are reconstructed as Zoho department assignments on the linked Job.

Workday Job Requisitions map directly to Zoho Jobs. Standard fields including job title, department, location, employment type, and requisition status transfer cleanly. Confidential Requisitions in Workday map to Zoho Jobs with a private/internal visibility flag we set via custom field. Open requisition date and projected start date migrate as Zoho custom date fields.

Workday Candidates are the talent pool entity, distinct from Workers. We map Candidate records to Zoho Candidate records with all standard fields (name, email, phone, address, source, skills). Workday's Candidate ID becomes a custom field wd_candidate_id__c for cross-system audit. Candidate availability status and referral source data migrate as custom fields in Zoho.

Workday ties each application to a single Requisition without a native multi-application chain. Source ATS platforms migrating into Workday commonly had multi-application candidates, but this pair is Workday-as-source, so each Workday Job Application maps to a separate Zoho Candidate record tagged with the original Workday application date, requisition, and stage. The full Workday application history for a given candidate is serialized as a structured note on each Zoho record for audit continuity.

Workday Interview Kits define structured interview plans and question banks with scheduled evaluator assignments. Zoho Recruit does not have a native Interview Kit template object. We map Workday Interview Kit records to Zoho Interview activity records with the kit name, planned duration, and evaluator list preserved as structured text in the interview description. We flag which Interview Kit templates require manual recreation in Zoho's interview scheduler.

Workday Scorecards are tied to specific evaluators and submitted against an Interview Kit. Source Workday scorecards may contain structured rating data across defined competencies. We map evaluator name, overall rating, and competency scores to Zoho custom fields on the Candidate record (or to custom fields on a linked Evaluation custom module). Free-form evaluation text that does not fit the rating model migrates as a Zoho Candidate Note.

Workday free-form notes attached to a Candidate or Application map directly to Zoho Candidate Notes, preserving author name and timestamp where available. Note type (recruiter note, hiring manager note, system note) maps to a Zoho Note Category custom field for downstream filtering.

Background check records are not a first-class Workday Recruiting object by default; they typically live as attachments or via a third-party integration (HireRight, Checkr). We migrate background check PDFs as native Zoho Candidate attachments and set a custom field bg_verification_status__c to Flag for Manual Review so your team can complete verification in Zoho's verification workflow after migration.

Workday generates offer letters via business processes tied to the Requisition. Migrated offer letters from Workday are loaded as approved offer records or as PDF attachments to the Zoho Candidate record. Offer amount, start date, and offer status migrate to Zoho custom fields on the Candidate so that offer history is queryable post-migration.

Workday Workers are created when a hire is finalized via the Revise Hire business process and are distinct from Candidates. We map Worker records flagged as currently active to Zoho Candidates with an employee_status__c custom field set to Active Hire and the original Workday Worker ID preserved in a custom field. Inactive Workers are mapped as inactive Zoho Candidates for historical completeness.

Workday Custom Objects extend the core schema (Worker, Position, Candidate, etc.) to capture company-specific recruiting data. Zoho Recruit supports custom modules configurable via Zoho Creator or built-in ATS custom fields. We pre-create the destination custom module schema, including all custom fields and lookup relationships, before any data import. Any Workday Custom Object lookup dependencies that reference standard objects (Position, Requisition) require those standard objects to be migrated first to satisfy the foreign key.

Workday stores resume attachments against the Candidate object. Resume files served via signed S3 URLs or temporary blob URLs in Workday expire after export. We download all accessible resume files at migration time, verify reachability before export window closes, and re-upload them as native Zoho Candidate attachments. Any records where the original URL is no longer reachable are flagged with a missing_document__c flag so you can request documents directly from candidates or from Workday before the account is closed.

Workday tracks candidate sources (Employee Referral, Job Board, Direct Sourcing) at the Requisition and Application level. These migrate as Zoho Candidate Source values (Employee Referral, Job Portal, LinkedIn, Agency, Direct) preserved on the Candidate record. Historical source attribution from Workday Job Applications is transferred to the corresponding Zoho Candidate records.