Migrate from Vtiger Sales to Pipedrive

Vtiger Contacts map directly to Pipedrive People. We extract all standard Contact fields (name, email, phone, address) plus any custom Contact fields and map them to Pipedrive custom fields of matching type (text, numeric, date, picklist). Vtiger's Contact-to-Organization linkage via account_id preserves as the Pipedrive Organization link on People. Owner assignment migrates by email match against Pipedrive User records.

Vtiger Organizations (the Account/Company module) map 1:1 to Pipedrive Organizations. The organization name, industry, website, address, and any custom Organization fields migrate. Organization is created before any related Contact import so that the People-to-Organization link resolves at insert time without orphaned records.

Vtiger Leads map to Pipedrive Leads if the destination Pipedrive account has the Leads feature enabled (Professional and above). Lead status, lead source, and custom Lead fields migrate. If Pipedrive Leads are not enabled, Leads merge into People records with lead status preserved as a custom field.

Vtiger Deals (called Potentials in some editions) map to Pipedrive Deals. Deal stage from Vtiger maps to a Pipedrive Pipeline stage; the customer configures the Pipeline stages in Pipedrive before migration so we can assign the correct stage_id. Expected close date, amount, probability, and custom Deal fields migrate. Owner assignment resolves by email match.

Each Vtiger Sales Pipeline assignment becomes a Pipedrive Pipeline. We extract Vtiger pipeline names, stage names, and stage probabilities and reproduce them as Pipedrive Pipelines with matching stage order and probability percentages. Pipedrive's drag-and-drop stage editor is configured before migration so the stage IDs are stable for Deal import.

Vtiger Quotes contain line items, product references, pricing, and tax information that do not map to a single Pipedrive field. We split each Quote into a Pipedrive Deal record (carrying the quote header data: total amount, valid until, terms) and Product entries attached to that Deal. Vtiger Quote-to-Sales Order linkage is preserved as Deal notes or a custom deal field since Pipedrive has no native Quote-to-SalesOrder chain.

Vtiger Sales Orders generated from accepted Quotes map to closed-won Pipedrive Deals with a custom field indicating the original Sales Order number. Line items migrate as Deal Products. Billing and shipping address from the Sales Order copy into Deal address fields or custom fields.

Vtiger Invoices migrate as closed-won Pipedrive Deals with a custom field invoice_status__c set to 'invoiced'. The invoice number and payment due date migrate as custom fields. Pipedrive has no native Invoice object; if the customer requires invoice history, we flag this as a reporting-only import and recommend a dedicated billing tool post-migration.

Vtiger Price Books are pricing list objects storing product-to-price mappings. We unroll each Price Book entry into a Pipedrive Product record (name, SKU, unit) and create a Standard Price Book entry with the price value. If multiple Price Books exist, we create a custom field price_book__c on Product to identify which Vtiger Price Book the entry originated from.

Pipedrive has no native Help Desk or Ticket object. Vtiger Help Desk Tickets migrate as Pipedrive Activity Tasks with a custom field ticket_id__c carrying the original Vtiger ticket number, ticket_status__c matching the Vtiger status, and ticket_priority__c matching priority. Threaded conversation history from Tickets migrates as a series of Note records attached to the Task. This is a manual-overhaul approach; customers requiring full ticket management migrate to a separate helpdesk tool.

Pipedrive has no native Project or milestone object. Vtiger Projects migrate as Pipedrive Activities (Tasks with custom fields project_name__c and milestone__c) linked to the related Deal or Organization. If no related Deal exists, Tasks link to the Organization. This preserves task-level history but does not reproduce Gantt or project hierarchy. Project time tracking migrates as custom numeric fields on the Activity.

Vtiger User records (name, email, role, profile) are extracted for migration scoping and owner reconciliation. We match Vtiger Users to Pipedrive Users by email. Any Vtiger User without a matching Pipedrive User is held in the reconciliation queue for the customer to provision before record import resumes. Inactive Vtiger users are migrated as inactive Pipedrive users to preserve assignment history.

Vtiger allows custom fields on any standard module. We extract custom field definitions (name, data type, picklist values) and map them to Pipedrive custom fields by type: Vtiger picklists become Pipedrive dropdowns, Vtiger text fields become Pipedrive text fields, Vtiger date fields become Pipedrive date fields. Pipedrive requires custom fields to be pre-created in the destination account before import; we generate the Pipedrive field creation payload as part of the migration prep phase.

Vtiger file attachments on Contacts, Organizations, Deals, and Tickets are stored as references with URLs or as binary blobs depending on hosting configuration. We extract attachment metadata (filename, content type, associated record) and migrate as Pipedrive Files attached to the equivalent People, Organization, or Deal record. Actual file transfer depends on Vtiger hosting and access permissions; if the Vtiger instance is self-hosted, we coordinate with the customer to ensure file access is available during migration.