Migrate from HR Director to Crelate

HR Director Employee records map to Crelate People (candidate) records. The employee's first name, last name, email, phone, address, and job title transfer directly. We preserve the HR Director employee ID as a custom field hr_director_employee_id__c on the Crelate People record for cross-system reconciliation. NI numbers (UK National Insurance) transfer to a custom field national_insurance__c on People. Active employees become active People in Crelate; leavers become archived People with a termination date field populated from HR Director's leaving date.

HR Director's Organisation record maps to Crelate Organization (Client). If the destination use case is pure recruiting, the Organisation is the employer/client; if the destination use case includes HR data on current employees, the Organisation maps to a Client or Account record representing the company that the employee works for. We deduplicate against existing Crelate Organizations by company name and address.

HR Director compensation records with effective dates map to a compensation history on the Crelate People record. Each compensation entry (salary, bonus, equity) with its effective_date becomes a dated custom field set or a chronological note entry on the People record. Crelate has no native compensation object, so we use a structured note or a series of effective-dated custom fields (salary_effective_date__c, salary_amount__c, bonus_amount__c) to preserve payroll continuity. We sequence compensation records by effective_date to ensure chronological ordering in the destination.

HR Director absence records map to absence fields or structured notes on the Crelate People record. Each absence type (annual leave, sick leave, maternity, paternity) with start date, end date, and status becomes a structured entry. Crelate does not have a native absence management module, so we configure custom fields for remaining leave balances (annual_leave_remaining__c, sick_leave_remaining__c) and attach a detailed absence log as a note. Custom leave entitlement rules from HR Director require manual reconfiguration in Crelate's custom field setup; we document each rule during scoping and deliver it as a reconfiguration checklist.

HR Director emergency contact records (name, relationship, phone) per employee map to custom fields on the Crelate People record: emergency_contact_name__c, emergency_contact_relationship__c, emergency_contact_phone__c. If an employee has multiple emergency contacts, the primary contact maps to the standard fields and additional contacts attach as structured notes or a related-list custom object if Crelate's Enterprise tier supports it.

HR Director document attachments (contracts, ID copies, certifications) migrate as files attached to the corresponding Crelate People record. We preserve the original filename, file type, and upload date. Files are linked via Crelate's file attachment mechanism at migration time. Any document naming conventions used in HR Director (e.g., CONTRACT_2024_JohnSmith.pdf) are preserved as filenames for discoverability.

HR Director Job or Position records (job title, department, manager, FTE status, pay grade) map to Crelate Job records if the destination includes placement tracking. If the migration is purely an HR data migration without recruiting workflow, Job fields map to custom fields on the Crelate People record. The manager relationship from HR Director maps to a manager lookup field if Crelate supports it, or to a text field with the manager's name.

HR Director workflows and automations (approval chains, notification rules, absence triggers) do not migrate to Crelate's workflow system. Crelate's workflow builder is designed for recruiting pipelines and email sequences, not HR approval processes. We deliver a written inventory of every active HR Director workflow with its trigger, conditions, and actions, mapped to a Crelate configuration recommendation where applicable. The customer's HR admin rebuilds these in Crelate or a separate HRMS post-migration.

HR Director reports and dashboards do not migrate. We deliver a written map of every configured HR Director report with its filters, groupings, and data sources, and a recommended Crelate reporting equivalent (Crelate Analytics or a third-party BI tool). The customer's admin rebuilds reports in Crelate's analytics module or exports them to a data warehouse for ongoing BI.

HR Director payroll data (pay periods, earnings, deductions, tax codes) maps to a payroll history section on the Crelate People record as structured notes or a linked document. Crelate has no native payroll module, so payroll continuity is preserved by attaching HR Director payroll run exports as PDF notes or structured text entries on the People record. We flag the payroll data gap in the migration scope and recommend that payroll continues to run in HR Director or migrates to a dedicated payroll platform (Sage, BrightPay, or Xero) separately.

UK workplace pension enrollment details (scheme name, contribution percentage, employer/employee amounts) from HR Director map to custom fields on the Crelate People record: pension_scheme__c, pension_contribution_pct__c, employer_contribution_pct__c. Auto-enrolment status maps to a picklist field. Pension data requires re-enrolment setup in Crelate's HR module if used; we document the current pension configuration as a reconfiguration checklist item.

HR Director custom leave entitlement rules (accrual rates, carry-over limits, anniversary-based entitlements, contractual additional leave) require manual reconfiguration in Crelate's custom field setup. We audit every custom rule during discovery, document it with its logic and parameters, and deliver it as a Crelate configuration checklist. Leave balances are calculated at migration date and seeded into Crelate's custom fields; subsequent accruals are managed manually or via a leave management integration post-migration.