Migrate from GoCo to BambooHR

GoCo Employee records migrate to BambooHR Employee as a direct 1:1 mapping. We transfer personal information, employment status, compensation fields, hire date, and employment type. GoCo custom fields on Employee records map to BambooHR custom fields using type-matched equivalents (text, number, date, dropdown). We use GoCo's employee identifier as the dedupe key during import to prevent duplicate records. Any GoCo Employee field with no BambooHR equivalent is flagged in the mapping document for manual field creation in BambooHR admin.

GoCo Documents migrate to BambooHR Files with their type labels (offer letters, tax forms, signed agreements) preserved and mapped to BambooHR file categories. Documents associate to Employee records via a cross-reference map that links GoCo Employee IDs to the newly created BambooHR Employee IDs. This cross-reference is built during the Employee import phase and applied as a lookup during the document import phase. Custom document types from GoCo require BambooHR admin to define matching categories before import begins.

GoCo Time Off balances and accrual policy records migrate to BambooHR as Time Off entries with balances preserved. We migrate current balance amounts, accrued amounts, and pending or future-dated requests. Pending requests are sequenced to avoid applying balances before the employee's active status is confirmed in BambooHR. Accrual policy structures from GoCo map to BambooHR time-off policy configuration, and the policy assignment per employee migrates as a setup step in BambooHR admin.

GoCo Time Tracking records migrate to BambooHR Time Tracking with explicit timezone conversion. GoCo stores all timestamps in the company's local timezone setting; we convert these to the timezone configured in BambooHR or to UTC, and the conversion is flagged in the migration report. Organizations with employees across multiple timezones should verify BambooHR's multi-timezone support matches their needs before cutover. Timesheet entries map to BambooHR timesheet records with hours, date, and employee attribution preserved.

GoCo Hiring Workflow templates are not accessible via GoCo's public API, so they cannot be exported programmatically. During discovery, we collect screenshots, task lists, and step sequences from the GoCo admin, then document the full workflow structure. We deliver a written onboarding task template mapped to BambooHR's onboarding feature, with tasks, assignees, due-day offsets, and document requirements listed. Your BambooHR admin recreates the template in BambooHR Onboarding; we do not build this as automation code. Complex conditional logic in GoCo Hiring Workflows may require simplification in BambooHR.

GoCo general Workflows automating HR tasks beyond hiring are not exposed via API and require the same manual documentation approach as Hiring Workflows. We map trigger conditions, action steps, and conditional branches from screenshots provided by the GoCo admin during discovery. The output is a written checklist or task template for BambooHR, which your admin implements manually. BambooHR does not support the same event-driven automation model as GoCo, so conditional logic is reproduced as a structured task list with manual completion tracking.

GoCo company-level settings including departments, locations, and organizational hierarchy migrate to BambooHR's Company Info section. Department names and IDs from GoCo map to BambooHR departments with ID cross-referencing applied so that employee-to-department assignments resolve correctly. If GoCo stores multiple legal entities, we map each entity to a separate BambooHR location or department based on the customer's configuration preference. Structural data (departments, locations) migrates before Employee records to satisfy the dependency.

GoCo custom fields on Employee records migrate to BambooHR custom fields with type mapping applied. Text fields, number fields, date fields, and dropdown fields each map to their BambooHR equivalents. Any GoCo custom field type that does not have a direct BambooHR equivalent (such as GoCo-specific structured property types) is flagged in the mapping document for manual re-creation in BambooHR admin. The customer configures BambooHR custom field visibility and display tab during setup before Employee data is loaded.

GoCo benefits data links plan associations and enrollment status to Employee records. We migrate plan names, employee elections, and coverage tier status as structured data. Detailed benefit plan content including carrier details, contribution amounts, and plan rates is stored at the plan level in GoCo and maps as structured properties in BambooHR's benefits module. BambooHR's benefits administration is a separate add-on; if the customer has not licensed it, we migrate enrollment data as employee custom fields or as a structured import file that the customer uses during their next enrollment period.

GoCo saved Reports and analytics configurations are not accessible via GoCo's public API and do not migrate. We export the underlying employee, time off, and benefits data as structured CSV and JSON files so that the same data is available for rebuilding reports in BambooHR. We deliver a written catalog of every GoCo report the customer identifies, including its filter logic, column structure, and output format, so that BambooHR report rebuilding is a documented manual task for the customer's admin team.

GoCo notification preferences and scheduled alerts are user-specific and not exported via the public API. We do not migrate notification settings. We advise customers to document any critical automated alerts or notification rules in GoCo during discovery so that these can be recreated manually in BambooHR settings post-migration. Email notification defaults in BambooHR are configured at the account level and do not carry over from GoCo.