Migrate from Odoo ERP to Infor CloudSuite Corporate

Odoo Partners (type contact or company) split into Infor CloudSuite Contact records for customer-facing records and Supplier records for vendor records. The Odoo partner category (res.partner.category) maps to Infor Contact classification fields. We preserve address, phone, email, and bank details and resolve the Country/State references to Infor's coded address format. Multi-company Odoo configurations require entity-level segmentation in Infor before Partner import begins.

Odoo Product records map to Infor Item Master. The Odoo product type (product.template type: stockable, consumable, service) maps to Infor's item type codes. Product variants via attribute combinations (product.template.attribute.line) flatten into separate Infor Items or variant codes depending on the Infor edition configuration. The Odoo Standard Price and List Price map to Infor's cost and selling price fields, with currency preserved per Odoo's pricelist configuration.

Odoo's vendor pricing relation (product.supplierinfo) maps to Infor Supplier Item records, preserving vendor lead times, minimum order quantities, and supplier product codes. The many2one to res.partner (supplier) resolves through the Contact/Supplier mapping established in the Partner phase before this phase runs.

Odoo Sales Orders map to Infor Sales Orders. The Odoo order state lifecycle (draft → sale_order → done → canceled) maps to Infor order status codes. Order lines with product, quantity, and unit price migrate directly; discounts stored as Odoo discount fields map to Infor line discount columns. Odoo's fiscal position tax computation logic must be replicated in Infor's tax configuration before order lines are imported because tax computation rules are destination-side.

Odoo 17+ unified invoices into account.move with move_type distinguishing invoices from refunds. Posted invoices migrate as Infor A/R Invoices; posted refunds migrate as Infor Credit Memos. We preserve the invoice number, date, due date, and line amounts. Tax lines from Odoo map to Infor tax distribution lines, but country-specific fiscal positions and tax groups require explicit Infor configuration before invoice import because these are schema-level in Infor, not data-level.

Odoo Stock Quants tracking on-hand quantities per location map to Infor warehouse and sub-location inventory records. We map warehouse codes by matching Odoo's stock.warehouse name to Infor's warehouse site codes. Lot and serial number traceability migrates where present in Odoo, but traceability verification is a post-import step because lot status and expiration date formats differ between systems.

Odoo Stock Moves representing inventory transfers and adjustments map to Infor inventory transaction records. Move states (draft, assigned, done, canceled) map to Infor transaction status codes. The many2one references to stock.location and stock.warehouse resolve through the location mapping established in the inventory phase. Quantities and unit of measure carry forward;UoM conversion factors require explicit mapping where Odoo uses non-standard units.

Odoo Manufacturing Orders (mrp.production) map to Infor Production Orders. The Odoo BoM reference (bom_id) resolves through the BoM mapping phase before production orders are imported. MO state (draft, confirmed, in_production, done) maps to Infor production order status. Workorder sequences from Odoo map to Infor routing operations, but routing dependencies may require re-sequencing in Infor's operation planning view because Infor uses a different routing structure model.

Odoo Bills of Materials (mrp.bom) map to Infor Product Structures. BoM type (kit, manufactured, phantom) carries forward. Component lines with product, quantity, and unit of measure migrate as Infor BOM lines. Phantom BoMs used for kits in Odoo map to Infor Kitting structures. Variant-specific BoMs require mapping to Infor Item variants using the product variant resolution established in the product phase.

Odoo Project records map to Infor Project. Project stages from Odoo's kanban pipeline map to Infor project status codes. Multi-company Odoo projects require explicit Infor entity assignment before import. Odoo project hierarchy (parent project) maps to Infor project structure.

Odoo Tasks link to Projects via project_id and include sub-task hierarchy via parent_id. We preserve the task hierarchy, stage, assignee (user_id), deadline (date_deadline), and custom fields. Task assignees resolve through the Odoo User mapping to Infor Worker or User records. Custom stage names from Odoo Studio map to Infor task status codes.

Odoo Employee records (hr.employee) map to Infor Worker records. Employee name, department, job title, and work contact info migrate. Odoo-specific fields like emergency contacts and HR categories do not have direct Infor equivalents and are preserved in a text block or custom field for manual entry in Infor's HCM module. Employee user linking (employee_id → res.users) resolves through the User mapping phase.