Migrate from HR Manager Pro to Crelate

HR Manager Pro Employee records map to Crelate Candidate records. We extract the employee's first name, last name, email, phone, address, job title, department, hire date, employment status, and compensation fields from the CSV export and map them to the corresponding Crelate Candidate attributes. The employee's WordPress user ID is preserved in a custom Crelate field (hr_manager_pro_employee_id__c) as a migration reference key for audit and reconciliation. Crelate's Candidate status field (Active, Hired, Placed, Rejected, Withdrawn) maps from HR Manager Pro's employment status, with terminations flagged as inactive candidates for historical reference.

HR Manager Pro department taxonomy maps to Crelate Tags attached to Candidate records. Each unique department name from the HR Manager Pro export becomes a Tag in Crelate, and every migrated Candidate receives the tag corresponding to their assigned department. Tags are created during the Crelate configuration phase before Candidate import begins. If the customer uses nested or multi-level department names (e.g., Engineering > Backend), we flatten to the most specific level and note the hierarchy in the migration documentation.

HR Manager Pro leave balance snapshots migrate as static custom fields on each Candidate record in Crelate. We create fields for each leave type present in the source data (Annual Leave Balance, Sick Leave Balance, etc.) and populate them with the current balance extracted from the plugin's custom tables. Accrual calculation rules (frequency, carryover limits, vesting schedules) are not exportable from HR Manager Pro and do not migrate; we note these in the migration report and advise the customer to configure leave entitlement rules in their destination HR system if applicable.

Employee documents (contracts, IDs, certifications, offer letters) are stored in the WordPress media library, not as rows in the HR plugin database. The HR Manager Pro CSV export contains the WordPress attachment ID or file path. We run a parallel download step to fetch each document from the WordPress media library using the file URL, map it to the corresponding Candidate record in Crelate, and attach it as a Candidate document. This step adds 15-30 minutes per 100 documents depending on file size and network latency. Documents are re-uploaded via Crelate's attachment API and linked with a custom migration_tag indicating the original HR Manager Pro document type.

HR Manager Pro allows admins to define custom fields on employee profiles. These fields are discovered only during the pre-migration scan against the live WordPress instance. We include each custom field as an additional column in the CSV export and map it to a corresponding custom attribute in Crelate. Field type mapping is determined during scoping: text fields map to Crelate text attributes, numeric fields to number attributes, dates to date attributes, and checkbox or multi-select fields to Crelate multi-select or tag-based fields. If the customer adds custom fields after scoping but before migration day, we re-run the scan and update the field map before executing the transfer.

Benefits plan assignments and deduction rates exported per employee as part of the HR Manager Pro employee CSV migrate to Crelate as custom Candidate fields. We create a Benefits Plan field on the Candidate record and populate it with the plan name from the source data. Plan details themselves (carrier, coverage tiers, cost) are not a separate exportable object in HR Manager Pro and cannot be migrated as structured plan records. We document the limitation in the migration report and advise the customer to configure plan details in their destination benefits administration system if separate from Crelate.

HR Manager Pro employment status values (Active, Terminated, On Leave, Suspended) map to Crelate Candidate status values and custom fields. Active employees map to Active Candidate status. Terminated employees map to a custom Crelate status (Historical - Terminated) to preserve the record without treating it as an active recruiting candidate. On Leave employees receive a custom leave_indicator__c flag. Employment status is resolved at migration time using the most recent status value in the source data.

Emergency contact information stored in HR Manager Pro custom fields or as part of the employee profile migrates to Crelate as custom text fields on the Candidate record. We create fields for emergency_contact_name, emergency_contact_relationship, and emergency_contact_phone, populated from the source CSV columns. If emergency contact is not present in the exported CSV, we flag it during scoping and either request the customer add the column manually in WordPress before export or note the gap in the migration report.

Employee photos stored in the WordPress media library migrate as Crelate Candidate photos. We extract the photo URL from the HR Manager Pro employee record, download the image file, and upload it to Crelate's candidate profile. Photos are processed in the same parallel download workflow as employee documents, adding to the per-100-documents time estimate. Photos that are hosted externally (URLs not pointing to the WordPress media library) are noted and linked as external URLs in a custom field rather than uploaded as attachments.

Job title from HR Manager Pro maps directly to the Title field on Crelate Candidate. This field is a standard Crelate attribute and does not require custom field creation. We use the job_title column from the CSV export. If the customer's HR Manager Pro instance uses a job_title_with_department format (e.g., 'Senior Engineer - Backend'), we parse and populate the Crelate Title field with the role name, noting the department assignment separately in the Tag field derived from the department mapping.

Salary, hourly rate, and compensation-related fields from HR Manager Pro migrate to Crelate custom currency fields on the Candidate record. We create fields for current_salary and compensation_notes if the source data includes salary bands or compensation history. Single compensation snapshot values migrate as static data; compensation history over time is not available for export from HR Manager Pro and cannot be migrated as a time-series record.

Dependent information and next of kin data stored in HR Manager Pro employee profiles migrates to Crelate as custom text fields on the Candidate record. We create fields for dependent_name, dependent_relationship, and dependent_contact if these columns appear in the exported CSV. This data is used for benefits enrollment and emergency contact purposes in the HR context and is preserved as reference fields in Crelate for cases where recruiting placements involve benefits administration or contractor onboarding.

Work authorization and immigration status fields from HR Manager Pro (visa type, work permit expiry, citizenship status) migrate to Crelate custom text fields on the Candidate record. These fields are particularly relevant for recruiting placements where compliance and work authorization are requirements. We create fields such as visa_type__c and work_permit_expiry__c populated from the source data, and flag any records with expired permits as a custom status for recruiter review.

Payroll runs are not handled by the HR Manager Pro core plugin. Historical payroll data (salary history, pay changes, bonus payments) lives in a separate database table that is not accessible via CSV export. We do not migrate payroll records. The migration report documents this gap and recommends the customer maintain access to HR Manager Pro or its backup files for historical payroll reference, or export payroll data separately before decommissioning the plugin.

HR Manager Pro leave approval workflows and automated rule configurations (e.g., auto-approve under 3 days, manager escalation paths) are plugin settings stored in WordPress options tables, not as data records exportable via CSV. These configurations do not migrate. We deliver a written inventory of any configured leave approval rules and suggest Crelate workflow alternatives (if the customer uses Crelate for internal HR alongside recruiting) or a separate HR system for leave management. This is standard scope for the migration deliverable.