Migrate from ZingHR to Zoho Recruit

ZingHR's talent acquisition submodule stores candidate records as part of the hire-to-rehire employee lifecycle. We extract candidate profiles, contact details, resume attachments, and sourcing metadata from ZingHR's recruitment module and map them to Zoho Recruit's Candidate module. Zoho Recruit requires Last Name as a mandatory field for every candidate; records missing a last name in ZingHR receive a placeholder value 'Not Provided' that the customer's admin reviews post-migration. Candidate status (applied, screening, interview, offer, hired) maps to Zoho Recruit's candidate status pipeline.

Active job postings in ZingHR's talent acquisition module map directly to Zoho Recruit Job Openings. Each job opening's title, description, department assignment, location, employment type, and hiring manager transfer as standard Zoho Recruit fields. Active job count limits vary by Zoho Recruit plan (1 on Free, 10 per recruiter on Standard, 20 per recruiter on Enterprise); we flag any migration scope that exceeds the customer's selected plan tier before record import begins.

We extract ZingHR users with a recruiter or hiring-manager role and map them to Zoho Recruit Users. Zoho Recruit has a specific constraint: a user who already holds a separate personal Zoho Recruit account cannot be migrated into a company Zoho Recruit account until that separate account is closed. We identify any users with pre-existing Zoho Recruit accounts during scoping and flag them for account resolution before migration begins. First Name, Last Name, email address, and role (Recruiter, Hiring Manager, Interviewer) transfer to Zoho Recruit's user profile.

ZingHR department hierarchies and cost centers map to Zoho Recruit Departments. We extract the full org chart from ZingHR's Reports module and create matching department records in Zoho Recruit, preserving the parent-child department relationships. Department assignment on Job Openings links to the migrated department records via Zoho Recruit's department lookup field.

ZingHR's manager-employee reporting lines extract from the Manager Hierarchy object. In Zoho Recruit, the hiring manager and assigned recruiter on a Job Opening and the assigned recruiter on a Candidate are User lookups. We resolve the manager assignments at migration time by matching the manager's email from ZingHR against the migrated Zoho Recruit User records. Any manager without a matching Zoho Recruit User goes to a reconciliation queue for the customer's admin to provision.

ZingHR's hire-to-rehire module includes digital onboarding checklists and task assignments for new hires. We split this data: active onboarding task assignments that relate to pre-hire preparation map to Zoho Recruit Tasks linked to the Job Opening; onboarding tasks that have already converted to employee workflow items (benefits enrollment, IT provisioning) are flagged as out-of-scope for Zoho Recruit and noted in the handoff document as requiring a separate HRMS destination.

Employee documents stored in ZingHR's ESS portal — offer letters, ID proofs, experience letters — that are attached to candidate records in the hiring context migrate to Zoho Recruit's Document Library and attach to the corresponding Candidate or Job Opening via ContentDocumentLink. We map ZingHR document categories to Zoho Recruit's folder structure, and flag any documents classified as post-hire HR records (payroll documents, performance reviews) as out-of-scope for Zoho Recruit migration.

ZingHR's Attribute Master API exposes company-specific custom fields used in the hiring module. We enumerate all custom candidate attributes during scoping, map them to Zoho Recruit custom fields per module (50 custom fields per module on Standard, 300 on Enterprise), and handle picklist value translation where ZingHR picklists differ from Zoho Recruit picklists. Custom fields that exceed the destination plan's limit are flagged for the customer to prioritize or upgrade.

ZingHR's hiring analytics (time-to-hire, source effectiveness, pipeline conversion rates) are available in the Reports module. We migrate the underlying data so that equivalent reports can be rebuilt in Zoho Recruit. Standard Reports are available on Zoho Recruit Standard and above; Custom Reports require the Enterprise plan. We deliver a written mapping of every ZingHR recruitment metric to its Zoho Recruit equivalent with the required plan tier noted.

ZingHR attendance punch-in/punch-out data is an HRMS record with no Zoho Recruit equivalent. Zoho Recruit is a talent acquisition system and does not track employee attendance. We extract attendance data during scoping to produce a migration inventory but do not load it into Zoho Recruit. The customer must migrate attendance records to a dedicated HRMS destination (Zoho People, for example) as a separate project.

Leave entitlement, accrual history, and balance data in ZingHR is an HRMS record type with no Zoho Recruit analog. Zoho Recruit's scope is recruiting operations, not employee leave management. We document leave balance records in the migration inventory and flag them as requiring a separate HRMS destination.

Payslip data, earnings, deductions, and net pay records in ZingHR are payroll history records with no Zoho Recruit equivalent. We extract the current payroll year data during scoping as a reference archive but do not load it into Zoho Recruit. Payroll migration requires a separate engagement targeting Zoho People or another payroll-capable HRMS.

Goals, feedback, and structured performance evaluation records in ZingHR's PMS module are HRMS data beyond Zoho Recruit's recruiting scope. We include the performance review module in the scoping inventory but do not migrate these records to Zoho Recruit. A separate migration plan targeting a full HRMS is required if performance data must be preserved.

ZingHR tracks candidate sourcing channels in the talent acquisition module. We map the source channel value (LinkedIn, referral, job board, agency) to Zoho Recruit's Candidate Source field. On Enterprise tier, Source Boosters are enabled for unlimited daily sourcing lookups; on Standard, Source Boosters are capped at 250 per day.