Migrate from Total Control Pro to Odoo CRM

Total Control Pro Customer records map to Odoo res.partner with type='contact' and customer_rank set to 1. Customer name becomes partner name, contact details map to street, city, email, and phone fields, and account terms map to property_payment_term_id. We deduplicate by email and flag records with duplicate email addresses for manual resolution before insert. Customer country and state map to the Odoo res.country and res.country.state lookup tables by code match.

Total Control Pro Supplier records map to Odoo res.partner with type='contact' and supplier_rank set to 1. Supplier part supply links and lead times map to seller_ids on product.template for purchase pricing, and to property_supplier_payment_term_id on the supplier partner record. Suppliers with both customer and supplier roles in Total Control Pro receive a single res.partner with both customer_rank and supplier_rank set to 1.

Total Control Pro Product definitions (part numbers, descriptions, unit of measure) map to Odoo product.template. The part number becomes default_code, description becomes name and description_sale, and the unit of measure maps to uom_id and uom_po_id by name match against the Odoo uom.uom table. Products marked as manufactured in Total Control Pro will also have a corresponding mrp.bom if Odoo MRP is in scope.

Bills of Materials map to Odoo mrp.bom only if the Odoo MRP module is licensed and in scope. Each BOM revision in Total Control Pro is evaluated for active status at migration cutoff; the most recent approved revision per product becomes the active Odoo BOM. Multi-level BOMs are expanded and components mapped to product.template by part number match. If Odoo MRP is not licensed, BOMs are delivered as a structured CSV with component quantities, revision numbers, and product links for post-migration import.

Work Orders map to Odoo mrp.workorder only if the MRP module is active. If Odoo CRM-only is the destination, Work Orders are delivered as a structured CSV with work order number, product, operation sequence, status, assigned operations, and timestamps, and any required manufacturing context is stored as custom fields on the nearest Odoo CRM record (Customer or Product). Work Order status maps to the Odoo done, cancelled, and in_progress states.

Quality Check results from Total Control Pro associate to parent Work Orders or Production Runs. If Odoo MRP is in scope, inspection results and non-conformance records map to mrp.workorder quality notes fields or to a dedicated quality.check model if the quality_mrp module is active. If MRP is out of scope, Quality Check data attaches to the corresponding res.partner or product.template via custom fields with a qc_ prefix.

Current stock levels, bin locations, and lot numbers from Total Control Pro map to Odoo stock.quant as a snapshot at migration cutoff. Live inventory movements during migration are queued in a staging table and replayed post-cutover to avoid discrepancy. Bin locations map to stock.location by name match against the Odoo location hierarchy. Lot and serial numbers map to stock.production.lot if lot tracking is enabled on the product.

Production schedules including operation sequences and due dates map to Odoo mrp.production (if MRP is active) or to project.project as manufacturing-themed projects (if CRM-only). Constraint flags and priority overrides migrate as project priority fields or custom fields. Scheduling data that requires Odoo MRP's finite capacity scheduling is out of scope unless MRP is licensed.

The Manufacturing Intelligence Module stores OEE, cycle time, and scrap rates as time-series data in a proprietary format not exposed in standard exports. We request a targeted MIM module export scoped to the customer's date range, normalize rows into a structured CSV with timestamp, metric name, metric value, and associated product or work order reference, and deliver it alongside the transactional migration. Odoo does not have a native time-series KPI store in the CRM module; the customer ingests the CSV into Odoo reporting or an external BI tool.

Total Control Pro user-defined fields added during implementation are enumerated during the discovery call. For Odoo, custom fields are created in Settings > Technical > User-defined Fields with the appropriate field type (char, float, integer, date, selection, etc.) and model targeting res.partner, product.template, or crm.lead depending on the field's parent object. If Odoo MRP is in scope, custom fields on Work Orders map to mrp.workorder. Odoo custom fields are tied to the database and require Odoo version compatibility verification; we confirm the Odoo major version before deployment.

Document attachments (drawings, SOPs, inspection images) stored in Total Control Pro's file store do not have a documented export endpoint. We flag these for manual transfer during a documented cutover window and advise using Odoo's document management module (documents module with attachments on partners, products, or projects) as the destination store. The customer receives a file manifest listing attachment names, associated records, and recommended Odoo folder structure.

Total Control Pro owner assignments on Work Orders, Quality Checks, and customer records map to Odoo res.users by email match. Any Total Control Pro owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner IDs on migrated records are set after user provisioning is confirmed.