Migrate your Vtiger Sales data

Standard Contact record with name, email, phone, address, and lifecycle fields. We extract all standard fields plus any custom Contact fields. Owner assignment is preserved as a user reference.

Organization (Account) module stores company-level data linked to Contacts. We map Organization fields 1:1 and preserve the Contact-to-Organization linkage through the account_id field.

Separate Lead module for pre-contact records. We extract Lead fields and can merge them into Contacts on the destination side, preserving lead source and status as custom properties.

Deals (Potentials) track pipeline opportunities linked to Organizations or Contacts. We map Deal fields including stage, amount, probability, expected close date, and sales pipeline assignment.

Quote records linked to Deals, Contacts, and Organizations. We extract line items, pricing, and tax information. Quote-to-Sales Order linkage is preserved through reference fields.

Sales Order documents generated from accepted Quotes. We map the full document including products, quantities, prices, billing/shipping addresses, and PO reference.

Invoice records linked to Sales Orders. We extract invoice line items, payment status, due dates, and related Contact/Organization references.

Price Books store product pricing lists. Migration requires mapping price book entries to destination product or item records, as the pricing model differs across CRMs.

Ticket module for customer support cases. We extract ticket fields, status, priority, assigned agent, and conversation history including customer and agent replies.

Project module with milestones, tasks, and subtasks. We map project hierarchy, task dependencies, assignees, and time tracking data. Kanban and list views are configuration-level and not stored as data.

Vtiger allows custom fields on any standard module. We extract custom field definitions and their values, then map them to destination custom fields by name and data type.

User records include name, email, role, and profile. We extract user data for migration but remap owner assignments to destination users based on email matching.

Workflow automations are configuration data stored as rule definitions. We catalogue workflow triggers, conditions, and actions and replicate equivalent logic in the destination CRM where supported.

File attachments on Contacts, Organizations, Deals, and Tickets are stored as references. We extract attachment metadata and URLs, but actual file transfer depends on Vtiger's file hosting and access controls.

Tags are applied across modules to label records. We extract tag assignments per record and map them to equivalent tagging or labelling features in the destination CRM.