Migrate from Vtiger All-In-One CRM to Nutshell

Vtiger Accounts map directly to Nutshell Company records. Standard fields — company name, website, industry, annual revenue, phone, address — map cleanly via Nutshell's native Company fields. Account number and type fields migrate to custom fields if the destination Nutshell plan supports them; otherwise they are flagged as candidates for a notes field consolidation. The Company record is the first object imported so that Contact records can reference it via the account_id linkage during the Contact phase.

Vtiger Contacts map to Nutshell Person records with the Contact-to-Account relationship preserved as a Person-to-Company link in Nutshell. Name, email, phone, title, address, and social profile fields migrate natively. Custom fields on Contact require field-type mapping — Vtiger picklist, checkbox, and currency types must align with Nutshell's equivalent field types. We generate a field-type comparison table during scoping and apply transformations before import.

Vtiger Leads map to Nutshell Lead records with Vtiger Lead_Status mapped to Nutshell Lead status values and Vtiger Lead_Source mapped to Nutshell's source field. Industry and rating fields from Vtiger migrate to custom fields in Nutshell if no native equivalent exists. Unconverted Vtiger Leads are treated as raw prospects; converted Vtiger Leads that have been turned into Contacts are imported as Nutshell Persons rather than Leads to avoid double-importing the same contact.

Vtiger Potentials (deals) map to Nutshell Deals with Sales Stage mapped to Nutshell pipeline stage, Amount mapped to deal value, Close Date mapped to expected_close, and Pipeline assignment mapped to Nutshell's pipeline. Multi-pipeline configurations in Vtiger require a pipeline-mapping step in Nutshell before migration; Nutshell Business plan and above support unlimited pipelines. Closed-won and closed-lost reasons migrate to custom fields if the customer uses them.

Vtiger Help Desk Tickets map to Nutshell Cases with Ticket status mapped to Case status, priority mapped to priority, assigned agent mapped to the responsible Person in Nutshell, and related Contact linked via the Person reference. Internal notes migrate as Case comments. Note that Vtiger's round-robin assignment rules and social ticketing channels are configuration settings that do not migrate; we deliver a written list of active routing rules for the customer's admin to reconfigure in Nutshell's case settings.

Vtiger Products with pricing and stock information map to Nutshell Products. Product name, SKU, unit price, and vendor associations migrate to Nutshell's product fields. If Vtiger Products reference the Inventory module for stock tracking, those dependencies are noted separately because Nutshell does not have a native inventory management module. Products must exist in Nutshell before Quotes can reference them, so Product import is sequenced before Quote import.

Vtiger Quotes migrate to Nutshell Quotes, but Vtiger gates the Quotes module behind the Inventory module — if Inventory is disabled in the source account, Quote records will not exist in the export. We check the source account's module configuration before data extraction and flag any disabled modules that suppress expected records. If Inventory is disabled, we advise the customer to enable it before running the export, or we note that Quote data will be absent from the migration scope. Quote line items require Products to exist in Nutshell first, so the import order is Products before Quotes.

Vtiger Sales Orders with line items, totals, and status map to Nutshell Quotes or Order records depending on the customer's Nutshell plan tier and usage pattern. Sales Orders require Products to exist in the destination first to maintain referential integrity, so we sequence Products before Sales Orders. Vendor linkage from Vtiger Purchase Orders is not natively supported in Nutshell and is flagged for manual reference or a notes field consolidation.

Vtiger Tasks under Projects and standalone Tasks migrate to Nutshell Task records with assignee, due date, status, and description preserved. Vtiger subtask hierarchy is flattened to top-level tasks in Nutshell if the destination does not support nested task structures, and this flattening is noted in the reconciliation report. Task assignment resolves by matching Vtiger owner email to the corresponding Person record in Nutshell.

Custom fields on Vtiger Accounts, Contacts, Potentials, and Help Desk migrate to Nutshell custom fields mapped by type. Vtiger picklist fields become Nutshell dropdown fields; checkbox fields become Nutshell checkbox fields; currency fields become Nutshell number or currency fields depending on the plan. We generate a field-type comparison table during scoping and apply transformations before the primary import. Custom field values on all parent objects are included in the relevant object import phase rather than as a separate step.

Vtiger exports attachments as individual files per record with no bulk download option in the standard UI. For migrations with more than 500 attachments, we stage files in object storage and re-associate them with their parent records after the primary data import completes. For smaller attachment sets, we include attachment URLs in the relevant object import and re-link using Nutshell's attachment API. This adds a step to the migration timeline and requires the customer to provision adequate destination storage.