Migrate from ZenHR to Zoho Recruit

ZenATS Candidates transfer to Zoho Recruit Candidate records. We map ZenATS first_name and last_name fields to Zoho Recruit's First Name and Last Name; if ZenATS stores full name in a single field, we split on the last space or flag records requiring manual name resolution. Candidate email, phone, current_position, and current_company map to their Zoho Recruit equivalents. Source attribution (candidate origin channel) maps to Zoho Recruit's Source field. Any ZenATS custom candidate fields map to Zoho Recruit custom fields created before migration — but custom field carry-over via the Zoho Recruit-to-Zoho People integration is partial, so we scope which fields matter post-hire.

ZenATS Vacancies map to Zoho Recruit Job Opening records. The ZenATS vacancy title maps to Job Opening Title; vacancy status (Draft, Published, Closed, On Hold) maps to Zoho Recruit's status picklist. Assigned recruiters from ZenATS map to Zoho Recruit Hiring Team members via email matching. Job Requirements, Desired Skills, and Experience from ZenATS map to custom fields or the Description/Requirements text area in Zoho Recruit. If ZenATS has multiple job opening records per vacancy (internal and external), these map to separate Zoho Recruit Job Opening records with distinct workflow assignments.

ZenATS pipeline stages (e.g., Application Received, Screening, First Interview, Second Interview, Offer, Hired, Rejected) map to Zoho Recruit Job Opening Custom Status values. We pre-create the status workflow in Zoho Recruit before migration so that candidate records land in the correct stage. Stage history (timestamps and stage change records) transfers as candidate activity notes or as a custom multi-line field if the destination org supports it — native stage history audit trail is limited in Zoho Recruit's standard import process.

ZenATS interview records (scheduled date, interviewer, interview type, outcome, feedback) map to Zoho Recruit Interview records linked to the Candidate and Job Opening. Interviewer names resolve to Zoho Recruit Users via email match. Interview type and feedback scores map to custom Interview fields if not covered by Zoho Recruit's standard Interview Feedback form. Interview scheduling metadata (calendar invite status, meeting link) does not transfer as calendar events — it migrates as note text for the recruiting team's reference.

ZenHR Employees who were hired from ZenATS map to Zoho People Employee records through Zoho Recruit's Convert-to-Employee action. The native integration pushes candidate data (name, email, phone, position) into Zoho People automatically. However, the Reddit-sourced evidence on r/Zoho confirms that a lot of fields do not carry over through the Zoho Recruit-to-Zoho People connection — banking information, custom fields, and HRMS-specific data require manual re-entry in Zoho People. We flag all employee fields that the customer wants preserved post-conversion and advise manual entry or a secondary data pass into Zoho People after the ATS migration completes.

ZenHR tenant-specific custom fields on employee profiles and requests require a pre-migration field discovery audit because every ZenHR install has unique field configurations. We enumerate every active standard and custom field with its type and mandatory/optional flag, then pre-create matching custom fields in Zoho Recruit before migration. Custom fields are available on all paid Zoho Recruit tiers (Standard: 50/module, Professional: 300/module, Enterprise: unlimited) but not the Free edition. Lookup fields require Professional or Enterprise. Formula fields also require Professional or Enterprise. We scope the destination edition during discovery and create only supported field types.

ZenATS candidate attachments (resumes, cover letters, portfolio files) transfer as Zoho Recruit Candidate Attachments linked to the migrated Candidate record. Binary file transfers are handled via Zoho Recruit's file upload API with the original filename and MIME type preserved. We extract resume text for candidates where ZenATS stores a parsed resume to populate the Skills and Work Experience sections in Zoho Recruit's structured candidate profile. File size limits are respected per Zoho Recruit's attachment constraints.

ZenATS vacancy statuses (Active, On Hold, Closed) map directly to Zoho Recruit Job Opening status values. We run a status audit before migration to identify any ZenATS statuses that have no Zoho Recruit equivalent and map them to the closest standard value, documenting the decision in the mapping spec. Closed vacancies transfer with their historical data but are set to Closed status in Zoho Recruit so they do not appear in active recruiter queues.

ZenATS candidate communication logs (email and SMS metadata — timestamps, template names, recipient addresses) transfer as Zoho Recruit Candidate Activity records or Notes. The email and SMS body content is not exposed via the ZenHR standard API and does not transfer automatically. We flag this gap during scoping: if the customer requires full candidate communication history, we recommend a manual export from ZenATS before migration. Only metadata (send timestamp, template name, recipient) migrates as a candidate note for the recruiting team's audit trail.

ZenATS Users (recruiters, hiring managers) map to Zoho Recruit Users. Resolution is by email address match. A Zoho Recruit constraint applies: users who already have a separate Zoho Recruit organization account cannot be imported into the destination company account until that separate account is closed. We audit the ZenATS user list against existing Zoho Recruit accounts before migration and flag any conflicts for the customer's admin to resolve. Active versus inactive status maps to Zoho Recruit's active/deactivated user state.

ZenATS job board posting configurations (which boards a vacancy is posted to, posting dates, status per board) transfer as Zoho Recruit Job Opening job board distribution records or as custom fields tracking posting status. We map active board postings to Zoho Recruit's native job board integration configuration post-migration. Historical posting data (board names, original posting URLs) migrates as a note on the Job Opening record.

ZenATS offer letter records (offer date, proposed compensation, offer status) map to Zoho Recruit's candidate Offer object if the destination Zoho Recruit edition supports it (Professional and above), or to a custom Offer module we create during schema setup. Offer details migrate as structured records linked to the Candidate, preserving offer amount, start date, and status (Accepted, Rejected, Pending). Historical offer data is migrated even for closed vacancies to support reporting on offer-to-acceptance ratios.