HRMS migration
Field-level mapping, validation, and rollback between IceHrm and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
IceHrm
Source
Zoho Recruit
Destination
Compatibility
11 of 12
objects map 1:1 between IceHrm and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
IceHrm is a full-stack HRMS covering Employee Management, Leave, Time & Attendance, Payroll, Recruitment, Performance Reviews, and Training. Zoho Recruit is a dedicated Applicant Tracking System focused on candidate sourcing, job openings, interview scheduling, and recruitment analytics. The migration scope narrows to IceHrm's Recruitment and Employee modules because the remaining modules have no direct Zoho Recruit object. We run a custom field discovery step per IceHrm module, handle Zoho Recruit's mandatory Last Name field requirement on Candidates, and preserve file attachments as Zoho Recruit Attachments linked to the correct Candidate record. IceHrm self-hosted instances may have modified PHP/MySQL schemas that require schema-audit adjustments before any field mapping is finalized. We do not migrate workflows, automations, or payroll runs; we deliver a written inventory of these for your admin to rebuild in Zoho Recruit or a complementary Zoho product.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a IceHrm object lands in Zoho Recruit, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
IceHrm
Employees
Zoho Recruit
Candidates
1:1IceHrm Employee records map to Zoho Recruit Candidates. The First Name and Last Name fields split from IceHrm's full_name or emp_firstname/emp_lastname structure. Zoho Recruit requires Last Name as a mandatory field; records without a last name are flagged and populated with 'not provided' per Zoho Recruit's import specification. Employee number, joining date, and employment status migrate as custom Candidate fields. Self-hosted IceHrm instances may have custom columns added to the employee table; we discover the deployed schema before field mapping begins.
IceHrm
Recruitment: Job Openings
Zoho Recruit
Job Openings
1:1IceHrm job postings map directly to Zoho Recruit Job Openings. IceHrm job_title, job_description, and department assignments transfer to Zoho Recruit's corresponding fields. IceHrm's recruitment status (open, closed, on-hold) maps to Zoho Recruit's Job Opening status field. Hiring team assignments on IceHrm job postings become Zoho Recruit users assigned to the Job Opening.
IceHrm
Recruitment: Applicants
Zoho Recruit
Candidates (linked to Job Openings)
1:1IceHrm applicant records map to Zoho Recruit Candidates and are linked to the corresponding Job Opening via the Zoho Recruit Candidate mapping. IceHrm application stages (applied, screening, interview, offer, rejected) map to Zoho Recruit pipeline stages. Application date, source channel, and referral information migrate as Candidate fields.
IceHrm
Recruitment: Interview Records
Zoho Recruit
Interviews
1:1IceHrm interview records map to Zoho Recruit Interviews. Interview date, time, interviewer name, interview type, and feedback or score migrate as Interview fields. IceHrm interview notes map to Zoho Recruit Interview Notes linked to the Interview record. Interview scheduling status (scheduled, completed, cancelled) transfers to the Zoho Recruit Interview status.
IceHrm
Leave / Time-off
Zoho Recruit
Not supported in Zoho Recruit
1:1IceHrm Leave module (balances, accrual rules, leave types, and approval workflows) has no direct Zoho Recruit object. Zoho Recruit is an ATS and does not include leave management. We flag this module as unsupported during scoping. Customers requiring leave data migration should consider a parallel engagement to Zoho People, which has a dedicated Leave Management module. Leave data is not migrated into Zoho Recruit.
IceHrm
Payroll
Zoho Recruit
Not supported in Zoho Recruit
1:1IceHrm Payroll (salary components, pay schedules, payroll run history, and custom salary structures) has no direct Zoho Recruit object. Zoho Recruit does not include payroll functionality. We flag payroll as out of scope and recommend Zoho Payroll as a separate migration destination if payroll data continuity is required. Payroll records are not migrated into Zoho Recruit.
IceHrm
Time & Attendance
Zoho Recruit
Not supported in Zoho Recruit
1:1IceHrm Time & Attendance (punch-in/out records, timesheets, and overtime calculations) has no direct Zoho Recruit object. Zoho Recruit does not include attendance tracking. We document the attendance module schema and record count as part of the written migration inventory, but no records migrate into Zoho Recruit.
IceHrm
Performance Reviews
Zoho Recruit
Not supported in Zoho Recruit
1:1IceHrm Performance Reviews (peer-to-peer review templates, review cycles, ratings, and comments) have no direct Zoho Recruit object. Zoho Recruit is an ATS and does not include performance management. Review records are documented in the written migration inventory but are not migrated into Zoho Recruit.
IceHrm
Training / Learning Management
Zoho Recruit
Not supported in Zoho Recruit
1:1IceHrm Training (courses, enrollments, completion records, and learning paths per employee) has no direct Zoho Recruit object. Zoho Recruit does not include LMS functionality. Training enrollment data is documented in the written migration inventory for admin reference but is not migrated into Zoho Recruit.
IceHrm
Documents
Zoho Recruit
Attachments
1:1IceHrm employee documents (contracts, certifications, ID scans) attached to Employee records migrate as Zoho Recruit Attachments linked to the corresponding Candidate record. We extract documents individually via web interface or file system access (self-hosted) because IceHrm does not provide a bulk file export endpoint. We preserve file name, MIME type, upload date, and the link to the Candidate. Zoho Recruit supports file attachments on Candidates and Job Openings.
IceHrm
Departments / Organization Structure
Zoho Recruit
Departments
1:1IceHrm departments, branches, and office locations map to Zoho Recruit Departments. Department hierarchy (parent-child relationships) migrates to Zoho Recruit's department structure via the parent department lookup field. Job titles and employment types from IceHrm's organizational setup become custom fields or picklist options on the Candidate object in Zoho Recruit.
IceHrm
Custom Fields
Zoho Recruit
Custom Fields
lossyIceHrm custom fields per module are discovered during the pre-migration audit and mapped to Zoho Recruit custom fields. Custom field types (text, number, date, picklist) are matched to equivalent Zoho Recruit field types. Picklist values from IceHrm custom fields are extracted and mapped to Zoho Recruit picklist options. Custom fields added to IceHrm modules that have no Zoho Recruit equivalent (Leave, Payroll, Training, Performance) are documented in the written inventory but not migrated.
| IceHrm | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Employees | Candidates1:1 | Fully supported | |
| Recruitment: Job Openings | Job Openings1:1 | Fully supported | |
| Recruitment: Applicants | Candidates (linked to Job Openings)1:1 | Fully supported | |
| Recruitment: Interview Records | Interviews1:1 | Fully supported | |
| Leave / Time-off | Not supported in Zoho Recruit1:1 | Fully supported | |
| Payroll | Not supported in Zoho Recruit1:1 | Mapping required | |
| Time & Attendance | Not supported in Zoho Recruit1:1 | Fully supported | |
| Performance Reviews | Not supported in Zoho Recruit1:1 | Fully supported | |
| Training / Learning Management | Not supported in Zoho Recruit1:1 | Fully supported | |
| Documents | Attachments1:1 | Mapping required | |
| Departments / Organization Structure | Departments1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
IceHrm gotchas
Self-hosted schema modifications cause migration surprises
Employee count billing model on IceHrm Cloud
Custom fields per module require manual field-level discovery
Document attachment export requires file-by-file handling
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and module inventory
We audit the source IceHrm instance across deployment type (cloud or self-hosted), active modules, and record volumes per module. For self-hosted instances, we connect to the MySQL database and inspect the deployed schema to identify any custom columns, modified field types, or custom tables. We produce a written migration inventory listing every IceHrm module, its record count, and whether a Zoho Recruit equivalent exists. This inventory forms the basis for the migration scope and the out-of-scope module documentation.
Name field auditing and mandatory field preparation
We analyze IceHrm's name field structure across all Employee and Applicant records. If IceHrm uses a single full_name field, we split it into First Name and Last Name using common name patterns; records where splitting is ambiguous are flagged for customer resolution. We verify that every record will satisfy Zoho Recruit's mandatory Last Name requirement before migration begins. Records without a resolvable last name are prepared with a 'not provided' placeholder per Zoho Recruit's import specification.
Custom field discovery and picklist value extraction
We run a custom field discovery step across all active IceHrm modules. For each module, we extract the custom field definitions (name, type, required flag) and any associated picklist option sets. Custom fields are mapped to equivalent Zoho Recruit field types during this phase. Picklist values from IceHrm are extracted and mapped to Zoho Recruit picklist options, with unmapped values flagged for customer confirmation. Modules without Zoho Recruit equivalents (Leave, Payroll, Training, Performance) have their custom field schemas documented but not migrated.
Sandbox migration and reconciliation
We run a full migration into a Zoho Recruit sandbox account using production-like data volume. The customer reconciles record counts (Candidates in, Job Openings in, Interviews in, Attachments in), spot-checks 25-50 random Candidate records against the IceHrm source, and validates that custom field data landed correctly. Name field handling is validated specifically. The customer signs off on the sandbox migration before production cutover begins. Any mapping corrections happen here.
Production migration in dependency order
We run production migration in record-dependency order: Departments (setup first for department hierarchy), Job Openings (referenced by Candidate links), Candidates (with Last Name resolved and department assignment mapped), Interviews (linked to Candidates and Job Openings), and Attachments (linked to Candidates by record ID). Each phase emits a row-count reconciliation report before the next phase begins. During cutover, we capture a final delta export of any records modified in IceHrm during the migration window.
Cutover, validation, and module inventory delivery
We freeze IceHrm writes during cutover, run the final delta migration, then enable Zoho Recruit as the system of record for recruitment data. We validate that all Candidates are linked to correct Job Openings, all Interview records reference the correct Candidates, and all Attachments are accessible on the correct Candidate records. We deliver the written migration inventory covering unsupported modules (Leave, Payroll, Training, Performance) and a written map of any IceHrm workflow or automation rules requiring rebuild in Zoho Recruit Blueprint or Assignment Rules. We do not rebuild automations inside the migration scope.
Platform deep dives
IceHrm
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across IceHrm and Zoho Recruit.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
IceHrm: Not publicly documented.
Data volume sensitivity
IceHrm doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during IceHrm to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your IceHrm to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave IceHrm
Other ways to arrive at Zoho Recruit
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.