Migrate from Vtiger All-In-One CRM to Zoho CRM

Vtiger Accounts (called Organizations in some exports) map directly to Zoho CRM Accounts. The account name, website, phone, industry, and address fields align cleanly. We use the account name as the dedupe key during import. Accounts must be imported before Contacts so that the Account-Contact lookup relationship is satisfied at insert time.

Vtiger Contacts map to Zoho CRM Contacts with first name, last name, email, phone, and mailing address fields preserved. The Contact-to-Account relationship is resolved by matching the Vtiger account name to the Zoho Account created in the previous phase. Custom fields on Contact (picklists, checkboxes, date fields) are type-mapped to their Zoho equivalents before import.

Vtiger Leads map to Zoho CRM Leads. The Vtiger lead_status and lead_source fields map to Zoho Lead Status and Lead Source picklists respectively. Any industry or rating fields on the Vtiger Lead migrate as custom fields or standard Zoho fields depending on the customer's schema design. Leads without a matching Contact in Vtiger are kept distinct from the Contact import phase to prevent duplication.

Vtiger Potentials map to Zoho CRM Opportunities. The potentialname becomes the Opportunity subject, amount maps to Amount, closingdate maps to Closing Date, and sales_stage maps to Stage. Pipeline assignment in Vtiger maps to a Zoho CRM pipeline configured during schema design. Closed-Lost and Closed-Won reasons from Vtiger custom fields become Zoho Loss Reason and Won Reason picklist values.

Each Vtiger deal pipeline becomes a Zoho CRM pipeline with corresponding stages. We configure the pipeline in Zoho's Blueprint or pipeline settings before Opportunity import, whitelisting only the stage values present in the source data. Stage probability percentages from Vtiger migrate to Zoho Probability fields rounded to Zoho's accepted integer range.

Vtiger Help Desk Tickets map to Zoho CRM Cases (Service Plus module) or Zoho Desk Tickets if the customer activates Zoho Desk post-migration. We preserve ticket status, priority, assigned agent, related Contact, and internal notes. Round-robin assignment rules from Vtiger are documented as a Zoho Desk assignment rule configuration task for the admin rebuild. Status mapping uses Vtiger's ticket status values mapped to Zoho Case Status picklist values.

Vtiger Products with pricing, stock information, and vendor associations migrate as Zoho Products. Product code, unit price, and tax settings transfer directly. Note that Vtiger bundles Products under the Inventory module, so we check whether Inventory is enabled before extracting Product records. Products must be imported before Quotes and Sales Orders to satisfy the product lookup in line items.

Vtiger Quotes migrate to Zoho Quotes with line items, totals, and status preserved. This mapping requires the Vtiger Inventory module to be enabled; if it is not, we flag the dependency during discovery and advise the customer to enable it before export. We sequence Quotes after Products so that the product lookup resolves correctly. Quote PDFs from Vtiger are attached as files to the corresponding Zoho Quote record.

Vtiger Sales Orders migrate to Zoho Sales Orders with vendor linkage and line items. Vendor records (as Accounts or as a separate Vendor module if the customer uses one) must exist in Zoho before Sales Orders import to maintain referential integrity. We validate that each Sales Order's linked vendor Account is present in Zoho before loading.

Vtiger Projects with task dependencies and milestones map to Zoho Projects or Zoho CRM Projects if the customer activates the Projects module in Zoho CRM. Task-level dependencies (Finish-to-Start) are preserved as task links or dependency fields where the destination schema supports them. If Zoho Projects is not activated, we map to Tasks within the CRM with a project identifier field for grouping.

Vtiger Tasks (standalone and under Projects) migrate to Zoho Tasks with assignee, due date, and status preserved. Subtask hierarchy is mapped to Zoho's subtask structure if the destination supports it; otherwise we flatten to top-level tasks and note the hierarchy as a custom field for manual grouping post-migration. Task status values (Not Started, In Progress, Completed, Deferred, Planned) map directly to Zoho's task status picklist.

Vtiger exports attachments as individual files per record with no bulk download option in the standard UI. For migrations with fewer than 500 attachments, we extract them alongside their parent records and re-associate via Zoho's file attachment API during import. For migrations with more than 500 attachments, we stage files in object storage, then re-associate them with their parent records after the primary data import completes. This adds a step to the migration timeline and requires the customer to provision adequate Zoho storage.