Migrate from Odoo Enterprise to Infor CloudSuite Corporate

Odoo's res.partner is a single model handling customers, suppliers, and individuals with no native role distinction. Infor CloudSuite separates Business Partner roles: Customer, Supplier, Prospect, and Competitor, each with separate address and contact assignments. We split each Odoo partner into one or more Infor Business Partner roles based on Odoo partner categories (customer_boolean, supplier_boolean, industry_id) and address assignments. Individual contacts separate into Infor Contact records linked to the Business Partner. Email, phone, and address fields map directly; the Odoo category_ids become Infor Business Partner Category codes that we configure during migration.

Odoo product variants (product.product) and product templates (product.template) map to Infor CloudSuite Item records. We map Odoo product.default_code to Infor Item Number, product.name to Description, and product.list_price to Base Price. Product variants (size, color, dimension) resolve into Infor Item Variants or as separate Item records depending on the Infor edition's variant handling configuration. Vendor pricelists (product.supplierinfo) migrate as Infor Supplier Item records linked to the corresponding Business Partner Supplier role.

Odoo Sales Orders map to Infor CloudSuite Sales Orders with Order Number, Order Date, Customer (Business Partner), and line items. We resolve Odoo sale.order.partner_id to the corresponding Infor Business Partner Customer role, and sale.order.order_line.product_id to Infor Item references. Order states (draft, sale, done, cancel) map to Infor Order Status codes that we configure during the migration setup. Odoo delivery addresses stored in sale.order.partner_shipping_id become Infor Ship-To addresses on the order.

Odoo Purchase Orders map to Infor CloudSuite Purchase Orders with Order Number, Order Date, Supplier (Business Partner), and line items. We resolve Odoo purchase.order.partner_id to the Infor Business Partner Supplier role. Delivery dates, product quantities, and unit prices transfer directly. Receipt matching (stock.picking linked to purchase.order) preserves as Infor Receipt records. Odoo product-supplier info drives the Infor Supplier Item cross-reference on the purchase order.

Odoo posted customer invoices (account.move with move_type = out_invoice) map to Infor CloudSuite Invoice records. We map invoice.partner_id to the Infor Business Partner Customer role, invoice.invoice_date to Invoice Date, and invoice.amount_total to Total Amount. Fiscal positions and tax codes from Odoo's account.fiscal.position table require full remapping to Infor's tax codes and GL Account assignments, as the country-specific localization modules do not carry over. Reconciliation records (account.reconcile.model) do not migrate; they require reinstating in Infor's payment matching configuration.

Odoo vendor bills (account.move with move_type = in_invoice) map to Infor CloudSuite Vendor Invoice records. We resolve vendor bill partner_id to the Infor Business Partner Supplier role. Tax amounts and GL Account assignments remap to Infor's Chart of Accounts. Odoo vendor bill payment state (paid, partial, unpaid) carries as Invoice Status. Posted vendor bills migrate; draft bills are included only if requested and flagged by the customer during scoping.

Odoo's Chart of Accounts is country-specific via localization modules (l10n_fr, l10n_de, etc.) and does not carry over directly to Infor CloudSuite, which has its own country-specific account structures. We do not migrate the Odoo Chart of Accounts as records. Instead, we deliver a written mapping document pairing each Odoo account code and type to the corresponding Infor GL Account code, name, and account type. The customer and their Infor implementation partner configure the Infor Chart of Accounts before the accounting migration phase begins. Open invoice amounts and historical balances migrate as journal entry lines posting to the configured Infor GL accounts.

Odoo Bill of Materials (mrp_bom, mrp_bom_line) map to Infor CloudSuite Bill of Material records with routing operations. We map bom.product_id to the Infor Item, bom_line.product_id to component Items with quantities and units of measure. Odoo bom.routing_ids (work order operations) map to Infor Work Center operations with setup time, run time, and queue time. Multi-level BoMs (subassemblies) resolve recursively so that component lookups are satisfied before parent-level import. We flag any Odoo BoM with by-products or co-products for Infor Work Order configuration review.

Odoo Work Orders map to Infor CloudSuite Work Orders linked to the corresponding Item and Bill of Material. We map workcenter_id to Infor Work Center, duration (hours) to planned labor time, and state (pending, ready, in progress, done) to Work Order status. Odoo workorder tracked lot/serial numbers carry as Infor Job Traveler lot assignments. We do not migrate Odoo workorder time tracking (mrp.workcenter.productivity) as time entries; the customer configures Infor Shop Floor data collection post-migration.

Odoo stock.quant (on-hand quantities by lot/serial and warehouse) map to Infor CloudSuite inventory on-hand records per Item and warehouse. stock.picking records (receipts, deliveries, internal transfers) map to Infor Receipt, Issue, and Transfer records. We resolve warehouse_id to Infor Warehouse, product_id to Item, and lot_id to Infor Lot Number. Quant snapshots migrate as current on-hand values; historical stock.move records are migrated as Infor inventory transactions for audit trail completeness up to a configurable cutoff date. Odoo product routes (make-to-order, dropship) require Infor planning configuration review as these do not migrate as data.

Odoo Project and Task records map to Infor CloudSuite Project and Task/Subtask. We map project.name to Project Description, project.user_id to Project Manager, and project.task count to Task hierarchy. Task stages migrate as Infor Task Status values. Odoo project timesheets (account.analytic.line) migrate as Infor Project Transaction labor entries if the customer's Infor license includes Project Accounting. We do not migrate Odoo project automation rules or stage-triggered actions.

Odoo hr.employee records map to Infor CloudSuite Employee or Worker records. We map employee name, department, job title, and employment status. Active employee contracts (hr.contract) migrate as Worker records with effective dates and employment type. Historical payslip data migrates as read-only records; Infor HCM payroll configuration is out of scope. Employee bank accounts and emergency contacts map to Infor Worker Contact Information fields.