Migrate your GoCo data

Employee records are the core object in GoCo's API. We migrate Employee profiles including personal information, employment status, compensation fields, and employment dates as a 1:1 mapping. Owner assignment maps to the designated HR admin or manager in GoCo.

GoCo associates Documents to Employee records. We preserve document type labels (offer letters, tax forms, signed agreements) and map them to the destination system's document categories. Custom document templates require field-level re-creation in the target system.

GoCo tracks Time Off balances and accrual policies. We migrate current balances, accrued amounts, and policy configurations. Pending or future-dated time off requests are sequenced to avoid applying balances to inactive periods in the destination system.

Time Tracking data in GoCo includes clock-in/out records and timesheet entries. We map these to the destination's equivalent timesheet object, but timezone handling must be reviewed per migration since GoCo stores local timestamps. Hourly employees' tracking data is migrated as time entries.

Hiring Workflows are GoCo templates that orchestrate pre-hire tasks and onboarding steps. We map the workflow structure and task sequence, but destination platforms often represent these differently (as task lists, checkboxes, or automation rules). We reproduce the intent as close-aligned objects in the target system.

GoCo Workflows automate HR tasks beyond hiring. We map active workflow definitions and their trigger conditions, though complex conditional logic may need manual reconstruction in the destination platform. We document the original workflow map for the customer's review.

GoCo's saved Reports and analytics configurations are not exposed via the public API. We do not migrate report definitions. We export underlying data so reports can be rebuilt in the destination system, and we flag which reports require manual re-creation during the scoping call.

GoCo's 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 before migration so they can be reconfigured in the destination system.

GoCo stores company-level configuration including departments, locations, and organizational hierarchy. We migrate these as structural data but map department IDs to the destination system's equivalent. Benefit plan associations require value-level mapping since plan names vary between systems.

GoCo supports custom fields on Employee records. We identify all active custom field definitions and map their values to the destination's custom field schema. If the destination lacks an equivalent custom field, we flag it for manual review and offer to populate a text property as a fallback.

Benefits data in GoCo links plans to Employee records. We migrate plan associations and enrollment status. Detailed benefit plan content (carrier details, contribution amounts) is mapped as structured data. Some benefits configurations may require re-entry in the destination system's benefits admin module.