Migrate from HROne to Zoho Recruit

HROne Employee records map to Zoho Recruit Candidate records. Core fields (name, email, phone, department, employment type, joining date) migrate directly. HROne's per-employee custom fields require a custom-field audit step: we compare the API export against a UI export because instance-specific custom fields are not always in HROne's public API. We create matching custom fields in Zoho Recruit (paid editions only; Free Edition does not support custom fields) before import. The original HROne employee ID is preserved in a custom field hrone_employee_id__c for audit trail. Note: Zoho Recruit Candidate is the pre-hire record; after hire, the candidate-to-employee bridge is handled by the native Zoho Recruit-to-Zoho-People integration, which we configure as a post-migration step.

HROne employee records with rich employment history (previous employer, past titles, education, certifications) require a split: the base profile maps to Candidate, and structured employment-history entries map to a Zoho Recruit custom module linked via Lookup. This approach preserves the depth of HROne's employment data within Zoho Recruit's candidate record structure. We create the custom module, its fields, and the Lookup relationship during the schema design phase before any data import.

HROne Job Openings map directly to Zoho Recruit Job Openings. Fields (job title, department, location, employment type, hiring manager) migrate directly. HROne's compensation range field maps to Zoho Recruit's salary range custom field if configured. Owner from HROne maps to the Zoho Recruit Candidate Owner field. Job status (active, on-hold, closed) migrates to Zoho Recruit Job Opening status. Post-migration, we validate that open job counts match between HROne and Zoho Recruit before closing the HROne source.

HROne applicant records map to Zoho Recruit Candidates linked to their respective Job Opening records via the Candidates_For_Jobs related list. Applicant status (applied, shortlisted, interview, offer, rejected, hired) maps to Zoho Recruit Candidate status values. Source tracking (referral, job board, direct) migrates to Zoho Recruit's Candidate Source field. Interview scores and recruiter ratings migrate to custom fields in Zoho Recruit if the paid Enterprise edition is in use; Standard Edition does not support all rating field types.

HROne departments and cost centers map to a Zoho Recruit custom picklist field on Job Opening (Department) or to a Department Lookup module if the customer uses Zoho Recruit Enterprise. We configure the picklist values during schema setup, mapping each HROne department to its Zoho Recruit equivalent. The reporting hierarchy (manager relationships) from HROne is preserved as a custom field or note on the Candidate record for reference during hiring.

Clock-in/out logs, shift assignments, and overtime records in HROne have no equivalent module in Zoho Recruit. This data does not migrate. We document it as out-of-scope and recommend the customer pair Zoho Recruit with Zoho People for attendance tracking. If attendance data is relevant to the recruitment context (e.g., shift-based hiring), we store the most recent attendance status as a custom field on the Candidate record, but this is a scoped partial migration, not a full attendance transfer.

Leave entitlements, accrual policies, and current balances in HROne have no equivalent in Zoho Recruit's ATS data model. This data does not migrate. We recommend the customer migrate leave management to Zoho People or retain it in HROne if payroll and leave remain on the HROne platform while only recruitment migrates to Zoho Recruit. We document the leave-type schema from HROne as a reference for Zoho People setup.

HROne compensation records (salary structures, pay components, compensation history) partially map to Zoho Recruit's candidate salary expectation field and custom compensation fields. Deep pay structure data (separate allowances, deductions, variable pay) does not have a native equivalent in Zoho Recruit; we create custom fields to capture the most recent compensation data and document the full compensation schema for the customer's records. Payroll runs and historical salary data remain in HROne or migrate to Zoho People separately.

HROne employee documents (offer letters, employment contracts, ID proofs) associated with candidates in the recruitment pipeline migrate as Zoho Recruit attachments on the Candidate record. We extract the file binary and filename from HROne's DocumentTemplate export, validate file size against Zoho Recruit's attachment limits, and re-attach to the corresponding Candidate record. Documents stored for employees not yet in a recruitment context do not migrate to Zoho Recruit and are documented for a Zoho People migration scope.

Goals, appraisal cycles, and review ratings in HROne's performance module do not map to Zoho Recruit. Zoho Recruit is an ATS and does not support performance management. We document the performance schema (appraisal dates, reviewer assignments, rating scales) from HROne as a written handoff for the customer's next HRMS selection. If the customer selects Zoho People as the post-recruit HRMS, the performance data is migrated in a separate engagement.

HROne organizations frequently add custom fields capturing region-specific, policy-specific, or industry-specific data on the Employee and Recruitment modules. These fields are not consistently exposed via HROne's public API. We run a dual-export discovery: we request both the API export and a UI export from the customer, compare field counts, and flag any discrepancy as a custom-field audit item. Custom fields are then created in Zoho Recruit (Standard Edition and above) with matching data types (picklist, multi-select, text, date, number) before mapping finalizes. Note: custom fields are not available in Zoho Recruit Free Edition, so edition selection is confirmed during discovery.

HROne Owner records (hiring managers, HR admins, recruiters) map to Zoho Recruit User accounts. We resolve by email match. Any HROne Owner without a matching Zoho Recruit User is placed in a reconciliation queue; the customer's Zoho admin provisions the missing accounts before the production migration phase. Owner assignment on Job Openings (hiring manager) and Candidates (recruiter) migrate to Zoho Recruit's Owner and Candidate Owner fields respectively. Team-based hiring (multiple owners per job) maps to Zoho Recruit's sharing rules or a custom module if the Enterprise edition is in use.