Migrate from GoCo to Recruit CRM & ATS

GoCo Employee records split into two Recruit CRM objects. Active applicants and candidates sourced during GoCo onboarding sequences map to Recruit CRM Candidate records. The employing company (if the agency is staffing its own back-office) maps to Recruit CRM Contact with the role set to Internal. Employee personal fields — first name, last name, email, phone, address, start date, department, manager — map to Candidate fields or Contact fields depending on the record's role in the agency's placement pipeline. We preserve the original GoCo employee ID in a custom field goco_employee_id__c on the destination record for cross-reference.

GoCo departments and the organizational hierarchy map to Recruit CRM Company records. Each GoCo department becomes a Company entry in Recruit CRM with the department name as the Company name and the department head as the primary Contact. If the agency uses GoCo to manage its own organizational structure (rather than candidate-facing placements), we treat this as a configuration migration and set up the Companies in Recruit CRM before any Candidate or Contact import.

GoCo documents attached to Employee records (offer letters, signed agreements, tax forms, identification documents) map to Recruit CRM file attachments on the corresponding Candidate or Contact record. We use GoCo's Employee ID to destination ID cross-reference map to associate each document to the correct record during import. Document type labels (I9, W-4, NDA, offer letter) map to Recruit CRM's category or tag system. If GoCo documents are stored as URLs rather than binary files, we migrate the URLs as notes with the document type in the title for manual re-download if needed.

GoCo Time Off balances and accrual policies have no equivalent object in Recruit CRM. Recruit CRM is a recruiting ATS and CRM — it does not track employee time off. We export Time Off records as a structured CSV package during migration (employee name, balance, accrual date, policy name) and deliver it to the customer for import into their HR or payroll system. We flag this explicitly in the migration scope so no time-off data is inadvertently discarded.

GoCo clock-in/out records and timesheet entries do not map to Recruit CRM objects. Recruit CRM does not include a native time tracking module. We export timesheet data as a CSV package (employee name, date, hours worked, pay period) and flag that the customer should retain this in their payroll system or a dedicated timekeeping tool. Timezone conversion is applied to any timestamps in the export so the customer's payroll system receives accurate hours.

GoCo Hiring Workflow templates (pre-hire document collection, task assignment, onboarding step sequences) are not exposed via GoCo's public API. During discovery, we document the active Hiring Workflows via screen-shared walkthroughs with the customer's admin. We then map each workflow step to Recruit CRM's Pipeline and Stage definitions, adding tasks as Recruit CRM Checklist items per stage. Complex conditional branching (e.g., if document not signed within 3 days, send reminder) is documented as a written task sequence rather than automated, since GoCo's automation logic cannot be exported automatically.

GoCo general Workflows (HR task automations beyond hiring) are defined in the GUI and not retrievable via API. We document each active Workflow's trigger conditions, conditional logic, and automated actions during a discovery session, then deliver a written reconstruction guide mapped to Recruit CRM's task automation and pipeline rules. This is a manual handoff, not an automated migration, because the automation logic cannot be exported from GoCo's API.

GoCo custom fields on Employee records map to Recruit CRM custom fields on the corresponding object (Candidate for applicants, Contact for client-side records). We identify all active GoCo custom field definitions during scoping, map their data types to Recruit CRM field types (text to text, picklist to picklist, date to date, checkbox to checkbox), and pre-create the schema in Recruit CRM before import. Any GoCo custom fields without an equivalent Recruit CRM type are flagged for the customer to resolve before migration.

GoCo benefits enrollment links plan names and enrollment status to Employee records. Recruit CRM does not have a benefits enrollment object. We export benefits plan associations (employee name, plan type, carrier, enrollment status, coverage start date) as a structured CSV package for the customer's benefits administration system or HR records. We do not attempt to map this into Recruit CRM because no equivalent object exists.

GoCo saved reports and analytics configurations are not exposed via the public API. We do not migrate report definitions. We ensure all underlying data (Employees, Time Off, Departments) is available in Recruit CRM so the customer's team can rebuild reports in Recruit CRM's analytics module. We deliver a report inventory checklist documenting every GoCo report the customer has saved so none are lost during the transition.