Migrate from Ridder iQ to Odoo ERP

Ridder iQ Customer records map to Odoo Contact with address, email, phone, and payment terms. Odoo distinguishes between Contact and Address (res.partner with type=delivery or invoice), so billing and shipping addresses from Ridder iQ become separate Address records linked to the same Contact. Customer-specific margin or credit limit fields map to custom fields on the Contact record.

Ridder iQ Supplier master records map to Odoo Contact with the Supplier checkbox enabled. We preserve supplier-specific data including payment terms, lead times, and preferred delivery addresses. Any Supplier-specific notes map to the Contact internal notes field. Supplier-linked Items in Ridder iQ require the supplier to be present before the Item import so that the supply chain link is satisfied.

Ridder iQ Items cover raw materials, components, and finished goods and carry unit-of-measure, cost, and supplier-link data. We map the item number to Product SKU, description to product name, unit of measure to UoM, and cost to the product's standard cost field. Items with multiple UoMs in Ridder iQ require UoM category mapping in Odoo. Supplier info and lead times become Purchase tab data on the Odoo product form. Multi-stock-location items get configured with Odoo's multi-warehouse routing.

Ridder iQ allows BOM components to be marked as produced or purchased at the component level, creating multiple valid production paths for the same finished item. Odoo assigns a single make-or-buy type to each BOM line. We handle this by creating a separate Odoo BOM variant for each unique production path found in Ridder iQ, with the primary BOM flagged as the default. Items with more than one active BOM variant are flagged for customer review before migration commits to a variant set. Phantom assemblies from multi-level Ridder iQ BOMs are marked as Phantom BoM type in Odoo so that the parent BOM auto-explodes during work order creation.

Ridder iQ Production Orders reference a BOM and a routing, carrying scheduled start and end dates, work center assignments, and component allocations. We map to Odoo Manufacturing Order with the BoM reference resolved, scheduled dates preserved, and component demand lines auto-generated from the BOM. Work center assignments in Ridder iQ map to Odoo Work Centers, and we flag any split scheduling or overlapping operations that require manual routing configuration in Odoo. Closed production orders migrate as read-only records; open orders migrate as active Manufacturing Orders.

Ridder iQ Sales Orders span the quote-to-invoice lifecycle and carry pre- and post-calculation margin data per line that not all Odoo configurations expose by default. We map order headers, line items with quantities and prices, order status, and customer reference fields. Margin data requires a custom field or Odoo sale margin module to be activated before migration; we flag this configuration dependency during scoping. Confirmed and draft orders migrate as active Sale Orders; locked or closed orders migrate as read-only historical records.

Ridder iQ Purchase Orders link to Suppliers and Items, with order quantities often driven by BOM-level demand calculations. We map PO headers and line items, preserving supplier references and due dates. Open POs in Ridder iQ can be replicated as active Purchase Orders in Odoo and confirmed for receipt tracking. Closed or received POs migrate as historical records without triggering further Odoo procurement actions. Purchase requisitions linked to production demand in Ridder iQ map to Odoo Request for Quotation or Purchase Agreement records depending on the sourcing rule type.

Ridder iQ Projects coordinate multi-department ETO workflows including R&D, engineering, purchasing, and production phases. We map the project header with its budget and milestone data, and recreate phases as Odoo Project Tasks. Cost tracking data from Ridder iQ maps to Odoo Project analytic account entries, though Odoo's native budget control requires Project to be linked to an analytic plan. Customer review is required to confirm which project tracking dimensions map cleanly and which require Odoo Timesheet or custom reporting configuration.

Ridder iQ Invoices link to Sales Orders and track payment status. We preserve invoice headers, line items, amounts, and payment reconciliation records. Historical closed invoices migrate as read-only account moves in Odoo. We do not re-post invoices in Odoo; they are entered as posted entries so they appear in reports without triggering accounting actions. The Odoo journal (Sale Journal for customer invoices, Purchase Journal for supplier bills) is assigned during migration based on the invoice direction.

Documents attach to multiple Ridder iQ objects including Orders, Projects, and Items and include version history. We export file attachments and document metadata. Each document is linked to the corresponding migrated record in Odoo (sale order, project task, product template) via ir.attachment records. We do not migrate version-diff data or previous revision chains; the current revision becomes the sole version in Odoo. Document tags from Ridder iQ map to Odoo tags if the Document app is activated in the destination instance.

Ridder iQ stores pre-calculation and post-calculation margin data per sales order line, which Odoo does not expose as a standard field. During scoping, we identify whether the customer requires margin preservation for reporting or audit purposes. If required, we add a decimal custom field to the sale.order.line model before migration and populate it from the Ridder iQ margin columns. The customer activates the Odoo sale_margin module or approves a custom field addition during the configuration phase.