Migrate from GoCo to Bullhorn ATS & CRM

GoCo Employee records map to Bullhorn Candidate records. We migrate firstName, lastName, email, phone, address fields, hireDate, employmentStatus, jobTitle, department, and compensation fields as custom fields on the Candidate record. The GoCo employeeType property maps to a Bullhorn custom Candidate field. We preserve the GoCo Employee ID in a custom field goco_employee_id__c for cross-referencing during document association. Active Employees migrate as active Candidates; terminated Employees migrate as inactive Candidates with a separation date in the custom field.

GoCo Employees who are also hiring managers, HR administrators, or company contacts in the Bullhorn context map to ClientContact records in addition to their Candidate record. The mapping is determined during discovery by examining which GoCo Employee records have access roles beyond being a pure employee. We use email as the dedupe key and create a cross-reference between the Candidate and ClientContact records.

GoCo's company-level departments and locations map to Bullhorn ClientCorporation records representing the customer's own organization within Bullhorn. If the customer uses GoCo to track multiple legal entities or subsidiaries, each entity becomes a separate ClientCorporation with its own staffing data scope. The department hierarchy maps to a custom field or custom object structure in Bullhorn depending on edition.

GoCo Documents (offer letters, tax forms, signed agreements) migrate as ContentDocument records attached to the corresponding Bullhorn Candidate via ContentDocumentLink. We build a cross-reference map of GoCo Employee ID to Bullhorn Candidate ID during the Employee migration phase and apply it during document import. Document type labels (offer letter, I-9, W-4) map to Bullhorn's document category structure. Custom document types in GoCo map to custom ContentVersion tags.

GoCo Time Off balances and accrual policies require Bullhorn Custom Objects if the customer needs structured balance tracking. We assess the destination Bullhorn edition during scoping: Bullhorn ATS allows 2 Custom Objects, Bullhorn Front Office Growth and Enterprise allow 10. If Custom Object slots are available, we create a Time_Off_Balance__c Custom Object with fields for accrual type, balance amount, accrual rate, and last updated date. If no Custom Object slots remain, balances migrate as custom fields on the Candidate record. Pending or future-dated requests are sequenced to apply after the hire date in Bullhorn.

GoCo Time Tracking records (clock-in/out, timesheet entries) do not have a native Bullhorn equivalent since Bullhorn is not a time and attendance platform. For staffing agencies tracking candidate availability or assigned hours, we create a Custom Object (Hours_Tracking__c) with fields for date, hours worked, and project or job assignment. For organizations that do not require structured time tracking in Bullhorn, we export the historical time tracking data as a CSV and attach it as a ContentDocument to the relevant Candidate or Placement record for reference.

GoCo Hiring Workflow templates define pre-hire task sequences and onboarding steps that are not retrievable via GoCo's public API. We document the active Hiring Workflows during discovery by reviewing the customer's GoCo account and recording the task sequence, assignees, and completion criteria. This documentation is delivered as a written Workflow Inventory with recommended Bullhorn equivalents: Bullhorn Business Rules for automated task creation on Candidate status changes, or a manual Task checklist attached to the Job Order for complex multi-step sequences. The customer's Bullhorn admin rebuilds the workflow logic post-migration.

GoCo general Workflows automate HR tasks beyond hiring and are not exposed via the public API. We document active workflows during discovery and deliver a written inventory specifying the trigger, conditions, actions, and recommended Bullhorn Business Rule equivalent. Bullhorn Business Rules trigger on entity create/update events and can set field values, create tasks, or send email notifications. Complex conditional logic requiring multiple branches or wait actions may need manual reconstruction as a Bullhorn Workflow or a task-based checklist.

GoCo custom fields on Employee records migrate to Bullhorn custom Candidate fields (customText1-50, customDate1-10, customCheckbox1-20 depending on data type) for straightforward mappings. Fields requiring structured multi-value data (dropdown lists with more than 20 values, related records, or file attachments) may require Bullhorn Custom Object creation. Bullhorn requires Support ticket creation to provision Custom Objects; we include this step in the migration plan and verify the customer's Bullhorn edition supports the required count (ATS Growth 0, Bullhorn ATS 2, Front Office Growth/Enterprise 10).

GoCo benefits enrollment data linking plan types and enrollment status to Employee records migrates to Bullhorn as structured data on the Candidate record or as a Benefits_Enrollment__c Custom Object. Plan names, carrier details, contribution amounts, and coverage levels migrate as text and currency fields. If the destination Bullhorn edition lacks Custom Object slots, benefits data maps to a group of custom fields on the Candidate record. We flag any benefits data that cannot be mapped due to field type constraints for customer review.

GoCo Employee records with an assigned Owner (HR admin, manager) map to Bullhorn User records by email match. We extract distinct owner emails from GoCo, match against the Bullhorn User table in the destination org, and create a mapping record. Any GoCo Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before the Candidate import phase.

GoCo saved Reports and analytics configurations are not exposed via the public API and do not migrate. We export the underlying GoCo data (Employee records, Time Off, Time Tracking) as CSV and JSON during discovery so the customer's Bullhorn admin can rebuild reports against the migrated dataset in Bullhorn's reporting module. We document the GoCo report names and the data sources they reference as part of the handoff package.