Migrate from OrangeHRM to Crelate

OrangeHRM Employee records from the PIM module map to Crelate Contact records. We add a custom picklist field crelate_source_type__c with values Employee and Candidate so that migrated OrangeHRM employees are distinguished from Crelate-generated candidate records. Standard fields (name, email, phone, job title, department, supervisor) map directly. OrangeHRM's supervisor chain reconstructs as a custom lookup field or the contact's hierarchy display in Crelate.

OrangeHRM allows up to 10 custom fields per employee screen (Text, Number, Dropdown types). We extract these as flat key-value pairs per employee and map them to Crelate's custom Contact fields. OrangeHRM Dropdown values become Crelate picklist options. We require that Crelate custom fields are created before migration runs; field creation order and naming must be confirmed during scoping because Crelate requires admin access to Settings | Core Records.

OrangeHRM Candidate records map directly to Crelate Contact records with type = Candidate. Candidate name, email, phone, and application status migrate. OrangeHRM's candidate-specific fields (keywords, application date, shortlisting status) map to Crelate's built-in Contact fields and custom fields. If the candidate email already exists from an OrangeHRM Employee record, we flag the duplicate for manual resolution or auto-merge based on the customer's preference.

OrangeHRM Job Vacancy records map to Crelate Job records. OrangeHRM vacancy fields (title, description, hiring manager, status, job specification) map to Crelate Job fields including title, description, owner, status, and assigned recruiter. Active and closed vacancy status from OrangeHRM maps to Crelate Job status (Open, Closed, On Hold). OrangeHRM's vacancy-to-candidate association migrates as a Crelate Job-to-Contact association.

OrangeHRM stores job specifications as attached text or linked records within the Vacancy. Long-form job descriptions migrate to Crelate's Job description field. Structured specification fields (education requirements, experience years, skills) migrate as custom fields on the Job record if the customer requires searchability on these attributes.

OrangeHRM tracks candidate application status (Application Initiated, Shortlisted, Interview Scheduled, Interview Passed, Job Offered, etc.). We map these to Crelate's Activity records on the Contact timeline for historical audit. If the customer uses Crelate's pipeline feature for candidate tracking, we map OrangeHRM status values to Crelate pipeline stages during scoping.

Crelate has no leave management module. Leave entitlements, balances, and request records from OrangeHRM cannot be mapped to any Crelate object. We flag this data as non-migratable during scoping and recommend that customers use the migration as an opportunity to establish a dedicated leave management system (BambooHR, Rippling, or Workday) if leave tracking is required post-Crelate. Historical leave balances can be stored as a custom field on the Contact record for reference if desired.

Crelate has no attendance or time-tracking module. Punch-in/punch-out records and attendance summaries from OrangeHRM have no destination in Crelate. We flag attendance data as non-migratable and advise customers to consolidate any historical attendance reports as a file attachment on the Contact record or in a separate document management system before migration cutover.

Crelate has no performance management module. Performance review cycles, ratings, goals, and competencies from OrangeHRM cannot migrate to Crelate. We flag performance data as non-migratable and note that if the customer's organization requires post-hire performance tracking, they should maintain this in a separate HRMS platform. We deliver a written summary of OrangeHRM performance review records for the customer's HR team to archive.

Crelate is a recruiting platform and does not manage onboarding or offboarding task workflows. OrangeHRM task type definitions and per-employee task assignments are flagged as non-migratable. We extract task definitions as a CSV reference file and deliver it to the customer so their recruiting or HR team can manually reconstruct relevant pre-boarding tasks in Crelate or a separate onboarding tool.

OrangeHRM's supervisor-employee relationships define the organizational chart. We extract direct-report mappings and store the supervisor relationship as a custom lookup field on the Contact record in Crelate. For organizations with deep hierarchies, we export the full org chart as a CSV that can be loaded into Crelate's Contact hierarchy feature or used to build the org structure in a separate HRMS.

Work Schedule records from OrangeHRM 7.13 and later have no equivalent in Crelate. We flag schedule data as non-migratable and note that if the customer's recruiting team needs to track recruiter availability or interview scheduling preferences, Crelate's calendar integration (via Google Calendar or Outlook connectors) is the replacement mechanism rather than a structured schedule record.

OrangeHRM user accounts and admin role assignments are system configuration, not HR data. They do not migrate. We deliver a written inventory of OrangeHRM user roles and their module access permissions for the customer to use as a reference when provisioning Crelate user accounts and assigning Crelate User Roles with API access enabled for any integration requirements.

OrangeHRM stores employee document uploads (contracts, ID scans, certifications) as file references. We export document metadata (filename, type, upload date) and provide a file copy package transferred as a separate deliverable. Crelate supports file attachments on Contact records via its document storage. The customer's admin uploads the file package to Crelate after migration cutover and links documents to the appropriate Contact records.