Migrate from gradar to Bullhorn ATS & CRM

gradar Jobs (Roles) with their evaluation status, title, and overall point score map to Bullhorn JobOrder as the primary record, with evaluation metadata (grade, career path, evaluation date, total points) stored in customObject1s. The job title maps to JobOrder.title, and the evaluation date maps to a custom Date field in the Custom Object. Jobs without a completed evaluation migrate with a status field indicating pending evaluation so the customer's Bullhorn admin can flag roles requiring re-evaluation post-migration.

gradar's derived grades (1-25 from point-factor scoring) map to a custom picklist field on the Custom Object attached to JobOrder. The grade name and numeric value both migrate. Bullhorn's picklist field limits require mapping to one of the two representations; we default to numeric grade (1, 2, 3...) and include grade name as a text field to preserve both. Organizations with custom grade naming conventions confirm the picklist values during scoping.

gradar's three career paths map to a custom picklist or text field on the JobOrder Custom Object. Career path is a property of the Job record in gradar and migrates as a read-only field on the Bullhorn JobOrder. We use a picklist if the customer confirms the three path names; we use text if the organization has customized career path labels beyond the standard three.

gradar pay band definitions (min, mid, max per grade per currency) map to customObject2s with a lookup relationship to the JobOrder Custom Object or a direct link via a reference field. Currency handling requires explicit customer confirmation per pay band row during scoping because gradar exports do not consistently tag currency. We flag any ambiguity and ask the customer to confirm before committing data. Bullhorn has no native pay band management, so compensation data lives as structured custom fields.

Individual factor-level point scores from gradar's evaluation (the raw factor breakdown that produces the total grade) map to customObject3s with a composite key of JobOrder ID plus factor name. We extract the complete factor score set from gradar's advanced exports. Bullhorn's 55-field limit per Custom Object applies; for roles with many factors we consolidate the most significant factors and note the remainder in a structured text field. Factor score history (changes over time) migrates as a separate entry per evaluation date if the export includes it.

gradar competency profiles linked to jobs migrate as a structured list within the JobOrder Custom Object. If the competency list is short, we use multi-select text fields; if extensive, we create a separate Custom Object for competencies with a junction lookup back to JobOrder. Any custom competencies defined by the organization are flagged during scoping and confirmed before migration because Bullhorn's custom field editing requires Bullhorn Support involvement for certain field types.

Market benchmarking data sourced from third-party providers within gradar (external market rate comparisons per role) migrates as structured fields on the Compensation Custom Object if the customer confirms the benchmark provider allows data portability. If the benchmark data is licensed and restricted from export, we migrate only the customer's internally calculated benchmarks and flag the external market data gap in the handoff documentation.

gradar's gender pay gap regression analysis outputs migrate as a structured dataset. The analysis results are datasets, not system configuration, so they transfer as rows with role, grade, compensation value, and demographic variables. We deliver the dataset as structured records in a dedicated Custom Object (if space allows) or as a CSV manifest with field mapping documentation for the customer's HR admin to import into their analytics environment. Equal pay dashboards do not migrate as live reports.

gradar user accounts and role-based access assignments map to Bullhorn User records by email match. gradar's permission groups (evaluators, approvers, administrators) map to Bullhorn UserType roles. We flag any gradar user without an email-equivalent in Bullhorn for the customer's admin to provision before migration completes. Inactive gradar users do not get Bullhorn User provisioning by default but are listed in the user inventory for the customer's HR admin to decide.

gradar's job descriptions (including AI-assisted generation outputs) stored as rich text migrate to the JobOrder.description field in Bullhorn. Bullhorn's description field accepts rich text. If the customer uses Bullhorn's Candidate-facing job posting fields separately, we map gradar descriptions to the public-facing description rather than an internal-only field. Bullhorn's field length limits are confirmed during scoping for unusually long descriptions.

gradar evaluation dates and grade change history require explicit extraction from extended exports. Standard exports may surface only the current evaluation date. We request extended exports that include the evaluation timeline per job during scoping. Historical grade changes migrate as additional records in the Custom Object with an evaluation_date field and a previous_grade field to preserve the progression audit trail. Where historical data cannot be extracted, we document the gap and migrate the most recent evaluation record only.

Organizations with custom grade naming, custom factor sets, or custom competency libraries in gradar require explicit scoping to identify every non-standard element. We document all custom configurations during discovery and either create matching Custom Objects in Bullhorn (if within Bullhorn's limits) or deliver a written configuration plan for the customer's Bullhorn admin to implement post-migration. Custom field creation in Bullhorn requires Bullhorn Support involvement for certain field types.