Migrate from Jarvi to Zoho Recruit

Jarvi Candidates map directly to Zoho Recruit Candidates. The Zoho Last Name field is mandatory and will reject records with no last name; we apply a 'not provided' placeholder to any Jarvi Candidate with a missing or empty lastName field during extraction. Jarvi's candidate status (active, inactive, placed) maps to the Zoho Candidate Status picklist. We preserve the original Jarvi candidate ID in a custom text field jarvi_id__c for cross-reference during the parallel-run window.

Jarvi's CRM-layer Contacts (client and prospect records) map to Zoho Recruit Contacts. Contact lifecycle stage in Jarvi (prospect, active client, dormant) maps to the Zoho Contact Status or a custom picklist field. The Zoho Last Name requirement applies to Contacts as well; we flag any Contact without a last name during scoping and apply the 'not provided' placeholder. Company association in Jarvi (linked Company record) maps to Zoho Contact's Account lookup, which we resolve after the Clients module is imported.

Jarvi Job postings and requisitions map to Zoho Recruit Job Openings. Job status (open, closed, on hold) maps to the Zoho Job Opening Status picklist. We preserve job-to-candidate associations as Zoho Job Opening Application records, linking each Candidate to the relevant Job Opening via the Candidates tab inside the Job Opening module. The posting channels used in Jarvi (LinkedIn, Indeed, direct) do not migrate as configuration; we note them in a custom text field posting_channels__c for the admin to reconfigure in Zoho's job distribution settings.

Jarvi allows custom pipeline stage definitions per job or per CRM deal, with stage names and win/loss states varying by organization. We extract the complete stage schema (stage names, ordering, probability percentages, and win/loss states) during scoping and map it to a Zoho Sales Process per Job Opening type. Zoho stage picklist values are created in Setup > Customization > Pipelines and correspond to the candidate's position in the hiring pipeline. We preserve stage probabilities as Zoho percentage fields if the customer's workflow relies on them for reporting.

Jarvi Activities (emails sent, LinkedIn messages, calls, meetings, tasks) are stored as timeline records linked to a Contact or Candidate. We map outreach actions to Zoho Tasks with TaskSubtype set to Call for phone activities and Task (generic) for todo items. Meeting activities map to Zoho Events with StartDateTime, EndDateTime, and Location preserved. The original Jarvi channel attribute (email, LinkedIn, WhatsApp, phone) is stored in a custom picklist field original_channel__c so the admin can filter by channel in Zoho. Note: Zoho does not have a native WhatsApp or Telegram connector; multichannel threads are flattened into standard activity records.

Jarvi Company records (firmographic data: industry, size, revenue tier) map to Zoho Recruit Clients. Client is the top-level organizational record in Zoho Recruit's CRM layer, analogous to Account in other CRMs. We use the Jarvi Company name as the Client name and map Jarvi's industry and size fields to Zoho Client's corresponding fields or to custom fields if the standard fields do not cover the required granularity. Clients are imported before Contacts to satisfy the Account lookup dependency.

Jarvi Conversation threads (LinkedIn InMail, email, WhatsApp, Telegram, SMS) are stored as a unified thread per Contact or Candidate. We map each message in the thread to a Zoho EmailMessage record (for email channel) or a Task record (for LinkedIn, WhatsApp, Telegram) with the message content stored in the Description or Comments field and the original channel stored in a custom picklist field. Zoho's IMAP sync on Enterprise and POP3 on all tiers can pull new email after cutover, but historical thread context from Jarvi's inbox is migrated as flat activity records without the threaded UI context.

Jarvi exposes a UUID-based Custom Fields API supporting text, number, date, and dropdown types for Candidates and Contacts. We retrieve the field schema during scoping, then create matching custom fields in Zoho Recruit before data migration begins. Text fields map to Zoho's Single Line, Multi Line, or Email field types depending on content. Date fields map directly. Dropdown fields map to Zoho Picklist. Note that custom fields are not available on Zoho Recruit's Free Edition and are limited to 50 per module on Standard; we flag any schema that exceeds the target edition's limit and recommend a Professional or Enterprise upgrade, or we consolidate less-critical fields into a JSON-serialized text field as a fallback.

Jarvi attachments (resumes, cover letters, uploaded documents) are stored as file metadata and reference URLs linked to Candidate profiles. We export the file content alongside candidate records where accessible via the Jarvi API. Files are uploaded to Zoho Recruit's Document Library and linked to the corresponding Candidate record via Zoho's Attachment related list. If a file reference URL is stale or inaccessible at migration time, we flag it in the reconciliation report and note the filename and candidate for manual re-upload by the admin.

Jarvi's AI agent generates candidate summaries, profile evaluations, and outreach suggestions that are stored as linked data points on the Candidate record rather than standalone objects. We export these as custom text fields (multi-line) on the Zoho Candidate record. The original summary text is preserved in full. If the customer's Zoho edition does not support custom fields, we flag the orphaned AI data and recommend regenerating summaries post-migration using Zia on the Professional tier or a third-party AI tool.

Jarvi Owners (recruiters and admins) are mapped to Zoho Recruit Users by email address. We extract all distinct Owner IDs referenced on Candidate, Contact, Job, and Activity records and attempt to match by email against the destination Zoho Recruit User table. Any Jarvi Owner without a matching Zoho User is held in a reconciliation queue. Note from Zoho documentation: users who already have a separate Zoho Recruit account must close that account before they can be imported into the company's Recruit account; we flag these in scoping.

If Jarvi stores interview records as a distinct object (linked to a Candidate and Job Opening with scheduled time, interviewer, and feedback), we map them to Zoho Recruit's Interview module. Interview status (scheduled, completed, cancelled) and interviewer assignment migrate as-is. Interview scorecards and feedback forms do not migrate as structured templates; we deliver a written inventory of the Jarvi scorecard fields for the admin to recreate as Zoho Interview form fields post-migration.