Migrate from IceHrm to Crelate

IceHrm Employees filtered to those with recruitment module activity (applicant records, application submissions) map to Crelate Candidate. We use the Employee's personal fields (name, email, phone, address) as Candidate standard fields and preserve IceHrm qualifications, work history, and application notes in Crelate's Candidate Notes or custom fields. Active and terminated employees both migrate; inactive/archived candidates can be excluded based on customer scope during discovery.

IceHrm Employees who have been through the recruitment pipeline but are not yet hired (applicant status) map to Crelate Contact. We map IceHrm's applicant email, phone, and source tracking fields to Crelate's Contact standard fields and preserve IceHrm application stage in a custom field icehrm_application_stage__c for re-segmentation if the candidate re-enters the pipeline.

IceHrm Job Postings map to Crelate Job Order. IceHrm job title, job description, department assignment, employment type, and location fields map to Crelate Job Order standard fields. IceHrm job status (Draft, Published, Closed, On Hold) maps to Crelate Job Order status. We preserve the IceHrm job ID as a custom field icehrm_job_id__c for reconciliation.

IceHrm Application records (which link an Employee/Applicant to a Job Posting with a specific stage) map to Crelate Submission, which is Crelate's Opportunity analog for recruiting placements. IceHrm application stage (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Crelate Submission pipeline stage. IceHrm application date, source, and assigned recruiter map to Crelate Submission created date, source, and owner. IceHrm custom application fields per job posting migrate to Crelate Submission custom fields.

IceHrm's Organization module with departments, branches, offices, and job titles maps to Crelate Company records. Each IceHrm office or branch becomes a separate Crelate Company record. IceHrm department hierarchy is preserved in Crelate Company Notes. If IceHrm stores client companies (for staffing agencies), those map directly to Crelate Company. Job titles from IceHrm are preserved as Crelate Contact title fields.

IceHrm Employee documents that are CVs, resumes, cover letters, or background check files map to Crelate Candidate attachments. We extract the file from IceHrm (via API for cloud, via file system for self-hosted), preserve the original filename and MIME type, and upload to Crelate's Candidate attachment endpoint. Non-recruitment documents (contracts, certifications, ID scans) are flagged as excluded scope and documented separately.

IceHrm notes and interactions logged against an application record (interview notes, email exchanges, phone screens, status change comments) map to Crelate Activity records linked to the Submission. We preserve the activity timestamp, the author (mapped to Crelate User by email), and the activity body as Crelate Note content. Stage-change activities in IceHrm generate Crelate Activity entries with the stage name preserved.

IceHrm Employee qualifications (education, certifications, skills, language proficiency) stored on the Employee record map to Crelate Candidate custom fields or tags depending on the qualification type. Structured qualifications (degree, institution, graduation year) map to Crelate custom fields; skills and language tags map to Crelate Tags on the Candidate record.

IceHrm emergency contact information stored on the Employee record maps to Crelate Candidate custom fields (emergency_contact_name__c, emergency_contact_phone__c, emergency_contact_relationship__c). These are not standard Crelate fields and must be created as custom fields before migration.

IceHrm Leave records (balances, accruals, approval history, leave types) have no Crelate equivalent. Crelate is an ATS and Recruiting CRM and does not have a Leave Management module. We exclude Leave from migration scope and document the exclusion with a one-paragraph note per leave type (Annual, Sick, Personal, etc.) indicating record count and date range so the customer can plan a parallel leave management tool.

IceHrm Time & Attendance records (clock-in/out, timesheets, overtime) have no Crelate equivalent. We exclude attendance data from migration scope and deliver a count of attendance entries by type and employee so the customer can assess whether to keep IceHrm for attendance only or migrate to a dedicated time-tracking tool.

IceHrm Payroll records (salary components, pay schedules, payroll run history, bank details, deductions) are excluded from Crelate migration because Crelate has no payroll schema. We deliver a written inventory of payroll data by employee including salary, pay frequency, and last payroll run date so the customer can use this as a structured handoff to their payroll tool of choice.

IceHrm Performance Review records (review cycles, peer feedback, ratings, goals) have no Crelate equivalent. We exclude performance data from migration scope. Review templates and goal structures are documented as items for the customer to rebuild in their performance management tool.

IceHrm Training module records (courses, enrollments, completions, learning paths) are excluded because Crelate has no LMS schema. We document training completion records by employee and course as a structured CSV handoff that can be imported into any LMS post-migration.

IceHrm custom fields on the Recruitment/Employee module migrate to Crelate custom fields on the equivalent object (Candidate, Job Order, or Submission). Each IceHrm module's custom field schema is independent; we run the custom field discovery step per module during pre-migration audit. Picklist values from IceHrm custom fields map to Crelate picklist options. Date, numeric, and text field types map directly to Crelate field types.