Migrate from eCommerce Pro to Odoo ERP

eCommerce Pro products with variants map to Odoo product.template (the shared product record) and one product.product per variant combination. Attribute names (colour, size) and values map to Odoo attribute lines on the template. Pricing at the variant level (price per SKU) maps to Odoo seller_ids and pricelist items with the product.product as the scope. We resolve the split during the audit phase because variant-heavy catalogs (100+ attributes, thousands of combinations) require the import to run in variant-first order to avoid template reference failures.

eCommerce Pro customer records map to Odoo res.partner. We use email as the dedupe key during import. Customer addresses migrate as partner addresses (street, city, state, zip, country) with address type flags (type=contact, invoice, delivery). The acceptsmarketing flag from eCommerce Pro maps to a custom boolean field opt_in_email__c on partner for reactivation post-migration. Customers with no email address are flagged for manual review because Odoo requires email for B2B and some eCommerce flows.

eCommerce Pro orders map to Odoo sale.order with order lines, payment state, and shipment tracking preserved. Order status (pending, processing, shipped, delivered, cancelled) maps to Odoo picking state (waiting, confirmed, assigned, done, cancelled) and invoice state (draft, posted, cancelled). Historical orders import with a backdate matching the original order timestamp so reporting periods reflect the correct fiscal month.

eCommerce Pro fulfilment records map to Odoo stock.picking linked to the corresponding sale.order. Tracking numbers and carrier names transfer to the picking's carrier_id and move_lines' result_package_id. Partial shipments create separate picking records under the same sale.order. Completed fulfilment status maps to done on the picking; cancelled fulfilment maps to cancelled.

eCommerce Pro inventory levels per SKU map to Odoo stock.quant records. Single-warehouse setups map directly to one stock.location (stock_location_stock). Multi-warehouse setups require us to either consolidate into one location or split the eCommerce inventory pool into separate Odoo warehouse locations (WH/Main, WH/Secondary). We validate that stock.quant quantities per product and location satisfy sale.order move lines after import.

eCommerce Pro discount codes (percentage, fixed amount, buy-X-get-Y) map to Odoo coupon.program records if the Odoo Loyalty app is installed. Percentage discounts that apply at checkout without a code map to product.pricelist.item rules scoped to the customer or product category. We flag complex stacking rules (discount-on-discount, time-gated tiers) as requiring Odoo Studio rebuild because Odoo coupon logic handles these differently from eCommerce Pro.

eCommerce Pro payment transactions map to Odoo account.payment linked to the corresponding sale.order invoice. Payment method (credit card, PayPal, bank transfer) maps to Odoo's payment journal and method configuration. Captured, pending, refunded, and failed states map to account.payment state values. We do not re-process payments; we record the historical transaction as a reconciled payment against the customer invoice.

eCommerce Pro product images migrate as ir.attachment records linked to product.product via the product.image_ids relation. We validate image URLs and optionally re-host assets to Odoo's filestore during import. Variant-level images attach to the specific product.product; template-level images attach to product.template.

eCommerce Pro product categories map to Odoo product.category hierarchy. The parent_id chain (if multi-level) preserves in Odoo. We run a topological sort to import parent categories before children to avoid foreign key constraint violations.

eCommerce Pro tax codes map to Odoo account.tax records configured manually in the Odoo Accounting app before migration. We preserve the source tax code name and rate in a custom field source_tax_code__c on account.tax so that the customer's accountant can map to the correct tax jurisdictions post-import. This is a manual step because tax configuration depends on the customer's nexus, jurisdiction, and filing regime.

eCommerce Pro B2B pricing lists, volume tiers, and company-specific catalogs map to Odoo product.pricelist records with pricelist.item rules scoped by product, category, or partner. Company-specific pricing requires the Odoo Contacts app with partner properties enabled so that the correct pricelist applies automatically at sale order creation. We flag any pricing logic that uses formula-based calculations (e.g., cost-plus markup) as requiring manual configuration in Odoo pricelist rules.