Migrate from GoHire to Bullhorn ATS & CRM

GoHire Job records map to Bullhorn JobOrder with job title, description, requirements, department, location, and open/closed status transferred as structured fields. GoHire's job board distribution metadata (which boards the job was published to) transfers as structured fields on JobOrder so Bullhorn's own job board connectors can re-syndicate without re-entry. Indeed formatting compliance issues flagged during scan (where GoHire jobs may have failed Indeed's content standards) are surfaced before import so the customer can remediate before jobs appear in Bullhorn.

GoHire Candidate profiles transfer directly to Bullhorn Candidate records. Contact information, work history, skills, and application metadata map to Bullhorn's standard Candidate fields. Resume files are exported via GoHire's built-in bulk download tool (an admin-panel action, not an API endpoint) and reimported as Bullhorn Candidate attachments. We flag this bulk export requirement during migration kickoff so the customer exports resumes before closing GoHire access.

GoHire Application records link a Candidate to a Job and carry source attribution (which job board, direct link, or careers page generated the application). We preserve this linkage and source channel as the submissionDate, source, and humanSubmitter fields on Bullhorn JobSubmission. The Candidate-to-JobOrder relationship is resolved at migration time using the Job mapping.

GoHire pipeline stages are configurable per job and vary by customer setup. We map source stage names to Bullhorn Opportunity stages using a naming convention agreed with the customer during scoping. Stage probability percentages transfer to Bullhorn StageProbability. If the customer uses multiple GoHire pipelines, each maps to a Bullhorn Record Type on Opportunity with its own Sales Process whitelisting the relevant stages.

GoHire custom screening questions attached to a Job are stored as custom fields. Their response values transfer as structured data to Bullhorn custom fields on JobSubmission. The question text itself (as opposed to the candidate's answer) is preserved in a separate document delivered as part of the migration inventory so the customer's Bullhorn admin can recreate the screening question in Bullhorn's form builder.

GoHire interview scheduling records and associated calendar invite metadata transfer as Bullhorn Event records linked to the Candidate and JobOrder. We do not transfer GoHire's own self-scheduling link preferences, Google Meet vs Outlook meeting link types, or calendar invite settings. These require manual configuration in Bullhorn Calendar Settings post-migration.

GoHire hiring team member accounts (recruiters, hiring managers) transfer as Bullhorn User records. Role-based permissions from GoHire map to Bullhorn UserType (Admin, Standard, Limited) and the relevant Bullhorn permission sets. Users without a matching Bullhorn account enter a reconciliation queue for the customer's admin to provision before record import completes.

GoHire custom fields on Jobs are discovered at scan time and mapped to equivalent Bullhorn custom fields on JobOrder. Field types (text, number, date, picklist) are matched to Bullhorn field types. If the customer's Bullhorn edition limits custom fields on JobOrder, custom properties are promoted to a Custom Object with a lookup to JobOrder.

GoHire custom fields on Candidates are discovered at scan time and mapped to equivalent Bullhorn custom fields on Candidate. Multi-select picklists from GoHire map to Bullhorn multi-select picklist fields. Any custom properties exceeding Bullhorn's per-entity field limits migrate to a Custom Object with a Candidate lookup.

GoHire stores employer or client information linked to jobs as structured records. These map to Bullhorn ClientCorporation with company name, address, industry, and contact information. If GoHire does not maintain a separate employer record (many GoHire setups store this data only within the Job), we create ClientCorporation records from Job data during transformation.

GoHire's multi-job-board distribution layer records which boards (Indeed, Monster, CareerBuilder, SimplyHired) received each job listing and the posting status on each. This metadata transfers as structured fields on JobOrder (externalReference, boardName, postingStatus) so Bullhorn's own job board connectors can identify re-syndication requirements. If any GoHire jobs failed Indeed formatting compliance, we flag those separately before import.

GoHire notes attached to Candidates migrate as Bullhorn Note records linked via ContentDocumentLink to the parent Candidate record. Note body migrates as text with attachment references preserved as separate ContentDocument records. Timestamps are preserved for activity timeline ordering.

GoHire's built-in careers page builder configuration transfers as a written template document describing the job board categories, branding elements, filtering options, and styling choices. We do not migrate careers page code; the customer's Bullhorn admin rebuilds the careers page using Bullhorn's Career Portal (an open-source GitHub-hosted tool) or a CMS-based approach.