Migrate from Infor CloudSuite Corporate to Odoo ERP

Infor CloudSuite hierarchical COA with cost center and department rollups maps to Odoo Accounting Chart of Accounts. We preserve account type (Asset, Liability, Equity, Income, Expense), department assignments, and currency denomination. For multi-company Infor deployments, we create corresponding Odoo companies and map each COA segment to the correct Odoo company before opening any fiscal periods. Multi-currency accounts retain their currency setting in Odoo's Accounting > Settings > Currencies configuration.

Infor Customer master records (stored in the Address Book with payment terms, credit limits, and tax registration codes) map to Odoo res.partner records with the customer flag set to True. We extract the address book entry, payment term (mapped to Odoo's account.payment.term), credit limit (mapped to credit_limit on res.partner), and tax registration (mapped to vat field). Customer-specific pricing lists from Infor map to Odoo Pricelist records linked to the Contact.

Infor Vendor master records map to Odoo res.partner with the supplier flag set to True. We extract address, payment terms, and tax ID (VAT field), preserving vendor-specific data including any supplier-specific lead times stored in Infor's purchase configuration. Vendor master data is loaded before Purchase Agreements to satisfy the supplier reference on purchase documents.

Infor Items carry unit of measure conversions, costing method, BOM linkages, and warehouse-specific stocking data. We map the core item record to Odoo product.template with type (consumable, service, stockable). Costing method (standard, average, FIFO) maps from Infor's costing configuration to Odoo's costing method on the product form. BOM linkages from Infor map to Odoo bill of materials records created separately during the manufacturing migration phase. UOM conversion tables require pre-creation of Odoo Units of Measure before item migration begins.

Open payables in Infor CloudSuite extract as vendor invoice headers and distribution lines. We load these as Odoo account.move records of type in_invoice linked to the vendor Contact. Payment terms from Infor determine the due date on the Odoo Vendor Bill. Open AP must reconcile to the penny at cutover; any discrepancy between the sum of migrated invoice lines and the vendor account balance in Infor blocks Odoo vendor bill posting. We run a pre-flight balance check before committing AP records.

Open receivables in Infor extract as customer invoice headers and distribution lines. We load these as Odoo account.move records of type out_invoice linked to the customer Contact. Aging bucket assignments from Infor map to Odoo's Follow-up Management configuration for each Contact. Open AR must also reconcile to the penny at cutover; any discrepancy between migrated invoice totals and the Infor AR account balance prevents Odoo customer invoice posting.

Infor Purchase Agreements include vendor reference, terms, and expiration at the header level and line-level pricing, quantities, and UOM at the line level. We map the header to Odoo purchase.agreement (if the customer has the Purchase Agreements app installed) or to sale.order template equivalents for blanket orders. Line-level pricing conditions from Infor that cannot be represented as Odoo standard price list rules are flagged as requiring custom configuration post-migration.

Infor Work Orders carry routing steps, material allocations, and status (open vs closed). We map the work order header to Odoo mrp.production, component lines to mrp.bom.line entries, and routing sequences to Odoo workcenter operations. Open work orders migrate in full; closed work orders migrate as historical records linked to the production order. Closed manufacturing orders with no remaining quantities are migrated as closed records with no pending quantity for planning. BOM linkages are resolved against the item master migration to ensure component references point to valid Odoo product.template records.

Infor CloudSuite user-defined fields attached to items, suppliers, and purchase agreements (called Technical Datasheet fields in CloudSuite Industrial, Custom Fields in CMS470) require pre-creation in Odoo as custom ir.model.fields before the associated records migrate. Alphanumeric and numeric custom fields migrate directly. Custom date fields require a workaround because Infor Enterprise Search cannot query date fields at the SQL level; we extract these via direct SQL query and transform them to Odoo date format during the staging phase. Custom field groups are defined per item group or supplier group and must be replicated as Odoo property groups before data load.

Infor Document Management stores attachments against customer orders, purchase orders, and work orders as configurable widgets. We migrate the association metadata (document reference, linked object type, linked object ID) as Odoo ir.attachment records pointing to the migrated document target. Binary file storage is handled as follows: we migrate the file reference URL if Infor Document Management uses external storage, and we flag binary file content migration as a separate scope requiring Infor document database access. Odoo's attachment limit is 115 characters for the file name field; we truncate and hash long Infor document names to maintain uniqueness.

Infor user accounts, role assignments, and permission groups require mapping to Odoo's res.users and access control groups. We extract Infor role profiles from the migration database and map them to Odoo access rights groups (Access Rights tab on the User form). Infor's multi-company user assignments map to Odoo's multi-company user flag with the allowed_company_ids field set per user. Active versus inactive status is preserved; inactive Infor users are created as Odoo portal users or inactive users depending on the customer's preference.

Infor OS audit logs and background task definitions are environment-specific infrastructure records that have no meaningful equivalent in Odoo. We do not migrate these. Transaction-level audit fields on individual records (created_by, created_date, modified_by, modified_date) are preserved where they exist as standard fields on the migrated record.