Migrate from hireEZ to Zoho Recruit

hireEZ candidate profiles with contact details, work history, skills, education, and engagement activity map directly to Zoho Recruit Candidates. We deduplicate on candidate email as the canonical key. Because hireEZ contact accuracy is reported at 70-80% with approximately 30% bounce rates, we validate email addresses against standard deliverability patterns during import and flag records with high-risk contact data (missing domain, non-standard format, duplicate at high confidence) for customer review before re-engagement. hireEZ's enriched profile fields (social profiles, salary expectations, availability) map to Zoho Recruit custom fields or standard fields where equivalents exist.

hireEZ Projects store requisition context including job title, department, location, salary range, and pipeline stage assignments. These map directly to Zoho Recruit Job Openings. We preserve the project-to-candidate association so that candidates remain linked to the originating requisition in Zoho Recruit's candidate pipeline view. Stage assignments from hireEZ map to Zoho Recruit's candidate status values within each Job Opening, with a custom field hireez_original_stage__c preserving the source stage label for audit.

hireEZ Talent Pools are named collections of candidates grouped by skill, role, or talent community. Zoho Recruit has no native Talent Pool object, so we map pool membership to Tags in Zoho Recruit, with each pool becoming a tag of type TalentPool. We also create a multi-select picklist field hireez_talent_pool__c on the Candidate object that captures all pools a candidate belongs to, preserving the many-to-many relationship. The customer chooses the tagging strategy during scoping based on their reporting needs.

hireEZ Campaigns store outreach sequences across email, SMS, and InMail channels with membership and engagement history. We migrate campaign membership (which candidates were in which campaigns) as Tags on the Candidate record, preserving the association for segmentation purposes. We do not transfer sequence step states or cadence logic, as these are tied to hireEZ's internal messaging infrastructure and cannot export cleanly. Post-migration, the customer rebuilds outreach cadences using Zoho Recruit's Blueprint workflows or a third-party sales engagement tool.

hireEZ activity logs capture email opens, clicks, replies, InMail views, and scheduling events tied to candidate engagement. We migrate the full activity timeline per candidate as notes or custom activity records in Zoho Recruit, preserving timestamps and engagement type. Note that hireEZ activity data sourced through ATS integration may have timestamp formats that vary by connected platform; we normalize to ISO 8601 during import. The activity timeline ordering is preserved by setting the activity date to the original hireEZ timestamp.

Interview scheduling events and calendar syncs from hireEZ migrate to Zoho Recruit Interview records linked to the corresponding Candidate and Job Opening. Scheduling metadata including interview type, interviewer, date/time, and location transfers directly. Interview status (scheduled, completed, cancelled) is preserved in a custom field hireez_interview_status__c.

hireEZ custom fields on candidate profiles vary by customer configuration. We discover all custom properties during scoping, map them to Zoho Recruit custom fields with appropriate field types (text, picklist, date, numeric, checkbox), and flag any with no matching target in Zoho Recruit's standard schema. Custom field mapping is validated in the staging migration before production import.

Enterprise hireEZ customers using Auto Sync have bidirectional candidate records synchronized between hireEZ and a connected ATS. When pulling data through the connected ATS rather than hireEZ's UI exports, we deduplicate on candidate email and resolve conflicting stage assignments by preferring the most recent update timestamp. Records without an email match are flagged for manual review before import.

hireEZ owners (recruiters assigned to candidates and projects) map to Zoho Recruit Users. We resolve owners by email match. Any hireEZ Owner without a matching Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Requisition metadata including department, location, employment type, priority, and salary range from hireEZ Projects maps to corresponding Zoho Recruit Job Opening standard fields. Custom requisition fields migrate as Zoho Recruit custom fields on Job Opening.

Historical engagement records (emails sent, InMail views, responses) migrate as notes on the Candidate record in Zoho Recruit. We preserve the engagement type, timestamp, and content summary. Detailed sequence state (step number, wait status, next-step date) does not transfer because hireEZ sequences are tied to their internal messaging infrastructure.

hireEZ native reports and dashboards do not export in transferable format. We migrate underlying funnel data (source, stage, hire) as candidate activities and custom fields to support basic funnel reporting in Zoho Recruit. Dashboard-level analytics require reconstruction in Zoho Recruit's custom reports and dashboards or Zoho Analytics.