Migrate your IceHrm data

Employee records are the primary object in IceHrm, storing personal info, employment details, qualifications, and documents. Standard fields map cleanly between IceHrm and most destination HRMS platforms. Custom fields added via Admin > Custom Fields require field-level mapping work during migration.

Leave is a first-class module tracking balances, approval workflows, and accrual rules. Leave types and accrual policies are standard fields and migrate well. Custom leave rules or rollover configurations need explicit translation to the destination policy model.

Punch-in/out records, timesheets, and overtime calculations are stored as time entries per employee. Migration requires preserving the relationship between the employee record and each time entry, including any location-based attendance data.

IceHrm stores salary components, pay schedules, and payroll run history. The payroll module is configurable with custom salary structures, which means we must map each salary component to the destination's payroll schema rather than performing a 1:1 field copy.

Recruitment stores job postings, applicants, application stages, and hiring pipeline data. These map directly to standard ATS objects in most destination platforms. Custom pipeline stages require explicit mapping.

IceHrm supports peer-to-peer review templates and review cycles. Review records, ratings, and comments are stored per employee and migrate as structured assessment objects. Custom review templates need field-level configuration review.

Training modules track courses, enrollments, completion records, and learning paths per employee. These map to standard LMS objects in destination platforms. Custom training modules require schema review before mapping.

IceHrm stores employee documents (contracts, certifications, ID scans) as file attachments linked to employee records. File attachments migrate alongside the record but require checking destination storage limits and accepted file types.

Custom fields can be added to selected modules via Admin > Custom Fields. Each module's custom field schema is independent. We discover all custom fields during the pre-migration audit and map them as extended attributes on the parent object.

Departments, job titles, employment types, and branch/office data define the organizational hierarchy. IceHrm allows multiple offices and countries. These structures map to the destination org chart but may require flattening or expansion depending on the destination's hierarchy model.

The Expenses module stores expense requests with custom fields per the IceHrm documentation. Custom expense fields and approval statuses require field-level mapping during migration.