Migrate from Asanify to Zoho Recruit

Asanify Employee records map to Zoho Recruit Candidate records as the primary object mapping. First Name and Last Name split from the Asanify full name field. Email, phone, current designation, and department transfer to equivalent Candidate fields. Employment status and joining date map to custom Candidate fields (asanify_employment_status__c, asanify_join_date__c). Any employee record with a role or background suitable for active recruitment pipelines qualifies for Candidate migration; current employees not in active hiring workflows may be imported as inactive candidates or archived per customer direction.

Asanify Contractor records are the strongest functional overlap with Zoho Recruit's Candidate model. Contract terms (contract start/end dates, contract type, rate, currency) map to Zoho Recruit custom fields since Candidate does not natively store contract-specific attributes. Multi-currency payout data from Asanify (stored at $18/contractor/month tier) transfers to a custom currency field. Contractor status (active, expired, pending renewal) maps to a custom Candidate field. The contractor module in Asanify is priced separately, so scoping must confirm the contractor tier is active before migration.

Asanify's department hierarchy and org chart map to Zoho Recruit Client records (representing the organizational client or business unit) and a custom department field on Candidate. Department assignments on employees transfer to the custom asanify_department__c field on each mapped Candidate. If the customer uses Asanify's multi-company org structure, each legal entity becomes a separate Client in Zoho Recruit with its own candidate pool.

Employee documents (offer letter, ID copies, employment contracts) stored in Asanify VIP tier transfer as file attachments to the corresponding Candidate record in Zoho Recruit. Document type labeling (offer letter, resume, ID proof) maps to Zoho Recruit's attachment category or a custom field. Documents require the VIP plan tier in Asanify; Essential-tier accounts do not have document storage and this object is out of scope for those accounts.

Salary revision history (effective dates, amounts, revision reason) has no native Zoho Recruit field. We export the salary revision log as a CSV and present it as a written record. If the customer requests, we store the most recent salary figure as a custom Candidate field (asanify_current_salary__c) for reference. Historical salary progression does not map to any Zoho Recruit object because the ATS is not designed to track compensation history.

Leave entitlement and accrual balances (annual leave, sick leave, earned leave, comp-off) have no Zoho Recruit equivalent. ATS platforms track candidate availability windows, not employee leave balances. We export leave balance data as a CSV report per employee for the customer's HR team to manage outside of Zoho Recruit. Leave encashment records similarly export as a written report.

Geo-tracked attendance logs (punch timestamps, coordinates, shift assignments) do not map to any Zoho Recruit object. ATS platforms do not store attendance data. We export attendance records as a CSV per employee for the customer's HR team. Bio-metric device integration records (VIP-only) are included in the export if present. Records with sparse or missing geo coordinates are flagged in the export with a null-coordinates indicator.

Payslip records (earnings breakdown, TDS deduction, PF contribution, ESIC, Professional Tax, net pay) have no Zoho Recruit equivalent. We export a per-employee payroll history summary as a structured CSV and a written record inventory. India statutory deduction amounts are preserved as-is from Asanify's payroll run output. Payslip PDFs are exported as file archives per employee. Any payroll runs in pending or in-progress state at migration time require explicit resolution: either the customer completes the run in Asanify before cutover or the run is archived as incomplete.

Performance management data (review cycles, ratings, 360-degree feedback, free-text review forms) is a VIP-tier feature in Asanify and has no Zoho Recruit equivalent. ATS platforms track candidate evaluations during hiring, not employee performance post-hire. We export performance review data as a written record with ratings, reviewer names, and feedback text per employee. Custom review question banks require a separate field extraction and are included in the written export scope.

OKR goal records (company-level OKRs, individual key results, progress percentages) are a VIP-tier feature in Asanify and have no Zoho Recruit equivalent. We export OKR data as a written record per employee with goal definitions, key results, current progress, and status. Goals and key results that reference other employees or departments are cross-referenced by ID in the export for manual reconstruction if needed. Flattened goal lists export as CSV alongside the written report.

KPI tracking definitions and current values (VIP-tier feature) do not map to Zoho Recruit. We export KPI records as a written inventory with KPI name, definition, current value, target, measurement frequency, and the employee to whom the KPI is assigned. Historical KPI snapshots are flagged separately if present in Asanify because the data model may store them differently from current values.

Shift definitions, assigned employees, and shift dates are a VIP-tier feature in Asanify. We export shift schedule data as a written record covering the most recent four-week representative window (rather than the full recurring pattern). Shift assignments per employee are linked by employee ID in the export. If the customer requires shift data in Zoho Recruit for scheduling or interview availability purposes, a custom Candidate field (asanify_shift_pattern__c) can be created, but standard ATS workflows do not natively consume shift schedule data.

Expense reimbursement records (amounts, expense categories, approval status, submission dates) are available on VIP and Enterprise tiers. We export reimbursement records as a written report. Pending reimbursements at migration time require explicit resolution: the customer must approve or reject all pending requests before cutover, or those requests are archived as unresolved in the written export. Rejected reimbursements do not transfer. Approved reimbursements export with approval metadata.

Employees onboarded via Asanify's EOR service are legally employed by a separate Asanify-owned entity in each country. Migrating EOR records to a non-EOR system (Zoho Recruit) requires either establishing a legal entity in that country or engaging a new EOR provider. We flag every EOR record with a written compliance notation: employer entity name, country of legal employment, EOR start date, and Asanify entity ID. If the customer requests, we create a custom Candidate field (asanify_eor_entity__c, asanify_eor_country__c) to preserve the EOR metadata on the candidate record for compliance visibility. EOR records do not convert to standard employee records without a legal review.