Migrate from gradar to Recruit CRM & ATS

gradar Job records migrate to Recruit CRM Job. Each Job carries the role title, evaluation date, and total point score from gradar. The job title maps to the Recruit CRM job name field, and the evaluation date maps to a custom field gradar_evaluation_date__c. Total point score maps to a numeric custom field gradar_point_score__c for audit and reporting in Recruit CRM.

gradar grades (1-25) have no native equivalent in Recruit CRM. We migrate the numeric grade as a custom integer field gradar_grade__c on the Job object, and the grade name (where available from the export) as gradar_grade_name__c text field. This preserves the evaluation result in the destination system even though Recruit CRM does not use grades in its workflow.

gradar's three career paths (Management, Specialist, Individual Contributor) have no native Recruit CRM equivalent. We map career path assignment to a custom picklist field gradar_career_path__c on Job. The picklist values are confirmed during scoping against the customer's actual gradar career path configuration.

gradar AI-assisted job descriptions migrate as rich text into Recruit CRM's job description field. The full description body transfers intact. If Recruit CRM strips formatting, we preserve the plain text version as a fallback and note the format difference in the reconciliation report.

gradar competency profiles are structured exports that can be mapped to Recruit CRM custom fields on Job. For organisations with fewer than 20 competencies per role, we use individual custom text or picklist fields (gradar_competency_1__c through gradar_competency_n__c). For larger competency sets, we create a Custom Object in Recruit CRM named gradar_competency and link it to Job via a lookup field, which requires the customer to configure the object via Recruit CRM admin before migration.

gradar pay bands (min/mid/max per grade) have no native Recruit CRM object. We migrate pay band data as custom numeric fields on Job: gradar_pay_band_min__c, gradar_pay_band_mid__c, gradar_pay_band_max__c. Currency assignment requires explicit confirmation during scoping because gradar's export does not consistently tag currency per row. Where currency is ambiguous, we flag the record and document the gap rather than migrate with an assumed currency.

Individual factor-level point scores from gradar evaluation exports migrate as custom numeric fields (gradar_factor_score_1__c through gradar_factor_score_n__c) on the Job record. The factor count depends on the customer's gradar configuration. We confirm the exact factor names and count during scoping and create fields dynamically for each migration.

gradar user accounts and their access levels migrate as User records in Recruit CRM. We match by email address. gradar permission groups have no direct Recruit CRM role model equivalent, so we flag the access level assignments in the migration documentation for the customer's Recruit CRM admin to reconfigure manually post-migration.

gradar market benchmarking datasets have no equivalent object in Recruit CRM. We export the benchmarking records, identify the linked Job in Recruit CRM post-migration, and deliver the benchmark values as a written dataset inventory alongside the migration. The customer's admin decides how to surface this data — whether as notes, a separate spreadsheet, or a custom reporting setup.

gradar's gender pay gap regression analysis outputs are datasets, not system configuration. These do not map to any Recruit CRM object. We export the analysis results and deliver them as a structured dataset with job references for the customer to maintain externally. The audit trail from gradar's equal pay analysis cannot be preserved inside Recruit CRM without a separate reporting or analytics tool.