Migrate from RESUMate to Zoho Recruit

RESUMate Candidate records map directly to Zoho Recruit Candidate. Core fields (name, email, phone, parsed resume text) migrate as CSV column mapping through Zoho Recruit's built-in import wizard. We apply the DaXtra parser mapping configuration in Zoho Recruit to standardize resume-extracted fields against the migrated schema. RESUMate's unlimited notes per Candidate migrate as Zoho Recruit Notes (free-text activity entries) linked to the parent Candidate record. Any Resume Files stored as attachments migrate as Zoho Recruit attachments on the Candidate record.

RESUMate Client records map to Zoho Recruit Client (displayed as Organization in the UI). The Client name, address, and contact fields map to Organization fields. RESUMate Client-to-Job-Order links are preserved by resolving the Client ID as a Zoho Recruit Client lookup value on the migrated Job Opening records. Clients are imported before Job Openings to satisfy the required lookup dependency.

RESUMate Job Order records map to Zoho Recruit Job Opening. Job title, description, requirements, department, and location migrate to the corresponding Job Opening fields. Job Order status (active, filled, on hold) maps to Zoho Recruit Job Opening status values. The Client lookup on Job Opening is resolved to the migrated Client record by Client name or ID during the transform phase.

RESUMate Active Jobs are filtered views of Job Orders organized by pipeline stage and status. These are derived views, not a separate object. We extract Active Jobs data to capture pipeline stage assignments and apply them as a custom picklist field or Job Opening sub-status in Zoho Recruit. Zoho Recruit's visual pipeline (kanban stage view) is configured to reflect the customer's Active Job stages after migration.

RESUMate Send-outs track when a Candidate is submitted to a Job Order—a core Part IV workflow in the RESUMate Getting Started Guide. We extract send-out records including submission date, submission status, and client reference, then import them as Zoho Recruit Candidate submissions linked to the migrated Job Opening and Candidate records. The Candidate-to-Job-Opening relationship established by send-outs becomes the foundation of the Zoho Recruit hiring pipeline view.

RESUMate Groups are named segmentation lists for Candidates, Clients, or Job Orders. We extract Group membership data as tag records and map them to Zoho Recruit Tags. Tags are created in Zoho Recruit before bulk Candidate import so that tag assignments can be applied during record insertion. Group names that exceed Zoho Recruit's tag character limit are truncated to the maximum allowed length.

RESUMate supports unlimited custom fields with no schema constraints. Zoho Recruit Standard allows 50 custom fields per module and Professional allows 300 per module. We discover the full custom field schema during discovery and create equivalent custom fields in Zoho Recruit before import. Field types are mapped: RESUMate text fields become Zoho Recruit single-line or multi-line text fields; date fields map to Zoho Recruit date fields; numeric fields map to Zoho Recruit long integer or decimal fields. Custom fields exceeding Zoho Recruit's per-tier limit are flagged for the customer to resolve before migration.

RESUMate Calendar events tied to Candidates, Clients, or Job Orders migrate as Zoho Recruit Event records. Event type, date, duration, location, and attendee information are mapped to the Zoho Recruit Event schema. Events are imported after Candidates, Clients, and Job Openings so that the WhoId (Candidate or Client) and WhatId (Job Opening) lookups resolve correctly.

RESUMate stores resume attachments in a proprietary format alongside parsed resume text. We extract original resume files as binary attachments and import them to Zoho Recruit as Candidate record attachments. Both the parsed resume text (migrated as structured fields) and the original file are preserved to give the Zoho Recruit team full access to source documents for re-parsing or reference.

RESUMate Owner records map to Zoho Recruit Users. We resolve RESUMate owners by email match against the Zoho Recruit User table. If the customer has existing Zoho Recruit users with matching emails, those records are linked. Any RESUMate Owner without a matching Zoho Recruit User goes to a reconciliation queue for the admin to provision before Candidate and Job Opening import continues. Zoho Recruit requires at least two users to exist before the native import wizard can be used.

RESUMate's relational database maintains explicit links between Candidates, Clients, and Job Orders. Zoho Recruit establishes these links through lookup fields on Candidate (Client lookup) and through submission records (Candidate-to-Job Opening association). We resolve these links during the transform phase by querying migrated record IDs and writing them as foreign key values in the Zoho Recruit import CSV. This is the most critical transformation step for preserving the three-way relational integrity.

RESUMate parses resume text into structured candidate fields during import. We extract both the parsed field values and the raw resume text. Parsed values map directly to Zoho Recruit Candidate fields during CSV import. Raw resume text is attached as a file for Zoho Recruit's DaXtra parser to re-parse on demand, allowing the customer to use Zoho Recruit's own parsing workflow for newly uploaded resumes going forward. This dual approach preserves structured data while enabling re-parsing capability.