Migrate from MONITOR ERP to Odoo ERP

MONITOR Customer records (address, contact, currency, payment terms) map directly to Odoo res.partner records with customer_rank set to 1. The customer code from MONITOR maps to the ref field in Odoo as the dedupe key. Payment terms from MONITOR map to Odoo property_payment_term_id on the partner. Currency settings map to property_product_pricelist and property_account_position_id for tax jurisdiction.

MONITOR Supplier records mirror the Customer structure. We map these to Odoo res.partner records with supplier_rank set to 1. The supplier code maps to ref, and the MONITOR supplier payment terms map to property_supplier_payment_term_id. Any linked Purchase Orders export alongside and are sequenced after partner creation so that partner_id lookups resolve at insert time.

MONITOR Items (with BOM links, routing data, unit of measure, and cost) map to Odoo product.product records. The MONITOR unit of measure maps to Odoo uom_id, and the cost maps to standard_price on the product template. If MONITOR stores the item as a kit or make-to-order, we set the product type to 'product' or 'consu' accordingly. The item code from MONITOR becomes the default_code or the Odoo product barcode field for dedupe validation.

MONITOR Bills of Materials linked to Items do not map as standalone records in Odoo; they become Odoo Manufacturing Bills of Materials attached to the product.template via the bom_ids one2many. MONITOR BOM lines map to mrp.bom.line records with product_id, product_qty, and product_uom_id resolved. MONITOR routing steps (work-centre assignments) map to Odoo mrp.routing.workcenter records on the bom.routing_ids tab. Nested BOMs (sub-assemblies) become linked mrp.bom records with bom_line pointing to the sub-assembly product.

MONITOR Customer Orders (status, lines, delivery dates, pricing) map to Odoo sale.order records. Order status in MONITOR (draft, confirmed, in-progress, closed) maps to Odoo state values (draft, sent, sale_order, done, cancel). Delivery dates from MONITOR map to the commitment_date on sale.order.line. We flag any orders with status 'invoiced' or 'partially invoiced' for reconciliation against MONITOR AR invoice positions before import to avoid duplicate billing.

MONITOR Purchase Orders map to Odoo purchase.order records. The supplier partner_id resolves from the Supplier mapping. Order status maps from MONITOR confirmed and in-progress states to Odoo purchase order states (draft, sent, purchase). Lines map to purchase.order.line with product_id resolved from the Item mapping and price_unit from MONITOR unit cost. Expected delivery dates map to date_planned on order lines.

MONITOR Production Orders carry embedded routing, work-centre assignments, and lot traceability. We decompose them into Odoo mrp.production records (the manufacturing order) and optionally mrp.workorder records for each routing step. The MONITOR production order number becomes the origin field on mrp.production. Lot traceability from MONITOR (lot number, expiry, traceability links) maps to mrp.production.lot_id or mrp.workorder.lot_id in Odoo. If MONITOR stores work-in-progress quantities, we create stock.quant records at the relevant location to set opening WIP balances.

MONITOR AR invoices map to Odoo account.move records with move_type = 'out_invoice'. Invoice header fields (number, date, due date, partner) map to name, invoice_date, invoice_date_due, and partner_id. Invoice lines map to account.move.line with account_id resolved from the MONITOR account code via the chart of accounts mapping. Tax lines map separately as account.tax with amount matched from MONITOR tax codes. We set the payment_state field based on MONITOR's paid/unpaid status and create any partial payments as related account.payment records.

MONITOR AP invoices (bills from suppliers) map to Odoo account.move with move_type = 'in_invoice'. The supplier partner_id resolves from the Supplier mapping. Line-level account codes map to Odoo account.account via the chart of accounts remap. Vendor bill numbers from MONITOR map to the ref field in Odoo for reconciliation against Purchase Orders. Partial payments and payment terms resolve as account.payment records.

MONITOR general ledger journal entries map to Odoo account.move records with move_type = 'entry' (manual journal entry). Account codes from MONITOR's chart of accounts map to Odoo account.account codes via a remap table we build during scoping. Debit and credit amounts migrate to debit and credit fields on account.move.line. MONITOR batch exports do not support date-range filtering; we perform in-house date filtering on the exported file before loading into Odoo to respect the customer's chosen migration window.

MONITOR inventory positions (quantity by Item, Warehouse, Lot/Serial) export as stock reports and map to Odoo stock.quant records. Each quant record carries product_id, lot_id (if serial/lot tracked), location_id (warehouse), and quantity. We flag any lot/serial number fields that require a dedicated lot_id lookup resolution step before the quant import. Stock locations in MONITOR map to Odoo stock.location records created from the warehouse configuration.

MONITOR account codes and account types map to Odoo account.account records via a remap table. Because MONITOR uses per-installation account-numbering conventions, we build the Odoo chart of accounts using the customer's fiscal localization package as the base, then overlay the MONITOR account codes as custom account numbers with their corresponding Odoo account types. Account types (asset, liability, equity, income, expense) map to Odoo's accountType field and user_type_id selection.