Migrate from Kinetic to Odoo ERP

Kinetic Customer records map to Odoo Partner with partner_type set to 'customer'. Address, payment terms, and credit limits transfer to the corresponding Odoo Partner fields. We validate that each Customer's payment terms code exists in Odoo before import so that the sale order terms reference resolves correctly at load time.

Kinetic Vendor records map to Odoo Partner with partner_type set to 'supplier'. Multi-address vendor setups transfer as separate Partner addresses linked to the same parent Vendor partner. We preserve PO approval workflow assignments as Odoo purchase order approval rules configured post-migration.

Kinetic Part records map to Odoo Product. PartNum becomes the product's default_code; TypeCode determines the product type (stockable, consumable, service). UOM codes from Kinetic's unit-of-measure definitions require validation against Odoo's UoM model during scoping because Kinetic UOM sets frequently include non-standard codes that must be created in Odoo before product import can begin.

Kinetic BOM and Routing are separate objects. Odoo nests routing operations as lines inside a single BoM record. We split each Kinetic BOM-Routing pair during the transform phase: the BOM header becomes the Odoo BoM record, and each Kinetic Routing Operation becomes an Odoo BoM Operation line with Work Center reference, sequence, and cycle time. BOM revision chains from Kinetic (including revision dates, approval states, and effective dates) map to Odoo's active/engineering BoM structure with a revision comment field preserved for audit.

Kinetic Routings reference Operations, Work Centers, and Sequences. Each Kinetic Operation step becomes an Odoo BoM Operation line linked to a mapped Odoo Work Center. We validate Work Center IDs against Kinetic before migration; invalid or missing Work Center references are a primary load failure cause. Where Kinetic uses step-level scheduling dependencies, Odoo models these as operation sequence ordering within the BoM with work center capacity constraints.

Kinetic Sales Order headers map to Odoo Sale Order. Order type, terms, and ship-from Site must exist in Odoo before order lines can be added. We migrate order headers first, validate Site and payment-term existence, then load lines in a second phase. Order status (booked, partial, shipped) transfers as the Odoo sale order state field.

Kinetic Sales Order lines require the parent order header to exist in Odoo first. We sequence the load so that all order headers complete before any order lines begin. Line-level pricing, quantity, and promised dates migrate; part number references resolve to the corresponding Odoo Product record.

Kinetic PO headers and lines map to Odoo Purchase Order. Vendor and Site records must exist in Odoo before PO lines can import. We handle PO approval workflow state by migrating the current approval status and flagging any PO that requires re-approval under Odoo's purchase approval rules post-migration.

Kinetic Work Orders depend on Part, BoM, and Routing records already existing in Odoo. We sequence Work Order migration after all product, BoM, and routing data has loaded successfully. JobNum generation rules vary by site configuration; we map source JobNum patterns to Odoo's manufacturing order naming sequence or preserve original IDs where the customer requires them.

Chart of Accounts must exist in Odoo before any transactional records load. Kinetic COA structures frequently use segment-based account numbering (company, division, department) that differs from Odoo's flat account code model. We design the account mapping during scoping: natural accounts map directly; segmented accounts map to Odoo account groups or analytic account tags. The customer approves the COA structure before migration of any transactional data begins.

Kinetic Site records and their associated Warehouses transfer to Odoo Warehouse records. Multi-site configurations map to separate Odoo Warehouses with inter-warehouse transfer rules. We preserve site-specific parameters like default warehouse, shipping calendars, and any inter-site transfer configurations as Odoo warehouse rules.

Kinetic Employee records map to Odoo Employee. User and owner assignments on records require the Employee to exist in Odoo first with a linked User for record ownership. We handle effective-dated employee status changes and preserve department and labor class assignments as Odoo HR department and job title mappings.