Migrate from GoHire to BambooHR

GoHire Jobs map to BambooHR Job Openings. We transfer the full job record: title, description, location, department, and open/closed status. The GoHire job ID is preserved in a custom field gh_job_id__c for audit traceability. GoHire department assignments map to BambooHR Department if that taxonomy exists in the destination; otherwise it is stored as a custom text field for the admin to reconcile post-migration.

GoHire Candidate profiles map to BambooHR Applicants. Contact information (name, email, phone, address), work history, and education migrate as standard Applicant fields. The original GoHire candidate ID is stored in a custom field gh_candidate_id__c. Resume files are exported from GoHire's built-in bulk download tool by the customer before migration kickoff and reimported as attachments to the corresponding BambooHR Applicant record.

GoHire Applications link a Candidate to a Job and carry source attribution (which job board or direct link generated the application). We preserve the Candidate-to-Job linkage by matching on the gh_job_id__c custom field after Jobs are loaded. The application source channel migrates as a custom text field. Application status (applied, screening, interview, offer, hired, rejected) maps to the corresponding BambooHR Application status values; any GoHire stages that do not map directly become custom Application status options that we document for the customer to activate in BambooHR settings.

GoHire's configurable candidate pipeline stages vary by customer setup. We discover the exact stage names during the source audit, then map each to a BambooHR Application status or custom status option. Stage order is preserved in the mapping document. If BambooHR's Application status options do not cover the full GoHire pipeline (for example, a 'background check' or 'reference check' stage), we document the gap and the admin adds those statuses in BambooHR settings before migration loads Applications.

GoHire custom screening questions attached to a Job are stored as custom fields with response values per Candidate. We transfer response values as structured data into equivalent BambooHR custom fields on the Applicant object. The screening question text itself (the field label) is recreated manually in BambooHR's Custom Field Builder by the customer post-migration, because BambooHR's import mechanism handles field values but not the definition of new custom field labels. We provide a field creation guide referencing GoHire's question text.

GoHire interview scheduling records and associated calendar invites migrate as calendar events in BambooHR. Meeting link preferences (GoHire's own self-scheduling link, Google Meet, Outlook) do not carry forward — we document the meeting tool used per interview and the customer configures a replacement in BambooHR or their calendar tool post-migration. Interviewer assignments, date, time, and location transfer where available.

GoHire hiring team members (recruiters, hiring managers, administrators) transfer to BambooHR as User accounts. We match by email address and map GoHire role labels (Admin, Recruiter, Hiring Manager) to the nearest BambooHR permission level. The customer admin reviews User access levels post-migration because BambooHR's permission model is structured around HRIS roles that may not map one-to-one from GoHire's ATS-specific roles.

GoHire's core differentiator is its multi-job-board publishing layer. We extract the job board association metadata for each GoHire Job (which boards the listing was published to, publication date, board-specific status). This data has no native equivalent in BambooHR's ATS. We preserve it as a structured reference document listing each GoHire Job, its associated boards, and the board-specific URL where available. The customer uses this document to re-publish listings on the destination boards of their choosing — BambooHR does not have a native multi-board distribution feature.

GoHire custom fields on Jobs are discovered at scan time and mapped to equivalent BambooHR custom fields on the Job Opening object. BambooHR enforces a 400-field ceiling per account across all object types, which we check during scoping. If the combined custom field count across all objects approaches this limit, we surface it before migration begins and work with the customer to archive or consolidate fields that are no longer in active use.

GoHire custom fields on Candidates map to BambooHR custom fields on the Applicant object. Custom field data types are matched during the mapping phase: text fields to text, numeric values to number, dates to date, and multi-select values to a type-compatible BambooHR field. BambooHR's Custom Field Builder is used to provision any new fields before data loading begins. Field IDs are fetched per customer via GET /v1/meta/fields as required by BambooHR's field-reference model, then used in the import payload.