Migrate from HR Director to Recruit CRM & ATS

HR Director Employee records map to Recruit CRM Candidate records. We extract FirstName, LastName, Email, Phone, Job Title, Department, Start Date, and Employment Status as structured fields. The Employee ID becomes a custom Candidate field (e.g., legacy_employee_id__c) for audit trail and cross-reference. Active employees become Active candidates in Recruit CRM; leavers become Archived or Inactive candidates depending on whether the organisation wants to retain them as historical records.

HR Director's organisational hierarchy (divisions, departments, business units) maps to Recruit CRM Client or Company records depending on context. If the organisation is a recruitment agency, internal departments map to internal Teams or custom fields on Client records. If migrating an in-house talent team, the employer organisation becomes the primary Client record with departments as custom fields or sub-records.

HR Director employment tenure, job titles, and employment type (full-time, part-time, contract) migrate as structured work history entries on the Candidate record. We extract role, employer, dates, and description fields from HR Director and populate Recruit CRM's standard work experience section or equivalent custom fields. Long tenure records (10+ years) that exceed Recruit CRM's default work history row limit are summarised in a Candidate note attached to the record.

HR Director emergency contact data has no native equivalent in Recruit CRM. We create a custom module or a structured set of custom fields (emergency_contact_name__c, emergency_contact_phone__c, emergency_contact_relationship__c) in Recruit CRM before migration. Emergency contact records that reference a second HR Director employee are resolved against the migrated Candidate records by email or employee ID.

HR Director compensation-effective-date records capture salary, bonuses, and benefit elections. Recruit CRM does not have a native compensation object. We create a Compensation_History__c custom module in Recruit CRM (Business tier or above) with fields for salary_amount__c, effective_date__c, currency__c, and bonus_amount__c, linked to the Candidate record via lookup. For Starter-tier Recruit CRM destinations, compensation data is summarised as a plain-text Candidate note for manual reference.

HR Director absence records (annual leave taken, sick days, accrued entitlement, carry-over) have no Recruit CRM equivalent because Recruit CRM does not include absence management. We create an Absence_History__c custom module in Recruit CRM Business tier with fields for leave_type__c, start_date__c, end_date__c, and days_taken__c. If the destination Recruit CRM account is on Pro tier, absence data is documented as a Candidate note for manual reconfiguration in a separate absence management tool.

HR Director documents attached to employee records (employment contracts, offer letters, policy acknowledgements) migrate as ContentDocument records in Recruit CRM linked to the Candidate record via ContentDocumentLink. We extract document type and original upload date to populate the ContentVersion metadata. PDF and Word documents transfer as binary blobs; documents larger than 25 MB are flagged for manual upload post-migration.

HR Director custom fields on the Employee object map to Recruit CRM custom fields on the Candidate object. We preserve field labels, data types, and picklist values during mapping. Multi-select picklists in HR Director become multi-select picklists in Recruit CRM if supported on the destination tier, or are flattened to comma-separated text fields. Read-only or formula fields in HR Director that reference live calculations (e.g., remaining leave balance) are not replicated; these require manual recalculation or rebuilt formulas post-migration.

HR Director payroll configuration (pay schedules, deduction rules, tax codes, bank account details) has no equivalent in Recruit CRM. We document every payroll configuration setting in a written handoff inventory with screenshots and current values. The customer configures equivalent payroll settings in Recruit CRM's integration layer or in a separate payroll tool post-migration.

HR Director absence approval rules (manager approval thresholds, escalation paths, automatic accrual triggers) do not migrate to Recruit CRM because Recruit CRM's automation builder operates on candidate and job stage events, not absence workflows. We deliver a written inventory of active absence approval rules with their trigger conditions and recommended Recruit CRM automation equivalents. Rebuild is handled by the customer's admin team post-migration.