Migrate from Vtiger Sales to Twenty CRM

Vtiger Contact records map directly to Twenty Contact. We extract standard fields (name, email, phone, address, job title) plus any custom Contact fields. Owner assignment (assigned_user_id in Vtiger) maps to the Twenty User via email resolution. Vtiger's lifecycle fields (like lead_source, secondary email) map to Twenty custom fields of equivalent type if no native equivalent exists. Contact-to-Organization linkage via account_id becomes Contact-to-Company linkage via the company_id field in Twenty.

Vtiger Organization (Account) records map 1:1 to Twenty Company. The organization name becomes the Company name, and domain or website fields map to the Company domain field for deduplication. Organization address, industry, annual revenue, and number of employees migrate to equivalent Twenty Company fields. We resolve the Organization before importing any linked Contacts so that company_id lookups are satisfied at insert time.

Vtiger Lead records do not map to a single Twenty object. We evaluate each Lead's status field: Leads with closed-won or converted status map to Twenty Contact (the prospect became a customer); Leads with open statuses map to Twenty Contact with a person_status custom field preserving the original Vtiger lead status for segmentation. We preserve lead_source, rating, and any lead scoring custom fields as Twenty custom fields on the resulting Contact record.

Vtiger Deals (Potentials) map directly to Twenty Opportunity. We translate dealstage to Twenty opportunity stage, amount transfers as amount, probability transfers as probability (or we calculate from stage if the source deal has no probability set), and expected_close_date becomes close_date. Pipeline assignment from Vtiger maps to a Twenty pipeline identifier that we configure before migration. Sales stage values migrate as custom picklist values if Twenty does not have equivalent native stages.

Vtiger Quotes are document objects linked to Deals with line items, pricing, and tax information. Twenty CRM does not have a native quote object in the core self-hosted version. We map Quote headers and key fields (quote number, total, validity date) into Opportunity custom fields, and document the line item structure as a structured notes block for manual recreation or third-party quoting tool integration. Quote-to-Sales Order linkage is not preserved as a native relationship in Twenty.

Sales Order records in Vtiger represent post-accepted-Quote fulfillment documents with product quantities, prices, and billing/shipping addresses. Twenty does not have a native Sales Order object. We extract Sales Order data as structured records and store the key fulfillment data as Opportunity-level custom fields and notes. The customer's admin recreates Sales Order templates in Twenty or connects a dedicated invoicing tool post-migration.

Vtiger Invoice records track payment status, due dates, and line items after Sales Orders. Twenty CRM does not include native invoicing in the core product. We preserve Invoice data (invoice number, total, balance due, payment status) as Opportunity custom fields and structured notes. Payment tracking requires a separate accounting or invoicing tool integration post-migration.

Vtiger Price Books store product-to-price mappings as separate list objects with multiple price entries per product (volume pricing, tiered pricing). Twenty uses inline product pricing on Opportunity line items without a separate Price Book concept. We unroll each Price Book entry into individual Product records with pricing stored as custom fields, or we create a dedicated Product record per Price Book with a structured pricing block. This is a field-level mapping step rather than a direct object swap and requires the customer to choose a pricing strategy for the destination.

Vtiger Help Desk Tickets map to Twenty Task records. We extract ticket status, priority, category, assigned agent, and the full conversation history (customer and agent replies). Ticket status maps to Twenty Task status, priority maps to Task priority, and the conversation thread becomes a series of Note records or comment blocks on the Task. Vtiger ticket SLA policies do not have a Twenty equivalent and are flagged for manual configuration or third-party SLA tool evaluation.

Vtiger Projects with milestones, tasks, subtasks, assignees, and time tracking data map to Twenty Task records with hierarchical structure. Milestone tasks become parent Tasks in Twenty; subtasks become child Tasks with the same parent_id linkage. Assignee resolution uses the same User email-matching logic applied to the Contact and Deal imports. Time tracking data from Vtiger migrates as custom fields on the Task record.

Vtiger allows custom fields on any standard module. We extract the full custom field schema (field name, API name, data type, required flag, default value) and recreate equivalent custom fields in Twenty before any data import. Data type mapping handles Vtiger picklists to Twenty select fields, Vtiger date fields to Twenty date fields, and Vtiger multi-select picklists to Twenty multi-select fields. Custom field values migrate as values only after the destination schema is confirmed.

Vtiger User records (name, email, role, profile) are extracted for migration scoping. Owner assignments on Contacts, Organizations, Deals, Tickets, and Projects are resolved by email match against the Twenty User table. Users without a matching Twenty account go to a reconciliation queue for the customer's admin to provision before record import resumes. Role and profile information is preserved as structured notes for admin to reconfigure in Twenty's access control layer.