Migrate from Workable Zone - HRM to Zoho Recruit

Workable Candidates map directly to Zoho Recruit Candidates. We use Workable's bulk API export endpoint to extract full candidate profiles including resume binaries and communication history; the standard CSV export omits attachments by design. First Name, Last Name, Email, Phone, Current Title, Current Company, Source, and Pipeline Stage map 1:1. The Zoho Recruit Data Migration wizard requires Last Name as mandatory; records without a Last Name value in the source are flagged and set to 'not provided' per Zoho's import specification.

Resume binaries, cover letters, portfolio files, and candidate documents are extracted via Workable's bulk API and reattached to the corresponding Zoho Recruit Candidate record. Zoho's Data Migration wizard does not handle binary attachments; we inject them via the Zoho Recruit REST API using the Attachments endpoint per candidate record after the primary field import completes.

Workable Job Postings map to Zoho Recruit Job Openings. We audit active job count during scoping because Zoho Recruit caps active jobs by plan tier: 1 on Forever Free, 10 on Standard, 100 on Professional, 250 on Enterprise. If the customer's Workable account has more active jobs than the target Zoho plan allows, we flag the delta and recommend upgrading before migration. Job description, location, department, hiring manager, and job status (open/closed/draft) migrate directly.

Workable pipeline stages map to Zoho Recruit candidate stages. We preserve stage names, order, and the probability or weight values if configured in Workable. Zoho Recruit stages are configurable via Setup > Recruitment > Candidate Stages; we add any Workable stages that do not have a Zoho default equivalent before migration and reconcile any stage consolidation during scoping if the customer's pipeline has more stages than Zoho supports.

Workable interview scorecards and evaluator feedback stored on the candidate record map to Zoho Recruit's interview feedback fields. Structured rating fields migrate as numeric or picklist values. Rich-text evaluation body migrates to the Zoho Interview Notes field. We flag any scorecard templates that rely on Workable-specific rating scales for the admin to re-create in Zoho.

Workable offer records map to Zoho Recruit Offers, preserving offer status (pending/accepted/declined), compensation details (salary, bonus, equity if stored as structured fields), and start date. Offer letter documents are extracted as binaries from Workable and reattached to the corresponding Zoho Offer record via the API after primary field import. Offer templates and branding do not migrate; these require manual re-creation in Zoho Recruit's offer letter builder.

Workable Employee records (from the HRIS module) require the Zoho People integration to route correctly. We migrate employee data to Zoho People as the HRMS destination, with a link back to the corresponding Candidate record in Zoho Recruit when a hire is made. Fields including First Name, Last Name, Email, Job Title, Department, Start Date, Manager, Skills, and custom properties map to Zoho People fields. Time-off balances migrate as records in the Zoho People Time-Off module for audit purposes. If Zoho People is not in scope, employee data is migrated as Candidates in Zoho Recruit with a 'Hired' status flag for the admin to convert later.

Workable leave and time-off balance records export for audit purposes. We migrate balance snapshots as historical time-off records in Zoho People if the HRMS integration is in scope. We do not reconcile balances against a payroll export; any forward-looking accrual logic requires manual configuration in Zoho People time-off policy settings post-migration.

Workable custom properties on Candidates, Employees, and Jobs require pre-creation in Zoho Recruit before migration begins. We audit all custom properties during scoping, note their field types (text, number, date, dropdown, boolean, multi-select), and create matching fields in Zoho Recruit via Setup. Dropdown and multi-select fields require a value list to be defined before migration because Zoho enforces picklist whitelists on import. Field-type mismatches (e.g., a Workable free-text field containing comma-separated values that should map to a Zoho multi-select) are flagged during scoping for the admin to resolve.

Workable interview records including scheduled date/time, interviewer, interview type, and outcome map to Zoho Recruit Interview records linked to the Candidate. Interviewer assignments migrate by email resolution against Zoho Recruit User records. Self-scheduled interview configurations do not transfer; these require re-configuration in Zoho Recruit's calendar integration settings post-migration.

Workable candidate communication history (emails, internal notes, activity log entries) migrates to Zoho Recruit's Activity timeline on the Candidate record. Each activity maps with its timestamp, type, author, and content. Zoho Recruit's Activity module supports Notes, Emails, and Tasks; generic activity log entries migrate as Notes with a system-generated author attribution.

Workable Owners and Hiring Team members on Jobs and Candidates map to Zoho Recruit User records. We resolve by email match. Any Workable Owner without a matching Zoho Recruit User is placed in a reconciliation queue; the customer's admin provisions the User before record migration proceeds. User provisioning must complete before Candidate and Job import because OwnerId is a required reference on many Zoho modules.