Migrate from GoCo to Crelate

GoCo stores pre-hire candidate data as Employee records with a status indicating onboarding stage. We extract these records and load them into Crelate as Contact records tagged as candidates. The GoCo employee start_date becomes a custom field on Crelate's Contact rather than an employment date (since Crelate is an ATS, not an HRIS). Personal fields (name, email, phone, address) map directly; onboarding-specific fields (offer letter status, background check status) map to Crelate custom fields or Opportunity fields depending on the customer's desired tracking model.

GoCo's active job postings (openings tied to Hiring Workflows) map to Crelate Job records. The GoCo job title, description, department, and location map to equivalent Crelate Job fields. Job status (open, paused, filled) migrates directly. We exclude positions marked as filled or cancelled from the active migration set unless the customer requests historical placement records, which would map to Crelate's Opportunity or a custom placement tracking setup.

GoCo stores organizational structure (departments, locations, company profile) under Company Settings. We migrate the top-level company name and any subsidiary or location records as Crelate Company records. In a pure ATS migration (no employee data), the Company object in Crelate represents the recruiting client's organization rather than the candidate's employer; we confirm the customer's data model intent during scoping.

GoCo Hiring Workflows define pre-hire task sequences, document collection steps, and stage progression logic. GoCo does not expose these definitions in its public API. We document active Hiring Workflows during the discovery phase by requesting screenshots, exported workflow descriptions, or admin walkthroughs. We then produce a written step-by-step reconstruction guide mapped to Crelate's Workflow and Task templates. This is a manual rebuild step, not an automated export; we flag it as a separate reconstruction task for the customer's admin team.

GoCo associates Documents to Employee records using internal Employee IDs. We maintain a cross-reference map of GoCo Employee IDs to Crelate Contact IDs, then import documents as file attachments linked to the corresponding Crelate Contact record. Document type labels (offer letter, tax form, NDA, background check) are preserved in the file description or a custom field. We flag any documents with missing Employee associations as orphaned and surface them in the migration report for the customer to resolve before cutover.

GoCo Time Off balances track accrued and used PTO as an HRMS function. Crelate is an ATS and recruiting CRM and does not have a Time Off or PTO tracking object. We do not migrate Time Off data. For organizations also moving their HRIS to a separate system, Time Off balances would be migrated in that parallel track. We flag the boundary explicitly in the scoping document.

GoCo Time Tracking data (clock-in/out, timesheet entries) is an HRMS payroll function with no equivalent in Crelate's ATS data model. We do not migrate Time Tracking records. Organizations using GoCo's payroll features would route Time Tracking data to their chosen payroll platform in a separate migration track.

GoCo benefits enrollment data links health, dental, and retirement plans to Employee records. Crelate does not store benefits data; this is an HRIS function. We do not migrate benefits enrollment. Plan associations and enrollment status are flagged as requiring a separate HRIS migration if the customer is moving their full HR stack away from GoCo.

GoCo supports custom fields on Employee records across types: checkbox list, currency, date, dropdown, long text, opinion scale, radio list, number, short text, and file upload. We identify all active custom field definitions in GoCo during discovery and map them to Crelate's custom field equivalents on the Contact object (for candidate fields) or Job object (for opening-specific fields). Picklist-type custom fields in GoCo map to Crelate picklist fields with the same options. Multi-select options map to Crelate multi-select picklists. We pre-create the destination custom field schema in Crelate before importing any candidate records so that data lands in typed fields rather than free text.

GoCo's saved reports and analytics configurations are not exposed via the public API. We do not migrate report definitions. We export the underlying data (candidates, jobs, activity records) so that the customer can rebuild reports in Crelate's custom report builder or in an external BI tool. The customer receives a written data export package in CSV/JSON format alongside the Crelate migration.

GoCo's notification preferences, scheduled alerts, and email notification rules are user-specific and not accessible via the public API. We do not migrate these settings. We advise customers to document any critical automated notifications (new hire alerts, onboarding completion reminders) before the migration and to reconfigure them in Crelate's Workflow engine post-migration.

GoCo engagement records (notes, call logs, email threads) attached to candidate or employee profiles migrate to Crelate Activity records on the corresponding Contact. Notes become Crelate notes linked to the Contact. Call logs map to Call activity records with duration preserved. Email threads attach as activity entries with content preserved. We use Crelate's Activity Forms and Field Mappings feature to copy key answers (candidate availability, interview feedback, offer terms) from activity forms directly to Contact fields as part of the post-migration setup.