Migrate from Vtiger Sales to Nutshell

Vtiger Contact records map directly to Nutshell Person records. Standard fields (name, email, phone, address, title) migrate 1:1. The Vtiger Contact-to-Organization link (account_id) is resolved during migration by matching the linked Organization's name to a Nutshell Company record; if no matching Company exists yet, we create it first so that the Person-Company relationship is established at import time. Any custom Contact fields are mapped to Nutshell custom Person fields by name and data type.

Vtiger Organization records map to Nutshell Company records with a merge step: multiple Vtiger Organizations with identical or near-identical names (Levenshtein distance below 0.85) are consolidated into a single Nutshell Company to prevent duplicate Company records. This merge is documented in a reconciliation report before the Company import begins. Standard fields (company name, website, industry, address) migrate 1:1; any custom Organization fields map to custom Company fields.

Vtiger Lead records map 1:1 to Nutshell Leads. Lead status and lead source from Vtiger migrate as custom Lead fields in Nutshell if no standard equivalent exists. Leads without a matched Person or Company in Nutshell are imported as standalone Leads and flagged in the reconciliation report for manual review and conversion if appropriate.

Vtiger Deals (Potentials) map to Nutshell Deals. The dealstage value migrates to Nutshell's status field; probability and expected close date are preserved as custom Deal fields since Nutshell's standard Deal does not have a native probability field. The Vtiger pipeline assignment is stored as a custom pipeline_name field for reference. If the Vtiger Deal links to a Contact (person_id) or Organization (related_to), we link the Nutshell Deal to the corresponding Person or Company using the relationship resolution established during Contact and Organization migration.

Vtiger Quote records are migrated as custom Quote records attached to the corresponding Nutshell Deal. Quote line items, pricing, and tax information are stored in custom fields or a custom line-items relationship on the Quote custom object. We do not migrate Quote PDFs as these are binary files requiring separate file hosting; we flag their existence in the migration inventory and advise the customer to reattach them from Vtiger's document storage post-migration.

Vtiger Sales Orders are migrated as custom Sales Order records attached to the relevant Nutshell Deal or Company. Billing/shipping address, PO reference, and product line items are mapped to custom fields or a custom line-items relationship. Sales Orders do not have a native Nutshell equivalent; they are handled as custom objects to preserve the document record.

Vtiger Invoice records are migrated as custom Invoice records linked to the corresponding Nutshell Company or Deal. Invoice status, due date, and line items are mapped to custom fields. Payment status is preserved as a custom picklist field. As with Quotes and Sales Orders, Invoice PDFs are flagged for manual reattachment from Vtiger's document storage.

Help Desk Tickets are migrated to a custom Nutshell object with the same name. Ticket fields (status, priority, category, assigned agent) map to custom fields on the custom object. Customer and agent reply conversations are migrated as Note records linked to the Ticket custom object. This is a high-priority pair-specific gotcha: Nutshell does not include a native help desk or service desk module, so ongoing support use cases require either a dedicated help desk integration or a rebuild of ticketing workflows post-migration.

Vtiger Project records migrate as a custom Project object in Nutshell. Milestones and subtasks are migrated as related custom records linked to the Project. Task assignees and time tracking data are preserved as custom fields. Vtiger project dependencies are not structurally migratable to Nutshell since no native project management module exists; they are documented in the configuration inventory for the customer's admin to evaluate in a dedicated PM tool if project tracking continues to be a core requirement.

Vtiger Price Books contain named pricing lists with multiple product-to-price entries per book. These must be unrolled: each unique product entry becomes a Nutshell Product record with its price stored in the Standard Price Book. Price Book names are preserved as Product custom fields to identify which Vtiger pricing list the product belonged to. This is a field-by-field mapping step, not a direct object swap, and requires the customer's review to confirm pricing strategy post-migration.

Vtiger custom fields on any standard module (Contact, Organization, Deal, Ticket, Project) are extracted as field definitions and mapped to Nutshell custom fields of equivalent data type. Nutshell's text custom fields support a maximum of 225 characters; longer Vtiger text fields are flagged and truncated with a note in the reconciliation report. Multi-select picklists, currency fields, and date fields are mapped to their Nutshell equivalents.

Vtiger User records (name, email, role) are extracted for migration context, but owner assignments in Nutshell are resolved by email matching against the destination User table. Any Vtiger User without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Vtiger role and profile data is catalogued in the configuration inventory for admin review but does not map directly to Nutshell's permission model.