Migrate from Vtiger Sales to Odoo CRM

Vtiger Contacts map to Odoo Partner records with is_company=False. We preserve firstname, lastname, email, phone, mobile, street, city, state, country, and zip. The Vtiger account_id (linking to Organization) maps to an Odoo Partner lookup (parent_id) where the parent Partner is the company-type record. Owner assignment (vtiger_assigned_user_id) maps to Odoo user_id on the Partner record. Any custom Contact fields migrate to Odoo custom fields on the res.partner model.

Vtiger Organizations (Accounts) map to Odoo Partner records with is_company=True. The Organization name becomes the Partner name. Industry, website, annual_revenue, and employee_count map to Odoo custom fields on res.partner. We pre-create company-type Partners before Contact migration so that the parent_id lookup is satisfied at insert time. Organization-to-Contact linkage is preserved through the parent_id field.

Vtiger Leads map directly to Odoo CRM Lead. Lead status, lead source, rating, and any custom fields transfer. Odoo Lead uses a different pipeline model from Vtiger Deals; Leads in Odoo are pre-conversion prospects that flow through a separate kanban before becoming Opportunities. We preserve the Vtiger lead score in a custom field on the Odoo Lead record.

Vtiger Deals (Potentials) map to Odoo CRM Opportunity. The dealname becomes the Opportunity name, amount maps to planned_revenue, and probability maps to Odoo probability (with Vtiger probability as a custom field since Vtiger stores a separate probability field). The pipeline assignment maps to an Odoo Sales Team and Stage. Closed-Lost and Closed-Won dates transfer as stage-specific dates.

Vtiger pipeline stages map to Odoo CRM stage records within a Sales Team. Each Vtiger stage gets a corresponding Odoo stage with the same sequence order. Stage colors and win/loss flags transfer. We configure the Odoo stages before Opportunity import so that the stage_id reference is satisfied at insert time.

Vtiger Quotes map to Odoo Sale Order records in Quotation state. Line items migrate as sale.order.line records with product, quantity, unit_price, discount, and tax. The linked Contact and Organization map to the Odoo Partner and its parent company. Quote expiration dates map to validity_date on the Odoo quotation.

Vtiger Sales Orders map to Odoo Sale Order records in confirmed (Sales Order) state. Billing address and shipping address from Vtiger map to Odoo's partner_invoice_id and partner_shipping_id. PO reference maps to client_order_ref. Line items, quantities, prices, and taxes migrate directly to sale.order.line records.

Vtiger Invoices map to Odoo Account moves of type out_invoice. Invoice line items migrate as move.line records. Payment status from Vtiger maps to Odoo payment_state. Due dates and invoice dates transfer to invoice_date and invoice_date_due. Vtiger invoice_number becomes Odoo name (with a configured sequence prefix).

Vtiger Help Desk Tickets map to Odoo Helpdesk Ticket records. Ticket status (Open, Waiting, Closed) maps to Odoo stage_id. Priority maps to Odoo priority. The assigned agent maps to Odoo user_id. Ticket conversations (customer and agent replies) migrate as Odoo Ticket chitchat or mail.message records linked to the Ticket. SLA policies from Vtiger Enterprise do not transfer; these require configuration in Odoo Helpdesk settings.

Vtiger Projects map to Odoo Project records. Milestones migrate as Odoo project milestones. Tasks and subtasks map to Odoo task records with parent_id for subtask hierarchy. Assignees map via user_ids on the task. Time tracking data from Vtiger maps to Odoo's timesheet entries if the Timesheet app is installed; otherwise it becomes a custom field on the task record.

Vtiger Price Books are pricing list objects with product-to-price mappings that do not have a direct Odoo equivalent. Each Price Book entry is unrolled: we extract the product reference and the price value and write them as individual product.pricelist.item records attached to an Odoo product.pricelist created for that Price Book. This is a denormalization step rather than a direct object swap and requires product-level mapping for each entry.

Vtiger custom fields on any standard module migrate to Odoo custom fields on the equivalent model. We map by field label and data type (text to char, number to float, date to date, picklist to selection). Custom field positioning and grouping within the form layout do not transfer; Odoo Studio is used post-migration to reorder fields on the form view.

Vtiger Users map to Odoo res.users records. We match by email address. Active/inactive status transfers. Role and profile assignments do not have a direct Odoo equivalent; Odoo uses access rights groups (id > 0 for regular users, 0 for portal-only). We flag any Vtiger role that requires Odoo group assignment for the customer's admin to configure post-migration.

Vtiger file attachments on Contacts, Organizations, Deals, and Tickets store as attachment references with file URLs. We extract attachment metadata (filename, MIME type, size, created date) and link them to the corresponding Odoo record via ir.attachment records. Actual file transfer depends on whether Vtiger is self-hosted or cloud; cloud attachments require download authentication handling. If the Vtiger instance is cloud-hosted and attachments are not publicly accessible, we flag this for manual file transfer or a mediated download step.

Vtiger Tags applied across modules map to Odoo tags on the equivalent model. Odoo CRM uses crm.tag on Lead and Opportunity; other models use mail.message.category or a dedicated tag model depending on the app. We extract tag assignments per record and write them to the Odoo tag field. Tag color does not transfer; Odoo uses a fixed color palette for tags.