Migrate from GoHire to Zoho Recruit

GoHire Jobs map to Zoho Recruit Job Openings with full field fidelity: job title, description, requirements, department, location, and open/closed status transfer directly. Job board distribution metadata from GoHire (which boards each job was posted to) migrates as structured custom fields (e.g., board_indeed__c, board_monster__c) so the admin can re-publish without re-entering board associations. GoHire's job type and employment classification map to Zoho's Job Type and Work Type picklist values. We validate that job description HTML is stripped of any GoHire-specific markup before import to prevent rendering issues in Zoho's job portal.

GoHire Candidate profiles (name, email, phone, work history, education, skills, source channel) map directly to Zoho Recruit Candidate records. GoHire's candidate source attribution (which job board, direct link, or referral generated the application) transfers to Zoho's Source and Source Type fields. Resume files exported from GoHire's bulk download are re-attached to the corresponding Zoho Candidate record as ContentDocument linked via ContentDocumentLink. Candidate status (active, archived) maps to Zoho's Candidate Status picklist.

GoHire Applications link a Candidate to a Job and carry stage history. Zoho Recruit represents this as a Candidate record linked to a Job Opening via the Candidate subform or via the Application object (accessible through the Jobs module). We preserve the application date, current pipeline stage, and stage-change timestamps as structured data. The source job board or campaign attribution migrates as a custom field on the association record. If the GoHire migration involves multiple applications per candidate, each application-to-job link is created as a separate Job Opening association in Zoho.

GoHire's configurable candidate pipeline stages (e.g., Applied, Screening, Interview, Offer, Hired) map to Zoho Recruit's Job Opening stage picklist values. We define the stage mapping during scoping based on GoHire's existing stage names and create a Zoho Sales Process (under Setup > Job Openings > Sales Process) that whitelists the migrated stage values. Stage probability percentages from GoHire (if set) migrate as stage probability fields in Zoho. The mapping document is agreed with the customer before any records move.

GoHire custom screening questions attached to a Job (stored as custom fields on the job) have their response values transferred as structured Zoho custom fields on the Candidate record. The question text itself (the prompt) requires recreation in Zoho's Custom Form Builder under the Job Opening module. We document every screening question with its response options and answer type so the admin can reconstruct the form in Zoho. Free-text screening responses migrate as Note records linked to the Candidate.

GoHire interview scheduling records (date, time, interviewer, location or meeting link, status) map to Zoho Recruit Interview records linked to the Candidate and Job Opening. GoHire's interview outcome or feedback summary migrates as an Interview Feedback Form response in Zoho. GoHire's self-scheduling link preferences (Google Meet, Outlook, GoHire's own scheduler) do not transfer; the customer recreates their scheduling integration preferences in Zoho's Interview Scheduling settings post-migration.

GoHire hiring team members (recruiters, hiring managers, admins) are mapped to Zoho Recruit User accounts by email match. We extract every owner and team member referenced on Jobs, Candidates, and Applications and reconcile against the destination Zoho Recruit User list. Any GoHire team member without a matching Zoho User is added to a reconciliation queue; the customer provisions the Zoho account before that user's records import. Role and permission sets from GoHire are documented for manual remapping in Zoho's Security Settings.

GoHire custom fields on Jobs are discovered during scan and mapped to Zoho Recruit custom fields on the Job Opening module. Text fields map to Zoho Single Line or Multi Line; numeric fields map to Zoho Number; date fields map to Zoho Date; picklist fields map to Zoho Picklist with the same options. If Zoho Standard tier is in use, we work within the 50 custom fields per module limit and prioritise fields that drive reporting or workflow criteria. Enterprise tier (300/module) accommodates most GoHire custom schemas without trimming.

GoHire custom fields on Candidates (beyond standard contact fields) map to Zoho Candidate custom fields using the same type-mapping logic as Job custom fields. Candidate-specific data like preferred location, availability date, notice period, or salary expectation transfers as structured fields where possible. Candidate notes with semi-structured content that cannot map to a typed field are attached as Note records.

GoHire's careers page builder output (branding, job listing layout, company description, culture content) is not a structured data object and does not migrate as records. We export the careers page content as a template document and deliver it alongside the migration package so the customer's admin can paste it into Zoho Recruit's Career Site builder (available on all paid tiers). We flag which GoHire job board URLs were associated with each listing so re-posting can be tracked.

GoHire's job board distribution records (which jobs were posted to which boards, posting dates, and listing IDs) transfer as structured custom fields on each Job Opening. For example, board_indeed_url__c stores the Indeed listing URL; board_monster_posted__c stores the posting date. This preserves the distribution history so the admin can manage re-posts or cancellations in Zoho without rebuilding the board list from scratch. We flag any jobs where Indeed's formatting requirements may cause re-publish issues (per GoHire's own documentation on Indeed compliance).

GoHire's candidate engagement notes (recruiter comments, internal communication logs attached to a candidate profile) map to Zoho Recruit Notes linked to the Candidate via ContentDocumentLink. Note timestamps preserve the original GoHire creation date for audit. We do not migrate email threads stored within GoHire as separate engagement records unless they are exported as a structured data set; the customer's GoHire data export determines what candidate-level notes are available for transfer.