Migrate from Intact iQ to Odoo ERP

Intact iQ customers map directly to Odoo res.partner records with customer=True. The supplier counterpart is a separate Intact iQ entity; both land in the same Odoo table with type differentiation via customer_rank or the is_company flag. Primary address, email, phone, and website transfer directly; parent/child company hierarchies map via parent_id in Odoo.

Intact iQ suppliers map to Odoo res.partner with supplier=True. Odoo does not distinguish supplier from customer at the table level — both use the same model — so FlitStack sets the appropriate flag during import. Supplier-specific fields like payment terms and supplier rank are set via the x_studio_ prefixed custom fields or the standard property fields.

Intact iQ contacts associated with companies map to Odoo res.partner records with parent_id pointing to the company partner. Function (job title) maps to function field in Odoo. Multiple contacts per company are supported natively in Odoo's partner model, unlike some ERPs that restrict N:1 relationships. Phone and email fields map directly.

Intact iQ products with variants decompose into Odoo's two-tier product model: product.template holds the shared product definition (name, categ_id, type, uom_id), while product.product holds the sellable/purchasable variants. Intact iQ product attributes map to Odoo attribute lines on the template. Products without variants create a single product.product with a one-to-one template relationship.

Intact iQ sales orders map to Odoo sale.order with partner_id resolved from the customer, date_order set to the original order date, and order lines containing product_id, product_uom_qty, price_unit, and discount. Odoo's onchange mechanism (now deprecated in newer versions) is handled by setting price_unit and taxes directly rather than relying on list_price lookup.

Intact iQ purchase orders map to Odoo purchase.order with partner_id resolved from the supplier, date_order from the source document, and order lines with product_id, product_qty, price_unit, and date_planned. Odoo purchase orders require a price_unit to be set explicitly — unlike sales orders, the default is not auto-filled from product standard_price.

Intact iQ customer invoices map to Odoo account.move with type='out_invoice'. The invoice number becomes the 'ref' field; the invoice date maps to invoice_date; line items use account_id resolved from the product's income account or the default sale account. Odoo requires journal_id on every move — FlitStack resolves this from the company's default sale journal based on the destination Odoo company.

Supplier invoices from Intact iQ become Odoo account.move with type='in_invoice'. Credit notes use type='in_refund'. Odoo's vendor bills require invoice_date, partner_id, and line entries with account_id pointing to expense accounts — FlitStack resolves these from the product's cost account or a fallback expense account configured in the migration plan.

Intact iQ stock movements map to Odoo stock.picking records with picking_type_id set to the appropriate warehouse operation (internal transfer, delivery, receipt). stock.move records within each picking carry product_id, product_uom_qty, location_id, and location_dest_id. Odoo's unit of measure must be resolved — FlitStack maps Intact iQ UoM names to Odoo uom.uom records using the product's uom_id and uom_po_id.

Intact iQ CRM leads map to Odoo crm.lead. name becomes the lead subject; partner_id is resolved by email match to res.partner; email_from and phone map directly; stage_id is resolved by matching Intact iQ status labels to Odoo stage names within the target pipeline. Odoo stage IDs are integer references — FlitStack creates a stage mapping table during the planning phase before any records are written.

Intact iQ extended properties that have no direct Odoo equivalent (e.g., customer credit rating, supplier tier classification, product tariff codes) are created as custom fields via Odoo's ir.model.fields API. FlitStack pre-creates these fields before data load, using field_description for the human-readable label and name matching the snake_case convention (x_intact_credit_rating, x_intact_supplier_tier). Existing custom fields in Odoo are detected and reused to avoid duplicates.

Intact iQ file attachments associated with customers, orders, or invoices are downloaded and re-uploaded to Odoo as ir.attachment records linked to the corresponding res.partner, sale.order, or account.move via res_model and res_id. FlitStack preserves the original filename, mimetype, and create_date. Large files (>25MB per Odoo default limit) are flagged for manual handling or chunked upload.