Migrate from Happy Hire to Zoho Recruit

Happy Hire candidate profiles (name, email, phone, resume file URL, source attribution, status) map 1:1 to Zoho Recruit Candidate records. The Candidate First Name and Last Name fields are required in Zoho Recruit; we flag any Happy Hire records missing Last Name during the export audit and set them to a 'not provided' placeholder per Zoho's migration documentation. Custom candidate fields from Happy Hire migrate as Zoho custom fields on the Candidate module, created before import.

Happy Hire Applications link a Candidate to a Job with stage, timestamp, notes, and scorecard data. Zoho Recruit models this as a Candidate record with one or more Job Applications (custom subform or linked section) referencing a Job Opening. We extract the application-stage history as a structured subform or as candidate notes, preserving the original stage name and transition timestamps. Scorecard ratings migrate as custom fields or formatted notes on the Candidate record.

Happy Hire Jobs (title, description, location, department, status, posting URL) map to Zoho Recruit Job Opening. We map the Happy Hire job status (active, closed, draft) to Zoho's Opening Status field. Active jobs receiving applications are kept open in the migration window until the cutover date so that in-flight applications are captured before the source is locked.

Happy Hire application pipeline stages (screening, interview, offer, hired, rejected, custom) map to Zoho Recruit Job Opening stage values. We create custom stage values in Zoho to match the source stage names where Zoho's defaults (New, Screening, Interview, Offer, Hiring, Lost) do not align. Stage probability percentages migrate as custom fields if tracked in Happy Hire.

Happy Hire users (name, email, role) map to Zoho Recruit Users. Zoho Recruit requires that migrating users do not already have a separate Zoho Recruit account; we flag any email conflicts during the audit and recommend closing duplicate Zoho accounts before migration. User roles (Admin, Recruiter, Hiring Manager) map to Zoho Recruit roles with corresponding field-level access.

Happy Hire Employee records (start date, department, employment status, role) represent post-hire data separate from candidate profiles. We migrate Employee records to Zoho Recruit as Candidate records with a custom field employment_status__c set to 'Active' and start_date__c carrying the original start date. Custom employee properties may require additional custom field creation in Zoho Recruit before import.

Happy Hire onboarding workflows include task checklists with assignees and completion statuses. We export task names, assignees (mapped to Zoho User records by email), due dates, and completion flags as Zoho Recruit Tasks. Subtask nesting in Happy Hire flattens to top-level tasks in Zoho Recruit unless the customer requests a custom subform structure; we document the flattening decision in the mapping spec.

Happy Hire scorecard templates and completed evaluations contain structured ratings and free-text notes. We export the scorecard structure as a Zoho custom section on the Candidate module and populate completed evaluations as formatted notes or as a custom picklist (rating values) plus a long-text field (evaluator comments). The relationship to the Candidate record is preserved by linking all scorecard entries to the same Candidate ID.

Happy Hire tracks active postings to external job boards as metadata on the Job object, including board name and posting URL. We record this as a custom multi-line text or multi-select field on the Zoho Job Opening record. Board-level analytics do not migrate; we note in the inventory that analytics reconnection depends on the job board integration being reconfigured in Zoho Recruit.

Happy Hire captures how a candidate was sourced (referral, job board, direct application, agency). We map this to a Zoho Recruit Candidate custom field (Source Channel or similar) with a picklist matching the source values present in Happy Hire. Source attribution is used for reporting in both systems; preserving it maintains pipeline analytics continuity.

Happy Hire tags applied to candidates (skills, certifications, clearance levels, flags) migrate as Zoho Recruit Tags or as a custom multi-select picklist field depending on the tag volume and whether the customer uses Zoho Recruit's tagging feature. Tags with free-form values (rather than a controlled vocabulary) require a custom field to preserve all distinct values.

Happy Hire custom fields at the Candidate level (beyond name, email, phone, resume) migrate to Zoho Recruit custom fields on the Candidate module. We pre-create the custom field in Zoho (with the correct field type: text, number, date, picklist, checkbox, etc.) before importing data. Any validation rules or conditional required fields defined in Happy Hire are documented for the customer to re-implement in Zoho's field settings post-migration.