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

Vtiger Accounts (and Organizations in some exports) map directly to Twenty Companies. The account name maps to company name, industry maps to industry, phone maps to phone, website maps to website, and billing address maps to address fields. We use the Vtiger account name as the dedupe key during import. Companies must be created before any People import so that the company link is satisfied at the moment of People insert.

Vtiger Contacts map directly to Twenty People records. First name, last name, email, phone, job title, and address fields migrate as typed fields. The Contact-to-Account relationship maps to the People-to-Company link in Twenty. Custom fields on Contact (picklist, checkbox, currency, date) migrate as custom fields on People after we create the destination schema in Twenty's Data Model settings before import.

Vtiger Leads require a migration strategy decision: if the customer wants to preserve the lead pipeline as pre-opportunity records, Leads migrate to Twenty People with a lead_status custom field set from Vtiger's lead_status and lead_source properties. If the customer prefers to convert all Leads at migration time, we create both a People record and an Opportunity record linked to the Company and set the Opportunity stage to a designated qualification stage. We confirm the strategy during discovery.

Vtiger Potentials map to Twenty Opportunities. Potential name maps to opportunity name, amount maps to amount, close date maps to close date, sales stage maps to stage, pipeline maps to a custom pipeline field or tag in Twenty, and probability maps to probability. The Contact Name (potential related contact) maps to the opportunity's person link in Twenty. We validate that the Account exists before importing the Opportunity to satisfy the company link.

Vtiger Help Desk Tickets map to Twenty Tasks (for activity tracking) with the ticket number, status, priority, and description preserved in custom fields. If the customer wants a dedicated case management experience, we create a Cases custom object in Twenty before migration and map tickets to Case records with status and priority mapped. The original assigned agent maps to the Twenty workspace member by email match. We confirm the case management preference during discovery.

Vtiger Products map to Twenty Items with product name, code, unit price, and vendor link preserved. The product description maps to item description, and stock information (if present) maps to a custom stock_quantity field. Items must be imported before Quotes or Sales Orders because line items reference the item. We validate that all products have a unique code for deduping during import.

Quotes migrate as Opportunities with the Quote content preserved in the Opportunity description or a custom quote_body field, and the Quote number preserved as a custom field. Line items from the Quote migrate as Opportunity items linked to the Items imported earlier. If Vtiger's Inventory module is disabled, Quote records will not exist in the export — we check the module configuration before extraction and advise the customer to enable Inventory if Quotes are in scope. Quote PDFs migrate as attachments linked to the Opportunity record.

Vtiger Sales Orders map to a custom Order custom object in Twenty (created before migration) or to Opportunities with order metadata. Sales Order line items require Items to exist first, so we sequence Products before Sales Orders. The vendor link on a Purchase Order maps to a vendor custom field on the Order; vendor records must be imported before Purchase Orders to maintain referential integrity.

Vtiger Projects migrate to a Project custom object in Twenty. Project name, description, start date, end date, status, and assigned user migrate as typed fields. Task dependencies (Finish-to-Start) migrate as task link records or are preserved in a custom dependency_notes field if the Twenty custom object schema does not natively support task dependencies. Milestones map to parent Task records with a milestone flag custom field.

Standalone Vtiger Tasks and Project Tasks migrate to Twenty Tasks with assignee (mapped by email to Twenty workspace member), due date, status, subject, and description preserved. Subtask hierarchy is preserved where the Twenty task schema supports it; otherwise we flatten to top-level tasks and note the original parent in a custom subtask_of field. Task status values are mapped to the Twenty task status options the customer configures during workspace setup.

Vtiger custom fields are fully supported but require field-type mapping. Picklist values in Vtiger must align with Twenty's select options for the equivalent field; checkbox maps to boolean; currency maps to number; date maps to date. We generate a field-type comparison table during discovery and create all custom fields in Twenty's Data Model settings before importing any records. Fields must exist in Twenty before CSV import creates records referencing them.

Vtiger exports attachments individually per record with no bulk download option. For migrations with fewer than 500 attachments, we extract them alongside their parent record, stage them in object storage, and re-associate them with the correct parent record post-import. For migrations exceeding 500 attachments, we stage files in object storage and run a separate association job after primary data import completes. The customer must provision adequate destination storage before migration begins.