Migrate from Infor M3 to Odoo ERP

M3 Items (MITMAS) map to Odoo Product records. We export Items with all associated costing models and unit-of-measure conversions. M3's stocking unit vs purchasing unit distinction maps to Odoo's UoM configuration with the corresponding UoM category. Custom fields attached to Items in M3 scan as Product attributes in Odoo; fields marked display-only in the M3 API are excluded and noted in the custom field manifest for admin re-creation.

M3 Customer Orders export as Odoo Sale Orders with header and line-level data. Order status values (pending, confirmed, shipped, invoiced) map to Odoo sale_order states. Multi-line orders with partial shipments preserve line-level delivery scheduling through Odoo's procurement orchestration. M3's customer order holds and credit blocks map to Odoo warning fields on the partner record.

Purchase orders and supplier invoices from M3's procurement API export as Odoo Purchase Orders. Header and line-item structure transfers directly, with M3's delivery schedule lines mapped to Odoo's scheduled date per line. Supplier invoice data (Voucher/Invoice matching) maps to Odoo Vendor Bills with account reconciliation.

M3 BOMs have multi-level structures with operations, resources, and by-products that require flattening before Odoo import. We export the full BOM hierarchy, collapse it to Odoo's single-level BOM structure (phantom BOMs become kit products), and flag any configured or attribute-controlled products that require Odoo's product variants with dynamic attributes. Routing operations (work centers, cycle times) map to Odoo Work Orders with work center capacity constraints.

Work Orders map to Odoo Manufacturing Orders with status, operations, and time entries preserved. M3 work order routing operations map to Odoo work order steps with the corresponding work center. Backflushed materials and by-products transfer as MO components and by-products. Open work orders export with current operation step and remaining quantity; completed work orders export as MO history.

Inventory quantities, warehouse locations, and bin locations export from M3's warehouse management module. We map M3 warehouse codes to Odoo warehouse records and M3 bin locations to Odoo stock locations within the warehouse hierarchy. On-hand quantities, reserved quantities, and incoming/outgoing quantities transfer to Odoo Quant records with the corresponding location context.

Inter-site and inter-company transfer orders export as Odoo internal transfers (stock moves between warehouses). Shipment and receipt details transfer as incoming and outgoing picking records linked to the transfer. Multi-leg distribution orders with intermediate stops split into separate Odoo transfer documents.

General ledger accounts, accounts payable, and accounts receivable are exportable but require explicit mapping to Odoo's chart of accounts structure. We extract the M3 account hierarchy, map to Odoo account types (receivable, payable, expense, revenue, etc.), and flag open AP/AR records requiring careful sequencing after chart of accounts is configured. M3's multi-company accounting structure maps to Odoo multi-company configuration with shared or separate charts per company.

M3's account structure with multi-company associations maps to Odoo's chart of accounts configuration. We export the full account hierarchy including cost center associations and inter-company elimination accounts. The customer defines the account mapping strategy (chart template, country-specific localization) during scoping before any data migration begins.

Fixed asset records include depreciation schedules and asset classifications. We export asset master records and depreciation history, flagging any assets with open depreciation periods. Depreciation method (straight-line, declining balance) maps to Odoo asset depreciation profiles. Assets in service, under maintenance, or fully depreciated transfer with their current book value and remaining depreciation schedule.

Organizational units used across finance, HR, and operations modules export for re-creation in Odoo. M3 cost center hierarchies map to Odoo departments, analytic accounts (for cost tracking), and user access groups. Multi-level department structures flatten to Odoo's single-level department hierarchy with parent-child relationships preserved where Odoo supports them.

M3 custom fields attached to various objects are searchable via Infor Enterprise Search. We extract custom field definitions and their values per company and per module, filter out display-only fields not exposed in the API, and map transferable fields to Odoo custom fields on the equivalent object or to product attributes for item-level customizations. The custom field manifest is delivered for admin re-creation of any omitted fields.