Migrate from Lead Commerce to Odoo ERP

Lead Commerce Orders map to Odoo Sale Orders. We extract orders with their lifecycle stage (pending, processing, shipped, completed) and split the migration into two batches: historical fulfilled orders import first, then open orders that require the customer to either pause new order creation or manually enter them post-migration. Order total, line items, and customer reference migrate directly. Odoo's sale.order and sale.order.line records are created in dependency order so that the parent order exists before lines are attached.

Lead Commerce Customer records map to Odoo Contact (res.partner with customer_rank set). Contact details, addresses, and phone numbers migrate as typed fields. We deduplicate by email during import and preserve the customer-to-order linkage so historical order context is not lost. If Lead Commerce stores companies and contacts separately, companies map to res.partner (company_type = company) and contacts map to res.partner (company_type = person) with the parent_id relationship set.

Lead Commerce inventory items with SKU, stock level, and location assignment map to Odoo Product Template (product.product for singular variants). Odoo requires a product type decision (storable, consumable, service) at import time. If Lead Commerce items have attribute-based variants (size, color), we create the Product Template first and then generate Product Variants using Odoo's product.attribute and product.attribute.value framework. Stock quantities per warehouse migrate to Odoo quant records linked to the correct stock.location.

Lead Commerce Warehouse records map to Odoo Warehouse (stock.warehouse) and child stock.location records. If Lead Commerce has sub-location structure (bins, shelves) that is not explicitly defined, we infer the warehouse layout from inventory assignment data and create a corresponding Odoo location hierarchy under the warehouse's view location. Multi-location inventory counts require per-warehouse record mapping; we flag any items with zero or negative quantities that may indicate data quality issues in the source.

Lead Commerce Purchase Order records map to Odoo Purchase Orders (purchase.order). Open POs and received POs need separate treatment: received lines should map to landed inventory (product receipts) while open lines represent commitments that may need to be confirmed in Odoo post-import. Odoo's po_state (draft, sent, purchase order, done, cancelled) is mapped from Lead Commerce's PO lifecycle stage. We import purchase.order and purchase.order.line in dependency order, resolving the vendor partner reference before lines are attached.

Lead Commerce User accounts and role assignments export as a flat list. We map role names to Odoo's access control groups (stock.group_stock_user, purchase.group_purchase_user, sales.team) based on the Lead Commerce role's functional scope. Active/inactive status is preserved. Any Lead Commerce user without a corresponding Odoo account goes to a reconciliation queue for the customer's admin to provision before the user-related records are imported.

Lead Commerce Custom Apps carry custom-built application code with no standard export mechanism. We identify any data stored in Lead Commerce's database by custom apps and flag it separately in the pre-migration report. The application logic itself cannot be transferred and must be rebuilt or re-platformed at the destination. We recommend the customer evaluate whether custom app functionality maps to an existing Odoo community module or requires custom Odoo module development.

Lead Commerce saved reports and historical analytics snapshots have no export path through CSV, API, or database query. We include a reporting export step in the pre-migration checklist: the customer pulls period-end reports as PDFs or screenshots before migration cutoff. Historical dashboard data cannot be replicated automatically at the destination. Odoo's native reporting engine is available post-migration for rebuilding reports from the migrated data.

If Lead Commerce stores product category hierarchies, they map to Odoo product.category records. Category names and parent assignments (if a subcategory structure exists) are imported before product templates so that the categ_id reference is satisfied at product import time. Categories without a Lead Commerce equivalent are created as flat top-level categories in Odoo.

Lead Commerce Order line items (product, quantity, unit price, discount) map to Odoo sale.order.line. The product reference is resolved by SKU match against the imported product catalog. If a line references a discontinued or deleted Lead Commerce product, we flag it in the pre-import reconciliation report and the customer decides whether to map to a new product or leave the line unmapped. Discounts migrate as price_unit with discount field set per Odoo's line model.