Migrate from Workable to Zoho Recruit

Workable Candidate records map to Zoho Recruit Candidates. Zoho requires Last Name as a mandatory field on every Candidate; Workable candidates with no last name (e.g., anonymous applicants) receive a placeholder value ('Not Provided' or similar) during import. We preserve the Workable candidate ID as a custom field for audit traceability and store communication history, tags, and source attribution in Zoho Recruit's corresponding Candidate fields.

Workable Jobs map to Zoho Recruit Job Openings with job title, description, department, location, and status preserved. We flag active versus closed versus archived status at migration time. Zoho's job opening limits are tier-dependent (1 on Free, 100 on Standard, 250 on Professional, 750 on Enterprise); we verify the destination plan supports the migrated job count before import.

Workable pipeline stages are per-job with candidate counts and movement history. We map each stage name and sequence to a corresponding Zoho Recruit stage in the candidate pipeline. Stage behavior differs: Workable stages can carry custom gating rules per plan tier, while Zoho Recruit stages are configurable via the candidate pipeline UI without tier gating. We document the original stage probabilities for the customer's admin to reapply in Zoho if needed.

Workable Interviews link to Candidates and Jobs with scheduling data, interviewer assignments, and meeting type preserved. We migrate interview dates, times, location or video link, and interviewer names. Zoho Recruit's Interview module supports structured feedback forms, which map from Workable Scorecards.

Workable interview scorecards (structured evaluation templates with ratings and written feedback) map to Zoho Recruit Interview Feedback Forms. Rating scales may differ: Workable uses configurable numeric scales per scorecard while Zoho uses a standard scale per form. We normalize the scale during transform and preserve the original Workable numeric rating in a custom field for reporting continuity.

Workable Offers store compensation details, start dates, and status (accepted, declined, retracted). We preserve the full offer record including any attached offer letter documents. Status transitions migrate as lifecycle flags on the Zoho Candidate record. Offer PDF attachments are handled as Zoho Recruit document attachments on the Candidate.

Workable Talent Pools are customer-created groupings of candidates. Zoho Recruit has no direct Talent Pool object; we map pool membership to Tags on the Candidate record. The pool name becomes the tag label. If the customer uses Talent Pools extensively, we recommend a pre-migration tagging strategy to preserve pool semantics as searchable tags in Zoho.

Workable recruiters, hiring managers, and collaborators assigned per job map to Zoho Recruit Users with corresponding roles (Recruiter, Hiring Manager, Interviewer). We match by email. Any Workable team member without a matching Zoho Recruit User goes to a reconciliation queue for the admin to provision before record import completes.

Workable custom candidate fields migrate to Zoho Recruit custom fields. We audit all custom field names, types, and picklist values during scoping and create equivalent Zoho fields before import. Custom field behavior differs: Workable custom fields on Candidates apply at the candidate level while Zoho Recruit custom fields can be module-scoped; we configure the field visibility per Zoho's field management rules.

Workable custom job fields map to Zoho Recruit custom fields on Job Openings. Job-level custom fields in Workable may control pipeline behavior or display logic; Zoho Recruit custom fields on Job Opening are display-only unless paired with a Workflow Rule for automation. We document any behavioral custom fields for the customer's admin to re-implement as Workflow Rules post-migration.

Resume files are extracted separately from Workable candidate profile data via the /candidates/{id}/resume endpoint. They are re-associated during Zoho Recruit import as Candidate resume attachments. Workable's CSV export does not include resume files; this is a separate extraction step that adds time for candidate-heavy migrations. File naming conventions are preserved where possible.

Workable's HRIS layer includes Employees, Departments, and Time-Off Records on Standard and above plans. Zoho Recruit is primarily an ATS and recruiting CRM; it does not have a full HRIS equivalent. Employee records and org structure migrate as Candidate records if the use case is internal mobility, but general HRIS data (time-off balances, employment status, payroll) does not have a native Zoho Recruit destination and is flagged for the customer to handle separately or in a dedicated HRIS.