Migrate from HiBob HRIS to Zoho Recruit

HiBob employee records migrate to Zoho Recruit Candidate module via the Corporate HR edition. Core fields (first name, last name, email, phone, address, hire date, employment status, department) map directly. HiBob's system-assigned employee ID becomes a custom field hibob_employee_id__c for audit. Last Name is mandatory in Zoho Recruit; any HiBob employee without a last name value is mapped to 'not provided' per Zoho Recruit's migration documentation. Status in HiBob (active, archived, onboarding) maps to Candidate Status with active employees marked as 'Active' and archived as 'Rejected' by default, confirmed during scoping.

HiBob custom fields on the Employee object migrate to Zoho Recruit Candidate custom fields. List-type custom fields in HiBob return internal string IDs rather than display values; we resolve these against HiBob's list metadata endpoint before mapping to Zoho Recruit picklist or multi-select fields. Custom field type conversion is applied: HiBob text fields map to Zoho Recruit single-line text, date fields to Zoho Recruit date fields, and boolean flags to Zoho Recruit checkboxes. If a list definition changed between extraction and migration, orphaned values are flagged for manual resolution.

HiBob's Job Catalog API exposes job roles, job families, and job family groups. These map to Zoho Recruit Job Openings, with the job role title populating the Job Title field. Job family becomes a custom field or maps to the Department if Zoho Recruit's department structure is used. Active job openings from HiBob's Workforce Planning module become candidates for import into Zoho Recruit's active job pipeline. Closed positions migrate as historical records if the customer requests it.

HiBob positions link employees to job profiles with budget and opening data. The position title and employment type (full-time, part-time, contractor) map to Zoho Recruit Candidate fields. Manager relationships from HiBob's position data become a custom field reporting_to__c or a lookup if the destination org uses Zoho People alongside Zoho Recruit with shared user records.

HiBob's Time Off API provides leave balance snapshots and request history. We migrate balance amounts as of the migration date to Zoho Recruit's leave records in the Corporate HR module. Pending approvals at migration time are flagged in a separate reconciliation sheet because Zoho Recruit's leave module does not have a native approval workflow equivalent for imported balances. Leave type labels from HiBob (Annual, Sick, Personal) map to Zoho Recruit leave types; any HiBob leave types without a Zoho Recruit equivalent require new leave type configuration before migration.

HiBob exposes document metadata via API; attachment binaries require a separate download step. We extract offer letters, employment contracts, and identification documents as binary files and attach them to the corresponding Zoho Recruit Candidate record. Zoho Recruit supports file attachments on candidates via the Document Library or direct attachment upload. We use Zoho Recruit's bulk attachment API to batch-upload documents per candidate. Documents without a valid candidate match go to a quarantine queue.

HiBob's org chart derives from employee reporting relationships on the Employee object. We extract the full reporting tree and map it to Zoho Recruit's department structure. Departments are created first in Zoho Recruit, then employee-department assignments are set during candidate import. Reporting-line relationships that exceed Zoho Recruit's flat department model are preserved as a custom field chain_of_command__c holding the full management path as a text string for reference.

HiBob performance review cycles (PDRs) with ratings, goals, and review text have no native equivalent in Zoho Recruit. We export review records to a structured assessment migration file and provide a written specification for configuring Zoho Recruit Assessments module to hold historical ratings. Reviewer names, review dates, overall ratings, and written feedback migrate as Assessment records attached to the candidate. If the customer does not license Zoho Recruit Enterprise with Assessments, we document the fields for manual re-entry.

HiBob's Goals API stores OKR hierarchies and key result progress. Zoho Recruit has no native goals or OKR module. We export goal data to a CSV structured for Zoho Recruit's custom field capability, mapping goal titles to a multi-line text field and key results to individual task records under the candidate. If the customer requires OKR tracking post-migration, we recommend Zoho People as a complementary module or a dedicated OKR tool like Profit.co integrated separately.

HiBob compensation bands, salary structures, and compensation history are accessible via employee profiles and reporting. We extract current salary, compensation band, and pay frequency as custom fields on the Zoho Recruit Candidate record. Historical compensation changes are not supported in Zoho Recruit's flat candidate model; we export this to a separate compensation history CSV for the customer's records. Note that Zoho Recruit is not a payroll platform; compensation data is reference information only and does not drive payroll.

HiBob onboarding workflows with configurable templates and task assignments are exportable as task lists. Zoho Recruit does not have a native onboarding flow builder. We export active onboarding task configurations and assignees as Zoho Recruit Tasks linked to the candidate, with task completion status preserved. The workflow builder, conditional logic, and automated reminders require manual rebuild in Zoho Recruit; we provide a written onboarding workflow specification document for the customer's admin.

HiBob engagement survey templates, response history, and aggregated engagement scores have no equivalent in Zoho Recruit. We export survey templates and response summaries as a written inventory document with screenshots and JSON exports of survey structure. The customer's HR team uses this inventory to reconfigure surveys in a dedicated survey tool (Culture Amp, Lattice, or the embedded survey capability in Zoho People if licensed). Survey response history is sensitive employee data; we deliver it as an encrypted file to the customer's HR lead for internal handling.