Migrate from Manu Online to Odoo ERP

Manu Online Products (manufactured, resold, purchased variants with unit costs and default warehouse) map to Odoo Product Template records. We preserve unit_cost from the manuonline_Products table as the product's standard_cost on the Odoo Product Template. Odoo's product type (stockable, consumable, service) is derived from Manu Online's product type field. Multi-attribute variants in Odoo are created only if the customer uses variant dimensions; otherwise the product template holds a single variant.

Manu Online BOMs (ingredient list and quantities per finished good, multi-level in Enterprise) map to Odoo mrp.bom records. Multi-level Manu Online BOMs with sub-assemblies are restructured into Odoo's nested BOM structure (parent BOM referencing child BOMs as components). Each BOM line carries the Manu Online quantity and unit of measure, with routing operations added in Odoo if the customer wants workcentre scheduling. We flag any BOMs that use Enterprise-only features during scoping so the customer can decide whether to expand them in Odoo or simplify the recipe.

Current on-hand, allocated, and ordered quantities per product per warehouse from manuonline_Stock map to Odoo stock.quant records. We map Manu Online warehouse codes to Odoo stock.location records (Internal Locations hierarchy). Serial and lot numbers from the stock transaction table migrate as Odoo stock.lot records linked to the relevant stock.quant. Any unallocated or negative quantities are flagged in the pre-migration data quality report.

Manu Online Customer records (address, contact, tax registration, price list assignment) map to Odoo res.partner records with the customer_rank set appropriately. We preserve the tax registration number as the Odoo vat field, credit limit as property_account_receivable, and price list assignment as a pricelist_id reference. Active open Sales Orders linked to the customer are migrated in a later phase after the customer record is created.

Manu Online Supplier records (address, contact, lead-time, preferred purchase unit) map to Odoo res.partner records with the supplier_rank set. Lead time in days becomes the delivery_lead_days on the Odoo partner record. Purchase order history and outstanding open POs link to the supplier record after it is provisioned.

Open Manu Online Sales Orders map to Odoo sale.order records with line items, pricing, dispatch instructions, and order status preserved. Partially despatched lines are mapped to Odoo's delivered quantity fields so the fulfilment state is accurate on import. We use Odoo's sale.order onchange mechanisms to recompute taxes after import since Odoo's tax computation is rule-based and may differ from the source tax assignment.

Open Manu Online Purchase Orders map to Odoo purchase.order records with supplier, expected delivery date, and received-versus-ordered quantities. The PO receipt state (fully received, partially received, not received) maps to Odoo's procurement state so that Odoo's incoming shipment workflow reflects the source status without creating duplicate receipts.

Manu Online Works Orders (BOM reference, stock allocation, labour time, completed quantities, stage status) map to Odoo mrp.production (Manufacturing Order) records. We resolve the BOM reference, set the product quantity, and map work order stages to Odoo mrp.production state (draft, confirmed, in_production, done). Unfinished work orders with partial progress are imported at their current state so the production team can resume them in Odoo without re-keying.

Posted Manu Online invoices and credit notes require Xero cutover coordination before migration. We identify all invoices already pushed to Xero and either exclude them from the migration set or mark them as historical to prevent double-posting. Remaining posted invoices migrate to Odoo account.move records in the 'posted' state; draft invoices migrate as draft moves for the customer's accountant to review and post in Odoo accounting.

Manu Online serial and lot numbers linked to stock transactions, works orders, and delivery documents map to Odoo stock.lot records with the lot_name, product_id, and company_id populated. The traceability chain (lot to supplier, through production, to customer delivery) is reconstructed in Odoo via stock.move.line records. We run a pre-migration traceability completeness audit: if the customer historically received stock without recording supplier lot numbers, the inbound traceability leg is blank and we flag this before migration begins.

Active Manu Online user accounts (login, email, role-based permissions) map to Odoo res.users records. We preserve the login and email, and flag any accounts with elevated admin privileges for explicit re-creation in Odoo with the appropriate access rights groups (Inventory / Manufacturing / Sales / Accounting / Administration). Odoo's group model (res.groups) is provisioned before the migration of transactional records.