Migrate from Infor VISUAL to Odoo ERP

VISUAL Work Orders are the primary production record, combining a routing header with materials attached to specific operations. Odoo Manufacturing Orders reference a BoM but do not natively attach materials per operation step. We map the Work Order header to MO (product, quantity, date_planned), reconstruct the operation sequence from the VISUAL routing as MO workstation lines, and attach materials from the VISUAL per-operation material list either to the MO directly (if Odoo BoM is flat) or as a mapped BoM with operation-linked components. The operation-to-material linkage is preserved in a custom field mo_visual_op_seq__c on each component line for audit.

VISUAL Routings define the sequence of operations and the resources (labor, machine, work center) each step requires. Odoo uses Workcenter records (name, capacity, time efficiency) and Work Order operations attached to the Manufacturing Order. We map routing headers to Odoo Workcenter definitions and operation lines within the MO, preserving setup time, run time, and sequence number. If VISUAL routing references work center codes, we match them to Odoo Workcenter records by name or create them during the Workcenter migration phase.

VISUAL allows BOM materials to be scattered throughout the routing rather than stored as a centralized multi-level structure. Odoo BoM types includekit, manufacture this product, and subcontract. We flatten VISUAL per-operation materials into a multi-level Odoo BoM with sub-assemblies where applicable, preserving the operation sequence from VISUAL as routing_order on the Odoo BoM line. Cases where destination BoM structures cannot represent the source operation dependency are flagged for manual Odoo BoM configuration review.

VISUAL Item master records (SKU, description, unit of measure, cost, revision) map to Odoo Product records. Item type (stockable, consumable, service) maps to Odoo Product Type. Standard cost from VISUAL becomes Odoo Product standard_price. We map VISUAL revision-controlled items to Odoo product variants if the destination uses variant tracking, and flag revision fields that require manual mapping where Odoo does not have a direct equivalent.

VISUAL Customer Orders drive the order-to-cash cycle and include order headers, line items, pricing, and EDI-ready CPO transaction set data. We map Customer Order headers to Odoo Sale Order, line items to Sale Order Lines (with product, quantity, price unit), and preserve order references, terms, and shipping instructions. EDI-ready formats are preserved in Odoo by mapping to the EDI module's purchase order synchronization if the destination Odoo instance has EDI installed; otherwise we flag EDI-ready records for manual configuration review.

VISUAL Purchase Orders and associated ASN records migrate with full header and line detail. ASN EDI 856 data extracts from VISUAL fixed-length file exports. We map PO headers to Odoo Purchase Order, line items to PO Lines, and vendor references by vendor number match. ASN data maps to Odoo's incoming picking (stock.move) if the destination uses Odoo's inventory module for receiving validation.

VISUAL Customer master records include addresses, contacts, credit limits, and EDI trading partner assignments. We map to Odoo Contact records with is_company=False for contacts and is_company=True for companies. Address data maps to Odoo's partner address fields (street, city, state, zip, country). Credit limit maps to Odoo's credit_limit field on the partner. EDI trading partner assignments extract from the separate VISUAL EDI configuration records (see gotchas) and map to the Odoo partner's EDI trading partner fields.

VISUAL Vendor master records include addresses, payment terms, and EDI configuration. We map to Odoo Contact records with supplier_rank > 0 to designate as vendor. Payment terms from VISUAL (net 30, net 60, etc.) map to Odoo Payment Term records created during configuration. EDI configuration extracts from VISUAL's separate configuration tables and maps to Odoo partner EDI trading partner fields.

VISUAL Invoices export as EDI 810 fixed-length files or through the Excel export background job. We map invoice headers, lines, and sublines to Odoo Account Move (invoice type). Tax handling requires mapping VISUAL tax codes to Odoo tax tags and accounts because the two systems use different tax code structures. Any custom invoice layouts or notes fields are flagged for post-migration manual review because Odoo's invoice layout customization is report-driven rather than field-driven.

VISUAL GL account structure and balances export via the database export tool or Excel. We map VISUAL account codes and descriptions to Odoo Account records, preserving account type (view, receivable, payable, credit, debit, liquidity) and grouping. Multi-company or intercompany account segments may require Odoo account code restructuring if VISUAL uses segment-encoded account codes that Odoo's flat account structure cannot represent without re-numbering.

Open payables and receivables require balance verification during migration. We extract open invoice detail from VISUAL (invoice number, date, amount, open amount, payment terms, due date) and map to Odoo Open Invoices (account.move with state=draft or open depending on validation status). Partial payment tracking in VISUAL maps to Odoo's payment register lines linked to the parent invoice. Balance reconciliation between VISUAL GL and Odoo account.move after migration is required before the customer closes the accounting period in VISUAL.