Migrate from Vtiger Sales to Zoho CRM

Vtiger Organization records map directly to Zoho CRM Account. Organization name becomes Account Name; industry, website, phone, address fields map 1:1. We use Organization ID as a cross-reference for Contact linkage resolution. If any Vtiger Deal or Quote references an Organization, the Account must exist before those records import because Zoho Opportunity WhatId requires a valid Account reference.

Vtiger Contact records map to Zoho Contacts with the account_name lookup resolved to the target Account ID. Name, email, phone, title, mailing address, and custom Contact fields migrate directly. We preserve the Vtiger contact_id as a custom field vtiger_contact_id__c for reconciliation. If a Contact in Vtiger has no linked Organization, we create a stub Account using the Contact's company name or a 'No Account' placeholder to satisfy Zoho's Account requirement.

Vtiger Lead records map to Zoho Leads. Lead source, status, rating, and custom fields migrate 1:1. We map Vtiger leadstatus to Zoho Lead Status values. Any lead scorings or custom qualification fields are preserved as custom Zoho fields. The customer's admin decides whether to convert Leads in Zoho after migration or maintain them as a separate record type for audit purposes.

Vtiger Deals map to Zoho Potentials (Zoho's Opportunity equivalent). Deal name, amount, closing date, probability, and sales stage map directly. The key mapping challenge is the Account lookup: if the Vtiger Deal is linked to an Organization, we resolve the target Account ID. If the Deal is linked directly to a Contact without an Organization, we create or identify the corresponding Account first, then set the Potential's Account lookup to that Account rather than to the Contact.

Vtiger deal stages and pipeline assignments map to Zoho Potential Stage values. We read the customer's current Vtiger stage names, probabilities, and pipeline assignments and configure matching Stage values in Zoho CRM under Settings > Pipelines > Stages. Stage order and probability percentages are preserved. Any closed-lost and closed-won custom reasons in Vtiger are mapped to Zoho Loss Reason and Won Reason picklist values.

Vtiger Quotes map to Zoho Quotes with line items preserved. Quote-to-Deal linkage maps to Quote-to-Potential linkage via the resolved Potential ID. Product names, quantities, list prices, discount percentages, and tax amounts migrate. We validate that each Quote's parent Potential exists in Zoho before Quote import to avoid orphaned quote records.

Vtiger Sales Orders map to Zoho Sales Orders. The Quote-to-Sales-Order linkage is preserved by resolving the Quote reference to its Zoho equivalent. Billing and shipping addresses, PO reference number, and line items migrate. We validate that the parent Quote and Potential exist before the Sales Order imports.

Vtiger Invoices map to Zoho Invoices. Invoice number, date, due date, line items, payment status, and related Contact and Organization references migrate. Invoice-to-Sales-Order linkage is preserved through the resolved Sales Order ID. Payment status flags and balance due amounts are mapped to Zoho's Invoice status field.

Vtiger Help Desk Tickets map to Zoho Cases. Ticket status, priority, category, assigned agent, and customer replies migrate. Vtiger's conversation threads (customer and agent replies) map to Zoho Case Comments in chronological order. The Contact who submitted the ticket is linked to the Case via the Contact lookup. We flag any tickets with no linked Contact or Organization for admin review.

Vtiger Project records map to Zoho Projects. Milestones, tasks, subtasks, assignees, due dates, and time tracking data migrate. Task dependencies are preserved as custom fields or task notes since Zoho Projects uses a different dependency model. Kanban and list view configurations do not transfer as layout data; we document the current view states for the admin to reconfigure in Zoho Projects.

Vtiger custom fields on any standard module (Contact, Organization, Deal, Ticket, Project) are extracted with their field names, data types, and values. We pre-create matching custom fields in Zoho CRM using the corresponding Zoho field type (single-line for text, multi-line for long text, picklist for option sets, date for date fields, currency for monetary values). Custom field mapping is validated during the sandbox migration before the production import.

Vtiger Price Books store product-to-price mappings as separate objects. Zoho CRM does not have a Price Book equivalent; pricing is managed directly on Product records. We unroll each Vtiger Price Book entry into a Zoho Product record with the price populated in the Standard Price field. If a Vtiger product appears in multiple Price Books with different prices, we create one Zoho Product per price book entry. This is a manual specification step that the customer's admin reviews before we execute the unroll.