Migrate from OrangeHRM to Zoho Recruit

OrangeHRM Employee PIM records map to Zoho Recruit Candidates. The employee's first name and last name become the Candidate First Name and Last Name fields (Last Name is mandatory in Zoho Recruit; we flag any OrangeHRM employees without a last name and substitute 'not provided' per Zoho's import requirements). Employee contact fields (personal email, phone) map to Candidate Email and Phone. Employee custom fields at the PIM level map to Zoho Recruit custom Candidate fields within the per-edition limit (50 on Standard, 300 on Professional). OrangeHRM employee status (Active, Terminated) maps to Candidate Status using Zoho's Active/Hired/Rejected/Archived values.

OrangeHRM's dedicated Recruitment module candidate records map directly to Zoho Recruit Candidates. OrangeHRM candidate status pipeline (Applied, Shortlisted, Interview, Offer, Hired, Rejected) maps to Zoho Recruit Candidate Status values. Application date, vacancy association, and candidate notes migrate as Candidate creation date, Job Opening lookup, and internal notes respectively. This is the cleanest object-to-object mapping in the pair because both systems use a candidate-centric data model in their recruitment modules.

OrangeHRM Job Vacancy records (title, description, hiring manager, status, job specifications) map to Zoho Recruit Job Openings. OrangeHRM vacancy status (Open, Closed, On Hold) maps to Zoho Recruit Job Opening status. The hiring manager field from OrangeHRM maps to the Assigned Recruiter in Zoho Recruit. Active vs. closed vacancy status must be set explicitly in Zoho Recruit during import, and any OrangeHRM vacancy descriptions longer than Zoho's text field limits are truncated or stored in a linked Notes record.

OrangeHRM employee qualifications, skills, education, and work history stored in PIM sub-sections map to the corresponding Zoho Recruit Candidate tabs (Skills, Education, Work Experience). Skills are mapped as text entries or picklist values depending on whether Zoho Recruit's Skills field is configured as free-text or a controlled vocabulary. We extract each qualification record as a separate row and bulk-insert into Zoho Recruit's Skills and Education sub-grids.

OrangeHRM onboarding and offboarding task assignments per employee map to Zoho Recruit Tasks linked to the corresponding Candidate record. Task type definitions from OrangeHRM (e.g., 'Background check', 'Contract signing', 'Equipment provisioning') become Task Subject values in Zoho Recruit, with completion status and due dates preserved. OrangeHRM Starter tier bulk task uploads require Gold Support contact; we route these through the CSV export path and reconstruct task records from the exported task type definitions and per-employee assignments.

OrangeHRM allows custom fields on the Employee screen that have no direct Zoho Recruit equivalent. We extract these as flat key-value pairs and create Zoho Recruit custom fields in the Candidates module during migration. This is constrained by Zoho Recruit's per-edition custom field limits: 50 on Standard, 300 on Professional. If OrangeHRM employee records have more than 50 distinct custom fields, we prioritize the top 50 by usage frequency and flag the remainder for manual re-entry or an edition upgrade. Custom field data types (text, date, picklist, checkbox) are mapped to Zoho Recruit equivalent field types with validation rules applied at import time.

OrangeHRM's organization structure with sub-departments and cost centers maps to Zoho Recruit's Departments module. We extract the department hierarchy as a flat list and reconstruct it as a Zoho Recruit Department tree with parent-child relationships. OrangeHRM's supervisor-employee reporting lines (org chart) do not have a native Zoho Recruit equivalent; we flag these as requiring manual setup in Zoho Recruit's user hierarchy post-migration.

OrangeHRM leave balances (entitlement by leave type per employee) and pending/approved leave requests do not have native equivalents in Zoho Recruit's ATS data model. We extract leave entitlement snapshots and map them to Candidate custom fields (e.g., PTO Balance, Sick Leave Remaining) if the customer wants this data preserved for reference. Leave type naming conventions differ between platforms; we produce a leave-type reconciliation table during mapping and apply it to entitlement records. This is an optional data carryover rather than a native object mapping.

OrangeHRM punch-in/punch-out records and attendance summaries are HR operational data with no equivalent in Zoho Recruit's recruitment-focused schema. We do not migrate attendance records. If the customer requires attendance data in the destination, we recommend loading it into a separate HRMS (such as Zoho People, which is part of the same Zoho ecosystem) as a parallel implementation rather than forcing attendance data into an ATS context where it has no functional use.

OrangeHRM performance module review cycles, ratings, and reviewer assignments are HR evaluation data with no Zoho Recruit equivalent. Zoho Recruit is an ATS and does not include performance management modules. We export OrangeHRM performance review data as a reference CSV and deliver it alongside the migration package for the customer's HR team to re-enter manually in their chosen performance management tool, or to load into Zoho People if performance management is part of their Zoho ecosystem implementation.

OrangeHRM employee document uploads (contracts, ID scans, certifications) stored as file references in PIM map to Zoho Recruit Candidate attachments. We export document metadata (file name, type, upload date) and provide a file copy package. Document content transfers as a separate file package delivered alongside the data migration for manual re-upload or bulk attachment to the corresponding Zoho Recruit Candidate records. We do not automate document transfer due to path and permission differences between OrangeHRM's file storage and Zoho Recruit's attachment API.

OrangeHRM user accounts and system admin role assignments are system configuration rather than HR data. These are not migrated. We extract the user list (name, email, assigned role) as a reference document and provide it to the customer's Zoho Recruit admin to provision matching users post-migration. The customer's admin assigns Zoho Recruit profiles (Standard User, Recruiter, Hiring Manager, Admin) based on the OrangeHRM role inventory we deliver.