Migrate from gradar to Zoho Recruit

gradar Job records map to Zoho Recruit Job Opening. We extract job title, job description (rich text), department, and location from the gradar export and populate the corresponding Zoho Recruit standard fields. The j ob's overall point score and total evaluation date migrate as custom numeric fields on the Job Opening. The mapping uses job title as the dedupe key; if a Zoho Recruit Job Opening with the same title already exists, we flag it for the customer's admin to resolve before insert.

gradar's 25-point grade scale (grades 1-25) has no native equivalent in Zoho Recruit. We create a custom picklist field on the Job Opening module named Job_Grade__c with the grade values (1 through 25) as picklist options and populate it from the grade field in the gradar export. If gradar also stores a grade name (e.g., G12, Senior Specialist), we create a second text field Grade_Name__c.

gradar's three career paths (Management, Technical, Specialist) map to a custom picklist field Career_Path__c on Job Opening. Each Job record carries its career path affiliation from gradar's evaluation record. We set the field to the appropriate path value during migration. If the customer uses custom career path names, we create the picklist options dynamically from the gradar export values rather than hard-coding a three-value enum.

gradar stores AI-assisted and manually authored job descriptions as rich text. We migrate the full description body into Zoho Recruit's Description field on Job Opening. If the description contains embedded images or formatting not supported in plain-text CSV, we flag each affected record and either sanitize to plain text or document the gap in the migration report.

Individual factor-level point scores (the component scores that contribute to the overall total point value) are available in gradar's advanced exports. We map these to a set of custom numeric fields on Job Opening — one field per factor — named Factor_Score_<FactorName>__c. The number of factors varies by the customer's gradar configuration, so the field creation step is driven by the actual export column headers rather than a fixed schema.

gradar pay band definitions (min, mid, max per grade per currency) have no standard representation in Zoho Recruit's ATS schema. We create a custom module named Compensation_Band__c linked to Job Opening via a lookup, with fields Grade__c (picklist), Currency__c (text), Min_Salary__c, Mid_Salary__c, Max_Salary__c (currency-formatted). Currency ambiguity in multinational exports is resolved during scoping with explicit customer confirmation before any salary values are committed.

gradar competency profiles are structured exports linking competencies to jobs. We create a custom module Competency__c and a junction object Job_Competency__c to represent the many-to-many relationship between Job Opening and competency records. If the customer's Zoho Recruit edition limits custom module creation, we fall back to a multi-select picklist on Job Opening named Competencies__c with competency names as options.

Market benchmarking data sourced from third-party providers into gradar migrates as a structured dataset to the custom Compensation_Band__c module. Fields include Market_Rate__c, Benchmark_Source__c (text), Benchmark_Date__c (date). The linked Job Opening lookup is resolved at migration time by matching the job title from the benchmarking record against the migrated Job Opening dedupe key.

gradar user accounts and role-based access assignments map to Zoho Recruit User records. We resolve by email match against the Zoho Recruit destination User table. Any gradar user without a matching Zoho Recruit User goes to a reconciliation queue; the customer's admin must provision the User before migration of any records that reference that Owner can proceed. Zoho Recruit requires users with existing separate Zoho Recruit accounts to close those accounts before import.

gradar's equal pay analysis outputs are regression datasets with gender pay gap calculations per job or grade. These are analytics products, not operational HR records, and have no ATS equivalent in Zoho Recruit. We export the analysis results as a structured CSV and deliver it as a standalone file alongside the migration, along with a written summary noting which jobs and grades are flagged. The customer imports this into Zoho Analytics or a dedicated BI tool post-migration.

If gradar is integrated with an upstream ATS that feeds candidate data into job records (some gradar deployments include this), we extract candidate records from that source and migrate them to Zoho Recruit Candidate module. The Candidate Last Name is mandatory in Zoho Recruit; any candidate without a last name value receives the placeholder 'not provided' per Zoho Recruit's import guidance. Candidates are inserted after Job Openings to satisfy the Job Opening lookup on each Candidate record.

gradar does not have a native campaign object, but if the customer's deployment includes recruitment marketing campaigns linked to job openings (rare, enterprise HRMS integrations only), we map these to Zoho Recruit Campaign. Standard gradar-only deployments will have no Campaign records to migrate.