Migrate from gradar to BambooHR

gradar Jobs map to BambooHR Employee records where each evaluated role becomes a job title and related custom fields for grade, career path, and evaluation date. We preserve the job's factor scores in a structured custom field group since BambooHR does not have a native evaluation score object. The employee record's job title field maps from gradar's role name. Evaluation dates migrate to a custom date field. If the destination BambooHR is configured with a separate Job Openings module for job reqs, we map gradar Jobs to the employee's current job history rather than the openings table.

gradar Grades 1-25 map to BambooHR Pay Grades if the destination is on Pro ($17/employee/month) or Elite ($25/employee/month). Core tier does not include pay grade configuration — we flag this at scoping and either recommend a tier upgrade or map grades as a custom picklist field on the Employee record. Each gradar grade value and grade name (where named, e.g. G10, M5) migrates as a Pay Grade entry. Grade-to-pay-band linkage migrates as Pay Grade Steps with min/mid/max amounts.

gradar's three career paths (e.g., Individual Contributor, Management, Technical) have no native BambooHR equivalent. We map career path assignments as a custom employee property (a BambooHR custom field with picklist values matching the three paths) on each employee record. If the customer uses BambooHR's department or division structure, we evaluate whether career paths map to those groupings during scoping.

gradar job descriptions (rich text) migrate to BambooHR's employee record. BambooHR stores a Job Description field on the Employee record; we map the full description body to that field. Where gradar descriptions include competency-linked sections, we split them into the job description field and a separate competencies custom field to preserve readability.

gradar competency profiles linked to jobs are available as a structured export. We map competencies to a BambooHR custom employee property of type multi-select picklist or store them as a structured text block. Custom competencies that exist only in gradar are flagged and the customer chooses whether to create matching custom picklist options in BambooHR or consolidate them into a generic competencies field.

gradar pay band definitions (min/mid/max per grade per currency) map to BambooHR Pay Grade Steps on Pro and Elite tiers. Currency handling requires explicit confirmation during scoping — gradar exports multicurrency pay bands without consistent currency tagging per row. We flag currency ambiguity per structure and ask the customer to confirm the correct currency before we write any compensation data. For Core tier destinations without Pay Grades, pay band data migrates to custom employee compensation fields (custom fields with currency type).

Individual factor-level point scores that contribute to each job's total grade are available in gradar's advanced exports. We migrate the complete factor score set as a structured JSON or CSV attached to the employee record as a file, or as a group of custom numeric fields if BambooHR's custom field limit permits. Factor scores have no native reporting equivalent in BambooHR; their primary purpose is audit trail preservation.

Market benchmarking data sourced from third-party providers integrated into gradar migrates as a structured dataset. We map benchmark market rates and their linked job references to a custom BambooHR table or file attachment. BambooHR has no native benchmarking feature; the customer uses this data for external reporting or keeps it in a spreadsheet alongside BambooHR records. We note this gap explicitly in the migration scope.

gradar's regression-based gender pay gap analysis outputs are datasets, not system configuration. We migrate the analysis results as a structured CSV with field mapping to the relevant employee identifiers. BambooHR has no native equal pay analysis module; this data serves as an audit record for the customer's compliance team to maintain independently. We document the structure for future reference.

gradar user accounts and their role-based access assignments map to BambooHR Employee records. gradar's permission groups require mapping to BambooHR's role-based access model (Admin, Manager, Employee). We extract the user list and permission assignments and create corresponding employee records in BambooHR with the appropriate access level. Any gradar user without a matching employee record in the destination is held in a reconciliation queue.