Migrate from Zimyo to Zoho Recruit

Zimyo's talent acquisition module stores candidate profiles including contact information, work history, education, skills, resume attachments, and application status within its Employee or Candidate object. We extract these as Candidates in Zoho Recruit. The mapping requires careful handling of the Last Name mandatory field: Zoho Recruit rejects any Candidate row without a Last Name value. We flag all records where Last Name is null during scoping and apply a fallback strategy (extracting from Full Name splitting, using 'Unknown' as a placeholder, or requesting source-system correction) before import. Email address migrates as the primary candidate identifier.

Zimyo job postings (title, description, department, location, employment type, requirements) map to Zoho Recruit Job Opening records. Each Job Opening in Zoho Recruit has a status (Open, Closed, On Hold, Draft) that we derive from Zimyo's posting status field. Primary skills and qualifications migrate as picklist or text fields in Zoho Recruit's Job Opening custom fields.

Zimyo's configurable hiring pipeline stages map to Zoho Recruit's Candidate Status values within each Job Opening. We document the stage sequence during scoping and configure Zoho Recruit's pipeline stages to match the original Zimyo workflow. Stage names are preserved for audit purposes even if the customer chooses to rename stages post-migration.

Interview records from Zimyo (interviewer name, date and time, interview type, duration, location or video link, candidate reference, and job reference) map to Zoho Recruit's Interview module. We resolve candidate and job opening lookups during import so interviews are linked to the correct records in Zoho Recruit. Interviewer notes and feedback migrate as Interview feedback form responses.

Zimyo stores structured evaluation data (rating criteria, scores, overall recommendation, interviewer comments) against applications. These map to Zoho Recruit's Assessments module linked to the relevant Candidate and Interview record. Rating scales require mapping during scoping: we normalize any non-5-point scales to Zoho Recruit's available assessment scale and flag any unstructured free-text evaluations that may not map cleanly.

Offer records from Zimyo (candidate, job, salary, benefits, start date, offer status, terms) map to Zoho Recruit's Offer module. Offer status (Pending, Accepted, Rejected, Withdrawn) migrates directly. Compensation amounts require attention if the source data is INR-denominated and the destination Zoho Recruit org is USD-based; we flag currency fields during scoping and apply exchange-rate timestamps where conversion is required.

Zimyo users with recruiter or hiring manager roles (name, email, role, department) map to Zoho Recruit Users. Zoho Recruit requires at least one existing User in the account before importing Users via CSV. We extract the user list first, resolve duplicates (Zoho Recruit rejects users who already have a separate Zoho Recruit account), and provision any missing Zoho Recruit User records before the candidate migration phase begins. Active versus inactive status maps directly.

Resume files and attachments stored against candidate profiles in Zimyo migrate as Zoho Recruit Attachments linked to the corresponding Candidate record. We preserve original filenames, upload timestamps, and file type metadata. File integrity checksums verify successful transfer. Attachments larger than Zoho Recruit's upload limits are flagged for manual re-upload or alternative hosting with a link stored in the record.

Organization-specific custom fields added to standard objects in Zimyo's ATS module (such as referral source tracking, background check status, security clearance level, or visa eligibility) are discovered during scoping and recreated in Zoho Recruit as custom fields. We match Zimyo field types to Zoho Recruit equivalents: text fields, picklists, multi-select picklists, date fields, checkboxes, and numeric fields all have direct Zoho Recruit counterparts. Lookup relationship fields require additional Zoho Recruit configuration before import.

Zimyo departments and organizational hierarchy from the ATS module (distinct from the HRMS org structure) map to Zoho Recruit's Department setting. Department is used as a filter and grouping dimension in Zoho Recruit's Job Openings and reporting. Location data migrates as a Zoho Recruit location or as a custom picklist field depending on the customer's Zoho Recruit configuration.

Zimyo payroll runs (earnings, deductions, tax withholdings, reimbursements, net pay per cycle) have no Zoho Recruit equivalent. Zoho Recruit is an ATS and does not store payroll data. If the customer uses Zoho People for HRMS functions, payroll data may belong there instead; we flag this as a separate engagement scope and deliver a written inventory of payroll run records requiring a Zoho People migration or an alternative HRMS destination.

The core HRMS objects in Zimyo — employee records, attendance logs, leave management balances, performance review cycles, and benefits enrollments — have no destination in Zoho Recruit's ATS data model. We deliver a written inventory of these object types with record counts and recommended next steps (Zoho People migration, another HRMS platform, or archival export) for the customer's admin. Workflows, automations, and approval chains do not migrate; we document them for admin rebuild.