Migrate from XSale to Odoo CRM

XSale Rep records map to Odoo res.users by email match. We extract every distinct rep_id referenced on Visit, Order, and Route records and attempt email-based lookup against the destination Odoo User table. Any Rep without a matching User goes to a reconciliation queue for the customer's admin to provision before record import begins. Active versus inactive status is preserved by setting the corresponding Odoo User to active or inactive. If XSale stores rep attributes beyond email (name, phone, territory), these migrate as res.users fields or custom fields on res.users.

XSale Route records (territory groupings of stores and visit sequences) have no direct Odoo CRM equivalent. Routes are recreated as Odoo crm.team records, where each team represents a geographic territory or route grouping. The route sequence of stores is documented in a custom field (e.g., xsale_route_sequence__c) on the Sales Team for admin reference. This is primarily a configuration step; the customer's admin defines the Sales Team structure in Odoo settings and we validate the mapping against the XSale route list.

XSale stores and companies map to Odoo res.partner records. We perform a 1:N split: the XSale company or store header becomes an Odoo res.partner with type=contact and is_contact=False (the Account record). Individual store contacts, buyer names, and branch contacts become res.partner records with type=contact and is_company=False linked via parent_id to the Account. The XSale store address, phone, and custom fields map to the corresponding res.partner fields.

XSale Visit records are the highest-volume migration object. Each Visit maps to an Odoo mail.activity record with activity_type_id set to the visit-related activity type (created during configuration as 'Visit' or 'Field Visit'). The XSale visit status (completed, skipped, no-answer) migrates as a custom char field xsale_visit_status__c. The visit timestamp and duration migrate to Odoo's date_deadline and create_date. The related store (partner) and rep (user) are resolved via lookup before activity insertion. Visit notes migrate as Odoo mail.message records on the activity's res_id.

XSale pre-order records (orders captured before delivery confirmation) map to Odoo sale.order with state=quotation. The pre-order line items map to sale.order.line with product_id, product_uom_qty, and price_unit preserved. Pre-order metadata (order taken by, order timestamp, store reference) migrates to custom fields on sale.order. The customer's admin decides whether pre-orders should remain as quotations pending delivery confirmation or be confirmed immediately as sale.order with state=sale.

XSale confirmed orders map directly to Odoo sale.order with state=sale. Order status (delivered, partially delivered, pending) maps to Odoo picking state via the stock.picking record created by the sale order. The link between sale.order and stock.picking is created at migration time using Odoo's delivery workflow. Order totals, taxes, and discounts migrate as sale.order.line records. If XSale stores order approval or sign-off data, this migrates as custom fields on sale.order.

XSale product catalog records map to Odoo product.product. Product name, SKU, unit of measure, and price migrate to the corresponding Odoo fields. If XSale tracks product images or descriptions, these migrate to product.product's image fields and description fields. Product categories in XSale map to product.category records in Odoo before product migration so that categ_id references are satisfied at insert time.

XSale route-to-rep assignments (which reps are assigned to which routes on which days) have no direct Odoo equivalent. We extract all route assignment records, document the rep-route-day relationships in a CSV inventory, and deliver this to the customer's admin for rebuild using Odoo Sales Team membership and the calendar module if scheduling is required. This is a configuration handoff item, not a data migration item.

XSale custom fields added to the Order object require pre-creation in Odoo as ir.model.fields records before any sale.order data inserts. We enumerate every custom Order field during discovery, determine the appropriate Odoo field type (char, selection, float, many2one, etc.) for each, create the fields in the staging environment, and validate that migration transforms populate them correctly. Custom field pre-creation is the most common source of migration delay if discovered late.

Same as Order custom fields: XSale custom fields on the Visit object require ir.model.fields creation in Odoo before mail.activity records can be imported with those values. We surface every custom Visit field during discovery, classify the Odoo field type, and create them in staging before production migration. Visit custom fields often include outcome codes, visit ratings, and field-collected attributes that have no Odoo standard equivalent.

If XSale captures deal-level pipeline data (expected value, stage, expected close date, probability), these map to Odoo crm.lead fields (planned_revenue, stage_id, date_deadline, probability). XSale's pipeline stages map to Odoo crm.stage records within the relevant crm.team. The xsale_original_stage__c custom field preserves the source stage name for audit. Deals without an associated Contact are imported as crm.lead; deals with a Contact are converted to crm.lead and linked to the Contact partner.

XSale delivery confirmations map to Odoo stock.picking records linked to the corresponding sale.order. The picking state (done, cancelled, waiting) is preserved. If XSale captures delivery confirmation signatures or photos, these migrate as Odoo ir.attachment records linked to the stock.picking. The stock.picking records are created as a downstream step after sale.order migration using Odoo's delivery workflow chain.