Migrate from Cetec ERP to Odoo CRM

Cetec Customer records map to Odoo res.partner, with the distinction between company-type partners (commercial contacts with children) and individual contacts preserved via the Odoo is_company flag. We map the Cetec customer number to the Odoo partner ref field as the dedupe key. Internal customer records (the company itself) that were flagged as non-editable in Cetec after order linking are migrated as inactive or archived partners in Odoo to prevent unintended edits post-migration.

Cetec PQuote records map to Odoo sale.order in quotation state. Quote approval thresholds (dollar-value, PPV, LBV) from Cetec are stored as custom fields on the Odoo quotation record because Odoo Quotation does not have native multi-threshold approval logic. We map the approval status to a custom stage field and document the threshold values so the customer can configure Odoo Approval Rules post-migration.

Cetec Sales Orders map to confirmed Odoo sale.order records with line items migrated as sale.order.line. The dual fulfillment pattern (build-to-stock and build-and-ship on the same part as separate line items) is parsed from the Cetec export and reconstructed as two line items on the same Odoo order with a custom fulfillment_type flag on each line.

Cetec Purchase Orders map to Odoo purchase.order. PO line items map to purchase.order.line with vendor pricing carried from the Cetec vendor pricing rule table. Drop-ship PO patterns with automatic PO generation are flagged as configuration notes because they may create linked records in Odoo's vendor inventory model.

Cetec Part records map to Odoo product.product (the variant model) and product.template (the product definition). The Cetec part number becomes the Odoo default_code. Units of measure from Cetec map to Odoo's uom.uom model, with the Odoo uom_category preserved so that the purchase, sale, and inventory UoMs align. Vendor pricing rules attach to the product.supplierinfo table.

Multi-level Cetec BOMs with materials, work instructions, and sub-assemblies map to Odoo mrp.bom. We flatten or nest the BOM structure depending on whether the Odoo target instance has Odoo Manufacturing installed. Phantom BOMs in Cetec (for assemblies treated as single part at the top level) map to Odoo phantom type on the BOM line.

Cetec Work Orders map to Odoo mrp.production only if the customer includes Odoo Manufacturing in the destination stack. Work order operation sequences map to Odoo workorder records with duration and workstation dependencies preserved. Open work orders migrate as confirmed Manufacturing Orders; completed work orders migrate as finished Manufacturing Orders with the production date set to the original completion date.

Odoo CRM does not include a native quality module; Quality Points, Quality Alerts, and Inspection templates require the Odoo Quality app (part of Odoo Manufacturing suite). We migrate Inspection records as structured custom objects with inspection date, outcome (pass/fail/conditional), and part reference, and we deliver a written recommendation for which Odoo Quality app configuration to enable post-migration.

Cetec NCRs map to Odoo quality.alert if the Odoo Quality app is installed in the destination instance. NCR status (open, under review, closed), disposition actions, and root-cause analysis fields migrate to quality.alert description and custom fields. If Odoo Quality is not installed, NCR records are migrated as Notes or Tasks attached to the related product or partner record.

Cetec Quality Codes are configured system-wide for inspections, NCRs, and receiving. We export the code tables and map them to Odoo quality.alert.category or product.category tags, flagging any code categories that have no Odoo equivalent. The customer configures the Odoo quality.category after migration.

Cetec Document Management files attached to parts, BOMs, work orders, and quality records export as binary files. We map them to Odoo ir.attachment records linked to the corresponding product.product, mrp.bom, or mrp.production via res_id and res_model. Original filenames and revision numbers are preserved in the attachment name and description fields.

Cetec Users and role definitions map to Odoo res.users with access rights configured per the Odoo permission model. The $25/user/month shop floor role in Cetec maps to an Odoo internal user with restricted access to the sale and crm apps, avoiding full-user pricing for shop floor staff. We map by permission set rather than by role name since naming conventions differ between platforms.

If the destination Odoo instance includes the Accounting app, the Cetec Chart of Accounts migrates to Odoo account.account with account codes, types, and department/cost center assignments preserved. Active/inactive status and any intercompany account mappings carry through. If Odoo CRM is deployed without Accounting, the Chart of Accounts is exported as a reconciliation reference document for the customer's Odoo admin to configure after enabling the Accounting app.