Migrate from Odoo ERP to Acumatica

Odoo partners with customer=True map directly to Acumatica Customers. The primary address, email, phone, and VAT registration fields transfer as-is. Secondary addresses on the Odoo partner become Shipping Addresses on the Acumatica Customer — each linked via the Address tab with a separate address record.

Odoo partners with supplier=True map to Acumatica Vendors. Payment terms, fiscal information, and bank account details carry over as Vendor attributes. Acumatica's VendorClass assignment (e.g., Domestic, Foreign) should be set based on country or tax configuration from the Odoo partner record.

Odoo partners flagged as both customer and vendor require duplication into separate Customer and Vendor records in Acumatica. We preserve the original Odoo partner ID in both records as SourcePartnerID__c custom fields for traceability. Merging is not possible in Acumatica since the two entity types have separate screens, access rights, and posting behaviors.

Odoo stockable products map to Acumatica InventoryItem records with the Stockable item type. The product.template fields (name, default_code, list_price, standard_price) transfer as ItemID, Description, Base Price, and Cost fields. Post-migration, the Acumatica Item Types screen must be configured to enable inventory tracking for each migrated item.

Odoo consumables and services map to Acumatica Non-Stock Items. These items lack inventory tracking in Acumatica by default; the Non-Stock flag prevents stock transactions from being posted against them. If the Odoo product has bills of materials, those do not migrate and must be reconstructed as Acumatica bills of materials if manufacturing is in scope.

Odoo product variants created via attributes (size, color, etc.) do not map to a native variant structure in Acumatica. Acumatica Matrix Items handle attribute combinations differently — each matrix generates child stocking IDs per attribute value. We create the parent Matrix Item and generate child items for each Odoo variant, linking back to the source variant via SourceVariantID__c.

Odoo sale.order documents migrate as Acumatica SalesOrders with header fields (name, partner_id, date_order, commitment_date) and line items (product_id, product_uom_qty, price_unit, discount). Order-status workflow states (draft, sent, sale, done, cancel) map to Acumatica statuses (on-hold, pending, open, completed, cancelled) using value mapping on the status field.

Posted Odoo customer invoices migrate as Acumatica ARInvoices. The invoice date becomes the document date, the Odoo journal entry number becomes the reference, and line items carry over with tax assignment. Odoo's partial payment handling (invoice with residual) requires mapping to Acumatica's Payment Plan feature if those records exist.

Odoo vendor bills map to Acumatica APInvoices. Vendor location and payment terms from the Odoo vendor record carry forward. If the Odoo bill is linked to a purchase order via Odoo's PO-Bill flow, the Acumatica APInvoice can reference the corresponding PO Receipt if that workflow is replicated.

Odoo incoming shipments (picking type = in) map to Acumatica Receipts against a Purchase Order. Lot numbers and serial numbers assigned at receipt in Odoo carry over as Lot/Serial Nbrs on the Acumatica receipt line. If no PO exists in Acumatica for the receipt, we create a standalone Receipt document and flag it for reconciliation.

Odoo outgoing shipments map to Acumatica Shipments, each directly linked to its corresponding Sales Order. Shipment line quantities align with the done_quantity values from the Odoo stock.move records, preserving the exact shipped amounts. Back-order references that existed in Odoo transfer as linked shipment documents in Acumatica, maintaining the relationship chain between original transfers and subsequent partial shipments.

Odoo analytic accounts (used for project accounting, cost-center tracking) map to Acumatica Subaccount dimension values. The analytic.account name becomes the Subaccount description; the code maps to the SubaccountID. Subaccounts must be created under the appropriate Subaccount segment in the Chart of Accounts screen before the migration run.

Odoo lot numbers (stock.productionlot) carrying item ID, lot number, and expiration date migrate as Lot/Serial Nbr records in Acumatica's Lot/Serial Nbrs screen. The link between lot and item is preserved via the ItemID field on the lot record. FIFO enforcement via lot expiration requires Lot/Serial Class configuration in Acumatica.

Odoo users map to Acumatica users by email address matching. The Odoo partner_id on sale orders and account moves resolves to the matched Acumatica user. Unmatched owners are flagged as exceptions before migration; your Acumatica admin either creates matching users or reassigns records to a fallback owner during the migration plan review.

Odoo file attachments stored in ir.attachment (binary fields linked to records) re-upload to Acumatica Files attached to the corresponding entity (Customer, Vendor, SO, Invoice). Large files follow Acumatica's file size limits per document type. Inline images in Odoo notes are downloaded and rehosted in Acumatica's note storage.