Migrate from webCRM to Odoo CRM

webCRM Organisations map to Odoo res.partner records with partner_type = contact and company_type = company. We extract Organisation name, address, phone, website, and any Organisation-level custom fields and create them as Company Partner records in Odoo. The Organisation ID is preserved in a custom Char field webcrm_id for reference. Odoo's Contacts module must be installed to enable the res.partner model for CRM use; we confirm this during scoping.

webCRM Contacts map to Odoo res.partner records with partner_type = contact and company_type = person. We resolve the Organisation-to-Company lookup at import time by matching Organisation name or ID to the Odoo Company Partner created in the prior phase. Contact-level custom fields map to custom Char, Integer, or Selection fields on res.partner. Email, phone, and job title migrate directly.

webCRM Deals map to Odoo crm.lead records of type opportunity. The Deal name becomes the Opportunity name; deal value maps to Odoo's Expected Revenue (planned_revenue); pipeline stage names map to Odoo CRM Stage values in the configured Sales Pipeline. We flag any Deals with status that has no Odoo stage equivalent and create a custom stage or use Closed Lost during staging. Deal-to-Organisation and Deal-to-Contact associations resolve via the Partner and partner_id lookups after those records are imported.

Each distinct webCRM pipeline stage value becomes an Odoo CRM Stage record in the sales team's pipeline. We create these stages during the Odoo configuration phase, mapping the original stage name and probability percentage. If webCRM uses multiple Deal pipelines, we create separate Odoo Sales Teams and assign the appropriate stage sets to each.

webCRM Deliveries are exported in webCRM Delivery XML format via Zynk. The nested XML with line-item detail is flattened into two records: sale.order (header: customer, order date, delivery address, delivery reference) and sale.order.line (product, quantity, unit price, tax). We parse the XML, extract parent Delivery attributes, and emit child Order Line rows, then load via Odoo's CSV import or XML-RPC API. webCRM Delivery status (dispatched, confirmed) maps to Odoo sale.order state.

webCRM Product Database records (name, description, SKU, list price, cost price) map to Odoo product.product records. We create each webCRM product as an Odoo Product with type = product or service based on the product database flags. Standard price from webCRM becomes Odoo's list_price; cost from webCRM becomes standard_price. Product associations with Deals or Deliveries resolve after both objects exist in Odoo.

webCRM Tasks linked to Organisations or Contacts migrate as Odoo CRM activities attached to the relevant crm.lead (Opportunity) or res.partner record. Task subject becomes the activity title; task status (pending, completed) maps to activity state; due date migrates as deadline. Tasks without a parent Deal or Contact are attached to the nearest related Organisation or Contact record. Activity timeline ordering is preserved by setting create_date to the original webCRM task timestamp.

webCRM custom fields on Organisations, Contacts, Deals, Deliveries, Products, and Tasks require manual creation in Odoo before data import. We extract the full custom field schema during scoping (field name, data type, options for picklists), create matching custom fields in Odoo via Settings > Technical > Database Structure > Fields, then import values as part of each object migration phase. Custom field types are matched to the closest Odoo field type: text fields to Char, numeric fields to Float or Integer, date fields to Date.

webCRM Automation Module rules (time-based reminders, inactivity triggers, deadline actions) are stored internally with no export endpoint and cannot be migrated. We inventory every active webCRM automation during scoping, documenting its trigger, conditions, actions, and affected record types. This inventory is handed off as a written specification for the customer's Odoo admin or an Odoo partner to rebuild using Odoo Studio automation, server actions, or scheduled actions. Budget 1-2 hours per automation rule for rebuild.

webCRM Owners (sales reps assigned to Organisations, Contacts, Deals) map to Odoo res.users records. We extract distinct owner references from all migrating objects, match by email address against the Odoo destination User list, and flag any owners without a matching Odoo User for the customer's admin to provision before record import resumes. Owner assignment on Deals migrates as user_id on the crm.lead record.

webCRM Order records linked to Deliveries are captured through the Delivery XML export. If webCRM maintains separate Order records distinct from Deliveries, we export those via the Overviews utility as CSV and map order number, order date, and customer reference to Odoo sale.order. The Delivery XML and Order CSV are cross-referenced to avoid duplicating records if both export paths produce the same data.

webCRM quotes or proposals stored as distinct records from Orders export as Odoo sale.order with state = draft or sent. Quote line items map to sale.order.line. If webCRM quotes are stored within the Deal object (attached as a document reference rather than a structured record), we note the file location and recommend it be re-uploaded manually to the migrated Odoo Opportunity as an attachment post-migration.