Migrate from GoCo to Zoho Recruit

GoCo Employee records map to Zoho Recruit Candidates when the migration scope includes pre-hire data or when the company tracks former employees as candidates for future roles. We map the Employee first_name, last_name, personal_email, and phone to the Candidate's Full Name and Email fields. Employment status and hire date determine whether a record is migrated as an active Candidate or held for a separate HRMS migration to Zoho People. Active employees hired within the last 90 days who went through GoCo's Hiring Workflow are the strongest migration candidates. Employee termination_date is not mapped to Zoho Recruit since the ATS does not manage employment status post-hire.

GoCo Hiring Workflows define the sequence of tasks, document collection steps, and approvals for new hires. Zoho Recruit does not have a Hiring Workflow object — the equivalent is a Job Opening with Candidate records at defined stages (Applied, Phone Screen, Interview, Offer, Hired). We extract the Hiring Workflow structure during discovery, document the task sequence and stage transitions, and map them to Zoho Recruit Job Opening stages and Candidate status values. The customer manually rebuilds the automation logic in Zoho Recruit Workflow Rules using the documented map as the specification.

GoCo Documents attached to Employees during the hiring process (offer letters, tax forms, signed agreements, background check results) migrate to Zoho Recruit Attachments. We preserve the document type label as a Zoho Recruit Custom Field on the Attachment record and associate each document to the corresponding Candidate using the Employee-to-Candidate cross-reference map built during the extraction phase. If GoCo Documents reference custom types not available in Zoho Recruit's standard attachment taxonomy, we create custom fields before migration and map the document type value there. The 4 GB file size limit per Zoho Recruit migration import is respected during the import phase.

GoCo's company-level configuration (departments, locations, organizational hierarchy) maps to Zoho Recruit Client records. The GoCo company name becomes the Client name in Zoho Recruit. GoCo departments map to Zoho Recruit Departments, which are available in both Standard and Professional tiers and control candidate-to-client assignment. Location and address data from GoCo company settings become Client address fields in Zoho Recruit. If GoCo's organizational hierarchy includes parent-subsidiary relationships, we map these to Zoho Recruit Client hierarchies using the Client ID reference.

GoCo custom fields on Employee records are identified during discovery and mapped to Zoho Recruit custom fields on the Candidate module. We create the destination custom fields in Zoho Recruit before migration using the Field Level Customization tool, matching field types (text, picklist, date, number) to their Zoho Recruit equivalents. Picklist values are mapped individually; multi-checkbox fields in GoCo become multi-select picklist in Zoho Recruit. Custom fields that have no equivalent in Zoho Recruit (e.g., benefits-specific fields that belong in Zoho People) are flagged and excluded from the Zoho Recruit migration scope with a note to migrate them to the HRMS system instead.

GoCo user accounts map to Zoho Recruit Users. We resolve by email match. Any GoCo user account without a matching Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision before candidate record import begins. User roles ( recruiter, hiring manager, admin) are mapped to Zoho Recruit profiles and roles, with the caveat that Zoho Recruit's security model uses Profiles and Data Sharing Rules that differ from GoCo's internal permission structure.

GoCo Time Off balances, accrual policies, and pending requests have no equivalent object in Zoho Recruit. This data belongs in an HRMS, not an ATS. We do not migrate Time Off records. If the customer's migration includes moving to Zoho People for HRMS functions, Time Off migrates there as a separate track. If GoCo remains the HRMS of record, Time Off data stays in GoCo and the customer accepts a dual-system environment.

GoCo Time Tracking data (clock-in/out records, timesheet entries) has no equivalent in Zoho Recruit's ATS data model. Zoho Recruit does not track employee hours or attendance. We do not migrate Time Tracking records. Companies requiring time and attendance tracking should evaluate Zoho People or a dedicated time-tracking tool as part of their broader HRMS migration.

GoCo benefits enrollment data (plan associations, enrollment status, carrier details, contribution amounts) has no equivalent in Zoho Recruit. This is HRMS data that belongs in Zoho People or a dedicated benefits administration platform. We do not migrate benefits enrollment to Zoho Recruit. If the customer is moving their full HR stack to Zoho, benefits enrollment migrates as a separate track to Zoho People; otherwise it remains in GoCo.

GoCo general Workflows that automate HR tasks beyond hiring (e.g., anniversary reminders, compliance document renewals, PTO approval routing) have no direct Zoho Recruit equivalent. Zoho Recruit Workflow Rules handle recruitment-specific automation (candidate status changes, interview scheduling, email triggers). We document the active general Workflows during discovery, including trigger conditions and actions, and deliver a written reconstruction plan for the customer's admin. We do not rebuild these workflows in Zoho Recruit as the triggers and actions are HR-specific, not ATS-specific.

GoCo saved Reports and analytics configurations are not exposed via the public API. We do not migrate report definitions. We export the underlying data (Employee records, Time Off, Time Tracking where applicable) so that reports can be rebuilt in Zoho Recruit using Custom Reports and Dashboards or in Zoho Analytics for cross-module reporting.

GoCo notification preferences and scheduled alerts are user-specific and not exported via the public API. We do not migrate notification settings. The customer's admin documents any critical automated alerts during discovery so they can be reconfigured in Zoho Recruit Workflow Rules post-migration.