Migrate from IceHrm to Recruit CRM & ATS

IceHrm Employee records are the primary migration object and map to Recruit CRM Candidate records. We extract the employee's full name, contact details, employment history, qualifications, and status (active, inactive, terminated) and create a Candidate record in Recruit CRM. The candidate's original hire date in IceHrm migrates as the candidate_joined_date field in Recruit CRM. Inactive and terminated employees require a scoping decision: they can migrate as candidates (archived status) or be excluded from the migration scope to keep the Recruit CRM candidate database lean.

IceHrm job postings migrate to Recruit CRM Job records. We map job title, job description, requirements, location, employment type, and department from IceHrm to Recruit CRM's job structure. If IceHrm has custom fields on the job posting module, we discover those during the audit phase and create corresponding custom fields in Recruit CRM before migration.

IceHrm applicants attached to a job posting map to Recruit CRM Candidate records linked to the corresponding Job record via the application relationship. Application stage in IceHrm (application received, screening, interview, offer, hired, rejected) maps to Recruit CRM pipeline stages. If IceHrm has custom pipeline stages, we document them and configure matching stages in Recruit CRM before the application data migrates.

IceHrm stores employee documents (contracts, certifications, ID scans) as file attachments linked to the employee record. We extract documents individually via the web interface or file system access on self-hosted instances, preserving the original filename, MIME type, upload date, and employee link. Each document is reattached to the corresponding Candidate record in Recruit CRM post-import. This requires file-by-file handling; there is no bulk document export in IceHrm.

IceHrm organizational hierarchy (departments, job titles, employment types, branch offices) maps to Recruit CRM through custom fields on the Candidate and Job objects. Department from IceHrm becomes a picklist or tag in Recruit CRM. We create the department taxonomy in Recruit CRM during configuration so the original organizational context is searchable in the candidate database.

IceHrm allows custom fields to be added independently to the Employees module, meaning the same module may have different custom field schemas across two IceHrm instances. We run a custom field discovery step against the source IceHrm instance before mapping begins, capturing all extended attributes. If custom fields reference picklist values, we also extract the value options and create matching picklist values in Recruit CRM. Custom field discovery is repeated per active IceHrm module.

IceHrm custom fields on job postings and applicants migrate to Recruit CRM custom fields on Job and Application objects. We apply the same discovery process as the Employee module: extract schema, map field types, and create the destination custom fields in Recruit CRM before the application data migrates.

IceHrm leave management (balances, accrual rules, approval workflows, and time-off requests) has no direct equivalent in Recruit CRM, which is a recruitment and applicant tracking platform and does not include HR leave management. We do not migrate leave data to Recruit CRM. We flag this module during scoping and recommend the customer either retain the leave data in IceHrm read-only post-migration, export it as a spreadsheet, or migrate it separately to a destination HRMS if the customer is adopting Recruit CRM as their standalone ATS.

IceHrm payroll data (salary components, pay schedules, payroll run history, custom salary structures) has no equivalent in Recruit CRM. Recruit CRM does not include payroll or compensation management. We do not migrate payroll data to Recruit CRM. If the customer needs payroll continuity, we scope a separate migration to a destination HRMS platform (BambooHR, Rippling, Gusto) as an additional engagement.

IceHrm performance review templates, review cycles, peer-to-peer ratings, and comments have no equivalent in Recruit CRM. We do not migrate performance review data to Recruit CRM. We export the review history as a structured CSV inventory delivered to the customer for manual re-entry or archive. Review templates are documented in the written migration inventory for the customer's admin to evaluate rebuilding in Recruit CRM's custom fields or a separate performance management tool.

IceHrm training modules (courses, enrollments, completion records, learning paths) have no equivalent in Recruit CRM. We do not migrate training data to Recruit CRM. We deliver a CSV export of completion records per employee as part of the written migration inventory. If the customer requires learning management continuity, we scope a separate migration to an LMS destination.

IceHrm expense requests and approval statuses have no equivalent in Recruit CRM. We do not migrate expense data. We export the expense history as a structured CSV for the customer to archive or migrate to a separate expense management platform.