Migrate from Kentro ERP & 3PL to Odoo ERP

Kentro Products with variants, SKU-level tracking, and pricing tiers map to Odoo Product Templates with the product.type field set to consumable, stockable, or service based on fulfillment model. Variant attributes (size, color, dimension) map to Odoo Attribute lines on the template. We preserve hs_sku as product.default_code and validate uniqueness before insert to avoid duplicate SKUs across the catalog.

Kentro product variants map to Odoo product.product records linked to their parent Product Template. Each variant's specific pricing, barcode, and weight transfer to Odoo fields lst_price, barcode, and weight. If Kentro exposes variant-level inventory by location, we populate Stock Quant records per warehouse at migration time.

Kentro real-time inventory positions at bin level map to Odoo Stock Quant records, one per product, lot, package, and warehouse location. FIFO/FEFO tracking logic from Kentro transfers as lot/serial numbers on the Odoo Stock Quant, enabling the same valuation method in Odoo's stock layer. We extract current stock snapshots plus any available receiving and transfer logs to reconstruct the movement chain where Kentro's export exposes historical records.

Kentro Orders through their full lifecycle map to Odoo Sale Orders. The Kentro order status (pending, confirmed, shipped, delivered, returned) maps to Odoo picking behavior and order state. Channel attribution (Shopify, Amazon, marketplace) preserves as the sale_order.origin field and a custom channel_id field for reporting segmentation. Historical orders and open orders migrate together; we flag open orders for customer acknowledgment before cutover.

Kentro B2C customers map to Odoo Contact records with address associations and account-level pricing terms. Email, phone, street, city, state, zip, and country fields transfer directly. We set the customer_rank to distinguish primary customers from shipping addresses, and preserve any loyalty or pricing tier data in custom fields.

Kentro B2B company accounts map to Odoo Partners in company mode with child Contact records for individual contacts at that account. Account-level pricing terms and credit limits transfer to partner property_payment_term and credit_limit fields. The company address becomes the partner's street address with child contacts carrying individual roles and contact details.

Supplier-facing purchase orders in Kentro map to Odoo Purchase Orders with vendor, order lines, and receiving records. Custom approval workflows on Kentro POs are flagged as manual handoff items; standard PO fields (partner, date_order, order_line with product and quantity) migrate 1:1. Any pending receiving records map to Odoo incoming Stock Moves at the time of migration.

Kentro Supplier records with contact details, lead times, and default terms map to Odoo Partners with the supplier rank set and a corresponding Supplier Information record on the relevant Product Template for default vendor pricing and lead times.

Kentro multi-client 3PL setups use separate account structures per client. We isolate each client's inventory, orders, customers, and billing records and map them to their own Odoo company partition or website depending on the destination Odoo configuration. Each partition maintains separate stock locations, partner records, and sales teams. Billing records migrate as Odoo Account Move (invoice) entries linked to the client partner. This isolation step is the highest-risk item in the migration and is validated in a staging environment before production cutover.

Inter-warehouse transfer orders in Kentro map to Odoo Internal Transfers (stock.picking with picking_type = internal). Transfer status at migration time is evaluated: completed transfers become Odoo done moves; in-transit transfers are flagged as pending with source and destination location preserved so that Odoo's warehouse management continues the transfer in the destination system.

Fulfillment events and carrier tracking data from Kentro map to Odoo Delivery Orders with the carrier tracking number stored in picking.carrier_tracking_ref. Shipping method names transfer as a custom field or map to Odoo's existing delivery carrier configuration if the same carrier is active in Odoo. Carrier-specific metadata (signature, photo proof, delivery exception notes) is preserved in custom fields where Kentro exposes it.

Kentro EDI transaction sets (810 invoices, 850 purchase orders, 856 ASN, 997 functional acknowledgments) are preserved as Ir Attachment records linked to the corresponding Sale Order or Purchase Order. EDI mapping rules specific to each retailer are stored as custom EDI configuration records in Odoo for regeneration using an Odoo EDI module or partner solution. This is not a 1:1 field migration; document snapshots are the preservation mechanism.

Kentro marketplace connections and online store configurations map to Odoo multi-channel integration settings (Shopify connector, WooCommerce connector, Amazon modules) or custom integration records per channel. The channel-to-order linkage is preserved via the sale_order.origin field so that historical orders retain their originating source for reporting.

Kentro IQ report definitions and underlying datasets export where accessible via API. We deliver the report structure and data lineage as a written handoff document. Odoo reporting is rebuilt in Odoo Studio or via custom SQL views; we provide the data source mapping so that Odoo administrators can reconstruct the reports without reverse-engineering the Kentro logic.