Migrate from HigherMe to Zoho Recruit

HigherMe job postings map directly to Zoho Recruit Job Openings. We extract job title, description (HTML preserved as rich text), location address, job status (open/closed/paused), and distribution status across integrated job boards. Screening questions migrate as custom fields on the Job Opening module (question text as field label, answer type mapped to Zoho field type: single-select as Picklist, multi-select as Multi-select Picklist, free-text as Text Area). Fit-score weighting configuration migrates as a note on the Job Opening record for admin reference during evaluation setup.

HigherMe Applications map to Zoho Recruit Candidates, preserving the application status progression (Applied, Screening, Interview, Offer, Hired, Rejected) as a custom picklist field hm_application_status__c. The source job reference links to the migrated Job Opening via a Lookup field. Application submission timestamp migrates as a custom date field hm_application_date__c. Source channel attribution (Indeed, Snagajob, direct) migrates as hm_source_channel__c.

HigherMe Candidate records (which aggregate all applications for the same individual across jobs and locations) map to Zoho Recruit Candidates at the contact level. We map candidate name, email, phone, and work authorization status. Geographic distance from the job location migrates as a custom numeric field hm_distance_miles__c. WOTC eligibility questionnaire responses and eligibility flag attach as hm_wotc_eligible__c (checkbox) with questionnaire answers preserved in hm_wotc_responses__c (text area). Non-US/Canadian applicants receive a migration flag hm_international_applicant__c for admin review post-migration.

HigherMe 30-second video cover letters are stored as hosted media URLs rather than downloadable video files. We preserve the URL reference in a custom URL field hm_video_cover_letter__c on the Candidate record, along with upload timestamp and duration metadata in companion text fields. We alert customers during scoping to verify whether Zoho Recruit's candidate portal or job application forms support video embedding. If the destination does not support embedding, candidates may need to re-record; the URL reference provides the original source until that decision is made.

HigherMe custom screening questions per job include single-choice (mapped to Zoho Picklist), multi-choice (mapped to Zoho Multi-select Picklist), and free-text (mapped to Zoho Text Area) types with weighted scoring. We create each custom field on the Job Opening module via Zoho Recruit's field-level customization (Setup > Customization > Modules > Job Openings > Layout Editor). Weighted scoring configuration is preserved as a note attachment for admin reference during evaluation criteria setup in Zoho. Note that Lookup fields and formula fields are not available in the Standard Edition; we adjust the field type selection based on the customer's Zoho Recruit edition during scoping.

HigherMe fit scores are calculated per application on a 0-100 scale based on availability match, distance from location, and screening question responses. The numeric score migrates to a custom Long Integer field hm_fit_score__c on the Candidate record. We map the score as a raw numeric value rather than a rank or tier so that Zoho Recruit users can build custom views, reports, and workflow conditions on the score directly. If the customer used band-based scoring (e.g., Excellent, Good, Fair), we also create a companion formula or picklist field hm_fit_tier__c with the tier labels.

HigherMe interview scheduling records (date/time, interviewer assignment, interview type: phone, video, in-person) map to Zoho Recruit Interview records. Interview type migrates as a picklist field hm_interview_type__c. Interviewer assignment resolves by email match against Zoho Recruit User records; unresolved interviewers go to a reconciliation queue for admin provisioning. Interview status (scheduled, completed, cancelled, no-show) migrates to hm_interview_status__c. Candidate and Job Opening lookups are resolved at migration time to satisfy Zoho Recruit's relationship requirements.

HigherMe manager notes and structured feedback attached to applications map to Zoho Recruit Notes records linked via Related List to the Candidate. Note body migrates as rich text with author name and creation timestamp preserved. Multi-author notes from different hiring managers each become separate Note records attached to the same Candidate. We flag notes with no author (system-generated) and assign them to a migration system user for post-migration admin review.

HigherMe multi-location franchise configurations (each store as a discrete hiring unit with its own job postings and applicant pool) require Zoho Recruit organizational mapping. We map each HigherMe location to a Zoho Recruit organizational level or, if the customer has configured Departments, to a Department record. Location address and manager assignment migrate as location metadata on the Candidate and Job Opening records via custom fields hm_store_id__c and hm_store_manager__c. We chunk the migration by location identifier during scoping to prevent cross-store applicant contamination; this requires a complete location inventory from the customer before migration phases are defined.

HigherMe background checks are managed through integrated third-party providers (First Advantage and similar) and are not stored as readable records within the ATS API. We do not migrate background check data. Candidates with completed checks will need to initiate a new check in Zoho Recruit or through their preferred background check provider post-migration. We document completed check dates as a note on the Candidate record referencing the external provider for compliance audit continuity.

Post-hire onboarding documents, I-9 forms, and new-hire paperwork live in HigherMe HR Software, a separate product tier from the ATS. We do not migrate onboarding document blobs as they fall outside the recruiting API scope. Customers requiring onboarding continuity should plan a parallel HR system migration or accept manual re-documentation for new hires.

HigherMe WOTC eligibility questionnaire responses and associated tax credit data attach to the candidate record. We preserve the questionnaire answers in hm_wotc_responses__c (text area) and eligibility flag as hm_wotc_eligible__c (checkbox). Note that WOTC eligibility is US-specific and tied to IRS tax credit qualification criteria; we flag the eligibility date and expiration if present in the source record. This data supports compliance continuity for franchise operators with active WOTC capture workflows.