Migrate from Aptean Distribution ERP to Odoo ERP

Aptean Customer records map to Odoo res.partner with partner_type set to 'contact' for billing and 'delivery' for shipping addresses. Customer hierarchical pricing tiers and customer groups from Aptean map to Odoo's pricelist and product.category access rights. We preserve the customer reference number as the partner's ref field and use the Aptean customer ID as an external identifier for reconciliation. Multi-currency customer pricing assignments require a dedicated pricelist per currency, which we configure before migration.

Aptean Vendor records map to Odoo res.partner with partner_type set to 'supplier'. The multi-currency vendor cost structure from Aptean—agency fees, freight, duties by harmonization code, and insurance components—migrates to Odoo's vendor pricelist (product.supplierinfo) entries per vendor and per currency. Vendor lead times map to Odoo's seller_delay on the product form. We validate that every Aptean vendor has at least one active purchase app contact before migration proceeds.

Aptean Item records map to Odoo product.template with product.product variants generated for each SKU size or color combination. Lot/serial tracking configuration from Aptean maps to Odoo's tracking field (by lot, by serial, or none) on the product form. Warehouse-specific stocking locations from Aptean map to Odoo's routes and warehouse-specific putaway rules. Cost layers (FIFO layers in Aptean) map to Odoo's real-time average cost or periodic standard cost depending on the customer's chosen valuation method; we discuss this decision during scoping.

Aptean multi-warehouse configurations map to Odoo stock.warehouse records with corresponding location hierarchies (view locations per warehouse, child locations per zone or bin). Directed putaway rules, speed-bin definitions, and wave-picking criteria from Aptean map to Odoo's putaway rules and removal strategies (FEFO by lot expiry, or FIFO by receipt date). We validate that all Aptean warehouse IDs are unique before creating Odoo warehouse records to avoid location conflicts.

Aptean Sales Order lifecycle records map to Odoo sale.order with order state (draft, confirmed, done, cancelled) preserved. Backorder flags and promised delivery dates from Aptean migrate to Odoo's commitment_date and procurements generated from the order. Order line pricing comes from the Aptean customer pricing tier; we resolve the Odoo pricelist before inserting order lines so that unit prices are correctly assigned. Open orders migrate in confirmed state; invoiced and closed orders migrate in done state.

Aptean Purchase Order records map to Odoo purchase.order with vendor assignment, order lines, and open/closed status. PO balances linked to specific Aptean import shipments carry the shipment reference as an external note; we attach the relevant inbound picking to the PO where the shipment record is available. Lead times per PO line migrate to Odoo's date_planned field, and vendor-specific delay adjustments are applied based on the seller_delay values migrated from the vendor record.

Aptean lot genealogy and serial number assignment records map to Odoo stock.lot with full traceability chains: receiving dates, stock movements, and customer shipment links preserved via Odoo's stock.move.line traceability view. Lot expiry dates from Aptean migrate to stock.lot.removal_date, enabling Odoo's FEFO removal strategy. We validate that each Aptean lot number is unique per product before inserting to avoid Odoo's duplicate lot constraint.

Aptean GL account structure migrates to Odoo account.account with account type (receivable, payable, liquidity, expense, revenue), currency assignment, and department/cost-center rollups preserved. Account codes and names migrate 1:1, and the full account hierarchy is replicated so that financial reporting continuity is maintained in Odoo's financial reports and tax mappings.

Outstanding Aptean AP and AR records migrate to Odoo account.move with move_type 'in_invoice' or 'out_invoice' and open status. Credit memos and payment applications migrate as account.move with negative amounts. We flag records near payment threshold for pre-cutover verification with the customer and set the Odoo payment_state to 'not_paid' for all open items. Reconciled records migrate with payment_state 'paid' and a payment_id linking to the reconciliation.

Aptean landed cost allocations are derived at shipment receipt and distributed across items in the container; the per-unit landed cost is not stored as a static item property. We extract the landed cost component values (freight, duty, insurance, agency fees by harmonization code) from the Aptean shipment record and write the final per-unit landed cost back as custom decimal fields on the Odoo product.product record (x_landed_cost_per_unit and x_landed_cost_components as a JSON field). This preserves the cost breakdown for profitability analysis without relying on Odoo's Stock Landed Cost object, which uses a different allocation methodology.

Aptean chargeback deduction records have no direct Odoo equivalent. Odoo has no native deduction management object; chargebacks are handled as manual journal entries or custom fields on the partner or invoice. We extract Aptean deduction reason codes and dispute status, build a deduction-code crosswalk during data audit, and create Odoo journal entries for open chargeback amounts linked to the corresponding customer partner record. The customer reviews the crosswalk before cutover to confirm which deduction codes are written off, disputed, or accepted.

Historical Aptean EDI 850 (purchase orders), 810 (invoices), and 856 (ship notices) documents are stored in a proprietary format that may not parse cleanly through the standard integration layer. We review the EDI archive scope with the customer, extract the functional business content (order lines, quantities, amounts, ship dates, carrier SCAC codes) from whatever export format the system provides, and document the data in a lookup table. Odoo's native EDI module is a separate purchase; we deliver a structured CSV of functional EDI data for the customer's Odoo implementation team to import or map to their EDI module configuration.