Migrate from Harri to Zoho Recruit

Harri Workers are a unified record type covering both active employees and job applicants. We split Workers at migration time using Harri's employment_status field: Workers with status of applicant or candidate map to Zoho Recruit Candidate; Workers with status of active, inactive, or terminated map to Zoho Recruit Contact. We preserve the original Harri Worker record as a custom field harri_worker_id__c on both the Candidate and Contact for audit traceability and cross-reference during the reconciliation phase.

Harri Positions define job listings within a Location, including job title, pay rate, FT/PT/seasonal classification, and department. Positions map 1:1 to Zoho Recruit Job records. Position title becomes the Job Name; pay rate migrates to a custom Currency field on the Job; FT/PT/seasonal classification becomes a picklist field. Each Job is linked to the corresponding Candidate records that applied during the Hiring Pipeline phase. Position hierarchies within a Location are flattened during migration because Zoho Recruit Jobs do not support hierarchical nesting.

Harri Locations represent individual restaurant or hotel properties with their own managers, position catalogs, shift rules, and compliance settings. Zoho Recruit has no native location or property management module; the Client module holds organizational entities (staffing agencies' client companies). We map Harri Locations to Zoho Recruit Client records using a custom Location Address field and a harri_location_id__c cross-reference field. Multi-location customers should decide during scoping whether to use the Client module for properties or maintain a Locations custom field on Job records. This decision affects downstream reporting and filter logic in Zoho Recruit.

Harri Applications track candidate submissions for Positions, including application date, source, pipeline stage, and interview scores. In Zoho Recruit, the candidate record is the primary applicant record; Applications do not have a separate object. We attach Application metadata (source, stage, score, notes) as a JSON-encoded or text custom field on the Zoho Recruit Candidate, preserving the original Harri application date and stage name. Pipeline stage names from Harri map to Zoho Recruit Candidate Status values, which are configurable per client during schema setup.

Harri Shifts are time-block records assigned to Workers at a Location with start/end times, shift type, and coverage requirements. Zoho Recruit is an ATS and recruitment CRM with no native scheduling module. Shift records have no target in Zoho Recruit and are explicitly excluded from migration scope. Customers who need shift scheduling post-migration should evaluate Zoho Shifts (a separate Zoho product) or a dedicated scheduling tool. We flag shift exclusion in the scope document and recommend the customer export shift patterns from Harri before termination as a CSV reference for manual re-entry or scheduling-tool setup.

Harri stores structured onboarding task checklists tied to new-hire Workers, including task name, completion status, due date, and custom task fields. We migrate completed and pending onboarding tasks as Zoho Recruit Task records linked to the Candidate (representing the hired employee). Task names, statuses, and due dates migrate directly. Custom onboarding task fields map to custom fields on the Task object. Onboarding workflow logic does not migrate; we deliver a written inventory of Harri onboarding workflows for the customer's admin to rebuild using Zoho Recruit's workflow automation or Zoho Flow.

Harri Compliance Records track certification expiry dates, mandatory training completion, and regulatory acknowledgements tied to Workers. Zoho Recruit has no native compliance tracking module. We migrate compliance records as custom fields on the Zoho Recruit Candidate: certification_name, certification_expiry_date, and training_completion_status. Supporting documents (certification scans, training certificates) migrate as file attachments on the Candidate record, preserving the original filename and upload timestamp. We flag that ongoing compliance monitoring requires a Zoho product outside Recruit (Zoho People for CoreHR compliance modules) or a third-party compliance tool.

Harri stores employee documents including contracts, ID scans, and policy acknowledgements attached to Worker records. We migrate these as file attachments on the corresponding Zoho Recruit Candidate or Contact. Files are exported from Harri as binary exports, mapped to the target record by harri_worker_id__c, and uploaded via Zoho Recruit's file attachment API. File types, original filenames, and upload dates are preserved. PDF and image file attachments are supported; we do not migrate file versions or document version history.

Harri's employee engagement and pulse survey module stores response data tied to its internal engagement engine. There is no documented export mechanism for engagement survey responses, and Zoho Recruit has no engagement survey module. Engagement survey data is excluded from migration scope. Customers who need historical engagement data should export it manually from Harri's UI before termination. This data will not appear in the standard data export.

Harri does not process payroll natively for most U.S. customers; payroll data lives in the integrated third-party payroll provider. Pay rates attached to Harri Positions migrate to custom fields on Zoho Recruit Job or Candidate records as a reference, but historical earnings, deductions, pay stubs, and tax withholdings are not stored in Harri and are not migrated. Customers export historical payroll data from their payroll provider separately and map it into their chosen payroll system post-migration.

Harri Owners represent users who own Workers, Positions, Applications, and Shifts (typically managers or recruiters). We extract distinct Owner records from Harri and map them to Zoho Recruit User records by email match. Any Harri Owner without a matching Zoho Recruit User is held in a reconciliation queue for the customer's Zoho admin to provision before Candidate and Job import begins. Owner assignment on migrated records (Candidates, Jobs) uses the Zoho Recruit OwnerId field.

Harri supports custom properties on Worker records that vary by customer configuration. Zoho Recruit supports custom fields on Candidates from all paid editions (Standard, Professional, Enterprise); custom fields are not available in the Free Edition. We pre-create custom fields in Zoho Recruit during schema design, mapping Harri field types to Zoho Recruit equivalent types: text to Single Line, numeric to Big Integer or Currency, date to Date, checkbox to Checkbox, picklist to Picklist. Lookup fields in Harri require a custom module or relationship configuration in Zoho Recruit during schema setup.