Migrate from Total ETO to Odoo ERP

Total ETO Projects (the top-level container for all ETO activity from quote through delivery) map to Odoo Project. We create a corresponding analytic account during migration for job costing and WIP visibility. Project owner, status stages, and milestone dates migrate as project metadata. If Odoo's Engineer-to-Order approach is chosen during scoping, the Project may also carry linked Manufacturing Orders and BOM references.

Total ETO BOMs are dynamic, multi-level, versioned structures that evolve throughout the build phase. This is the most complex object to migrate. We map each BOM revision as a distinct BoM version, preserving the multi-level component hierarchy with parent-component relationships. The decision between MRP-level BoM (for high-volume production scenarios) and Project-level BoM (for ETO project tracking) is made during scoping and documented with the full rationale before migration begins. Revision dates and engineering-change context migrate as BoM notes or custom fields.

Total ETO Parts map to Odoo Products configured as storable items. Part master attributes (description, unit of measure, cost, supplier link) migrate to the corresponding Odoo product fields. Part usage history across projects migrates as a linked product log or note. Supplier part numbers and preferred-vendor flags map to the Odoo product vendor list.

Total ETO Customer records (contact details, address, account balance) map to Odoo Contacts with the customer flag enabled. Open AR balances migrate as of the migration date. Customer-specific pricing rules from Total ETO map to Odoo product pricelists attached to the contact.

Total ETO Vendor records map to Odoo Contacts with the supplier flag enabled, preserving purchasing terms and contact information. Active RFQs and open POs reference vendor contacts, so vendor import must precede PO import.

Open POs and RFQs represent live procurement commitments. These cannot be imported before the Part master and vendor contacts are established at the destination, or foreign-key violations will block the import. We flag orphaned PO lines that reference parts not yet in the system and handle them in a separate reconciliation queue. Active PO and RFQ status migrates; closed or historical POs migrate as closed records with full line-item history.

Total ETO Work Orders link to Projects and BOMs, tracking manufacturing operations by shop-floor routing. We map Work Orders to Odoo Manufacturing Orders linked to the parent Project via analytic account. Operation sequencing and routing information migrate as MO operation lines in the correct order.

Total ETO NCRs reference specific parts, inspections, and quality issues from the shop floor, engineering, or procurement. We map NCRs to Odoo Quality Alerts, preserving the association to the relevant product, work order, and project for full traceability. NCR disposition and root-cause fields migrate to the Quality Alert description and custom fields.

Inspections record quality checks against parts and link to the inspector. We import inspection results as Odoo Quality Check records tied to the relevant Manufacturing Order and product. Pass/fail status, measured values, and inspector details migrate as Quality Check fields.

On-hand quantities tracked by location in Total ETO map to Odoo Quants and stock locations. Project reservations in Total ETO map to Odoo move reservations with scheduled dates. Any negative or reserved quantities that cannot be resolved at migration time are flagged for the customer's operations team before cutover.

Total ETO Employee records (labor class, department, time-entry data) map to Odoo HR Employee records. Employee provisioning in Odoo depends on the customer's HR module configuration; we import the employee master and map time-entry logs to the corresponding project and manufacturing order at the destination.

Total ETO stores documents linked to Projects, Parts, and quality records. We extract document references and file paths and map them to Odoo Attachments linked to the corresponding Project, Product, or Manufacturing Order. Actual file migration depends on the destination's document management capabilities and file storage configuration.