Migrate from HROffice to Zoho Recruit

HROffice Candidates map directly to Zoho Recruit Candidates. Standard fields including name, email, phone, current title, and application status migrate as typed fields. The HROffice application history (all Applications a candidate has submitted) migrates as related list entries on the Candidate record. Candidates with no Last Name in HROffice require pre-fill with 'Not Provided' before import because Zoho Recruit treats Last Name as a mandatory field on Candidate; records without this field are ignored during import per Zoho Recruit's data migration documentation.

HROffice Applications represent a Candidate's submission to a Job Posting. Each Application links to a Job Opening in Zoho Recruit via the Candidate's application history. The application date, status pipeline position, and recruiter notes migrate as properties on the Candidate record or as notes attached to the Job Opening. If a Candidate in HROffice has multiple active Applications to different Job Postings, each migrates as a separate Candidate-to-Job Opening relation in Zoho Recruit.

HROffice Job Postings map to Zoho Recruit Job Openings with the posting title, description, department, location, and employment type preserved. Employer branding and custom career site formatting do not migrate as design elements; only the text content and metadata transfer. Job status (active, closed, draft) maps to Zoho Recruit's Job Opening status field. Active job limits by plan tier (10 per recruiter on Standard, 20 per recruiter on Professional, 750 on Enterprise) should be validated during scoping to ensure the target Zoho Recruit plan accommodates the customer's open job volume.

HROffice Assignments (temporary placements, temp-to-perm arrangements, direct hire placements) have no native Zoho Recruit equivalent. We create a custom module named 'Assignments' or attach Assignment properties as custom fields on the Candidate record. The custom fields capture assignment type, start date, end date, client company name, pay rate, and weekly hours. This approach preserves the full staffing history without forcing assignment records into a standard employment model that would create duplicate or conflicting records.

HROffice Timecards record weekly hours submitted by temporary workers on assignment. Zoho Recruit has no native timecard object. We export timecard history as records in a custom module (with Date, Hours, Candidate reference, and Assignment reference) or as a serialized custom field on the Candidate record. The approach depends on the customer's reporting needs; a custom module enables timecard reporting within Zoho Recruit while a custom field approach is simpler but limits reporting depth.

HROffice internal Users (recruiters, administrators) map to Zoho Recruit Users. Resolution is by email address. A known migration blocker: Zoho Recruit will not import Users who already have a separate Zoho Recruit account. These users must close their individual Zoho Recruit account before the migration CSV is processed. We identify conflicting accounts during scoping and provide the customer with a list of actions required before user migration begins. Role-based permissions (recruiter, admin) map to Zoho Recruit profiles and roles.

HROffice benefit enrollment records (plan name, enrollment date, coverage type) have no standard Zoho Recruit equivalent. We export benefit data as custom fields on the Candidate record or as records in a custom Benefits module with lookup to Candidate. The specific benefit fields depend on what HROffice exposes via its API or export; benefit data is typically supplemental to the core ATS migration scope and is addressed based on customer priority during scoping.

HROffice compensation records (pay type, hourly or salary rate, effective dates) migrate to custom fields on the Candidate record. The standard Zoho Recruit Candidate module does not include a native compensation field. We create fields for Pay Type (picklist: Hourly, Salary, Contract), Pay Rate (currency), and Effective Date. If the customer also licenses Zoho People, compensation data may be better migrated there as part of a separate Zoho People scope; we flag this during scoping if the customer has a combined ATS/HRIS use case.

Free-text notes and recruiter comments attached to HROffice Candidates migrate as Zoho Recruit Notes linked to the Candidate record. Notes preserve the original author, timestamp, and text content. If the customer uses HROffice's candidate rating or scoring feature, we migrate the score to a custom Candidate field rather than a native Zoho Recruit field, since Zoho Recruit's standard Candidate object does not include a built-in candidate scoring field.

HROffice source tracking (referral, job board, direct application, career site) migrates to Zoho Recruit's Candidate Source picklist field. Source attribution (which job board, which referral program) migrates to a custom text field if the HROffice data captures source-specific detail beyond the broad category. Source Booster usage statistics from HROffice, if available via API, migrate as supplemental metrics on the Job Opening or as campaign-related custom fields.

HROffice's built-in branded career website builder and employer branding content tied to Job Postings do not migrate as design assets. The job posting text content transfers; the career site template, branding, and visual layout do not. We flag these elements in the migration scope document and recommend that the customer rebuilds their career site using Zoho Recruit's native career site builder (available on all paid tiers) post-migration, or exports their HTML assets for manual redeployment.

Resume and CV files attached to HROffice Candidates migrate as attachments on the corresponding Zoho Recruit Candidate record. Zoho Recruit's resume parsing (available on Standard and above, 250 resumes/day on Standard, unlimited on Professional and Enterprise) can re-parse imported resumes to populate Candidate fields automatically after migration. File size limits and supported formats follow Zoho Recruit's attachment standards.