Migrate from Infor LN to Odoo ERP

Infor LN maintains Business Partners as a single entity type with a Role field distinguishing customers from suppliers; address, contact, and financial limits are child records. We map LN Business Partner records to Odoo Contact with a type flag (customer, supplier, or both) and address data mapped to Odoo's contact address model. Multi-address Business Partners with distinct delivery and invoicing addresses in LN become separate Odoo Contact addresses linked to the same partner record.

Infor LN supports multiple financial companies within a single logical instance, each with its own chart of accounts, fiscal calendar, and tax configuration. Odoo ERP's multi-company module (Custom plan) or separate instances per entity handles this. We extract all financial company definitions, map each to an Odoo Company record, and flag intercompany journal entries that reference multiple financial companies so that the customer can reconstruct them as cross-company moves in Odoo or resolve them manually before closing each period.

LN Items carry rich attribute data including BOM structures, routing steps, costing information, and unit of measure conversions. We map Item Master records to Odoo Product Template with variant support enabled for items carrying size, color, or dimension attributes. Unit of measure and UoM category mapping requires a conversion table since LN's UoM library and Odoo's UoM model use different internal naming conventions. Stock valuation method (standard, average, FIFO) from LN transfers to Odoo's product category costing configuration.

LN Sites represent physical or logical locations with their own inventory policies, location definitions, and receiving rules. Multisite Control data governs cross-site stock transfers. We map LN Sites to Odoo Warehouse records with the location hierarchy preserved as Odoo Stock Locations. Cross-site transfer orders in LN become internal transfer orders in Odoo. Receiving rules and ASN expectations from LN site configuration map to Odoo warehouse incoming route configurations.

LN BOMs support multiple levels of nesting, phantom assemblies, option classes, lead-time offsets, and ECO revision overlays. We flatten multi-level BOMs into Odoo's BOM structure, preserving the component hierarchy and routing references. Phantom assemblies in LN map to Odoo phantom BOM type. ECO revision-controlled BOM overlays become separate Odoo BOM versions (one per active revision). Lead-time offsets and routings transfer to Odoo Work Centers and operations.

LN separates purchase order headers from lines and schedule dates; purchase contracts (blanket orders) link to release schedules that decrement funded quantities. We map PO headers and lines to Odoo Purchase Order, preserving header-level terms, payment conditions, and line-level scheduled delivery dates. Blanket order release schedules become Odoo Blanket Orders linked to corresponding Purchase Orders. PO approval workflows in LN (which may be multi-tier approval chains) are documented separately as an automation inventory item since they do not migrate as code.

Sales order pricing in LN can resolve through price books and matrix definitions; multicompany sales invoicing can combine lines from Sales, Project, and Service logistic packages onto a single invoice. We map SO headers and lines to Odoo Sale Order, preserving pricing, scheduled dates, and line discounts. Price resolution logic that relied on LN matrix priority chains is replaced with Odoo Price List rules, and the LN priority chain is preserved as a metadata field on the product for admin reference. Multicompany SO lines that span entities are flagged for manual reconciliation in Odoo.

LN Projects support ETO and MTO lifecycles with phase structures, work breakdown hierarchies, and billing milestones. We map project phases to Odoo Project tasks with a hierarchical task structure preserving phase-to-task relationships. Milestone-based billing milestones map to Odoo Milestones linked to project tasks, and the billing rule type (time-and-materials, fixed price, milestone) is preserved as a project tag. Note that Odoo Project does not natively support the full ETO planning depth of LN Project; complex ETO project plans may require custom development or an Odoo add-on module.

LN Service Contracts track entitlement, coverage periods, and SLA terms; field service records include technician assignments, mobile dispatch data, and parts consumed. We map service contract terms to Odoo Maintenance Contract (or Field Service app if licensed) with coverage period and SLA terms preserved as contract line items and tags. Technician assignments and parts consumed from LN field service records transfer to Odoo Task records within the Field Service project. Odoo Field Service is a separate licensed application; if it is not in scope, service contracts migrate as maintenance records only.

LN custom fields are defined in the Extensions package with a Domain property specifying data type, and values are stored in dedicated extension tables joined to base object tables. We read the Domain definition from the Extensions package before mapping to Odoo field types, rejecting any column where the domain type cannot be coerced to the Odoo field type. Two custom fields with the same logical name but incompatible domains are treated as separate fields. The customer must confirm which LN custom fields are still active and relevant before migration, as legacy or obsolete extension fields should be archived rather than migrated.

Price matrices in LN use priority-based search rules across purchase, sales, and transfer price types with matrix attributes as dimensions; item surcharges function as cost adders in valuation price calculations. We export the full Matrix Definition (tdpcg0610m000) metadata alongside each price book and preserve the priority chain as a custom JSON field on the product template. Pricelist rules in Odoo do not support the same priority chain resolution model; the customer's admin rebuilds the priority logic as individual Odoo pricelist rules or accepts a simplified first-match resolution in Odoo. Surcharges transfer as additional pricelist rule lines with a surcharge product.

LN stores document references (pointers to file storage) rather than binary content in most transactional tables. We extract the document metadata and URL paths from LN's document management references and map them to Odoo ir.attachment records. Large binary file migration (drawings, PDFs, images) is out of migration scope; we deliver a manifest of file references with storage paths for the customer's IT team to relocate into Odoo's document storage or an integrated DMS. Document version history from LN (if present) transfers as a comment on the Odoo attachment record.