Migrate from Kladana ERP to Odoo ERP

Kladana Items with variants, bundles, serial numbers, batches, expiry dates, and barcode associations map to Odoo Product Template (the canonical product) with Product Variant records for each SKU combination. The Kladana cost price maps to Odoo's standard cost field; sell price maps to list_price. Reorder points and route configurations (make-to-order, buy-to-order) migrate to Odoo's route definitions on the product form. Serial number and batch histories map to Odoo's lots/serial numbers with the original manufacture and expiry dates preserved as lot_date and use_date fields.

Kladana Counterparties with type=Customer map to Odoo Contact (with is_customer=True) and optionally to a parent Company record. Counterparties with type=Supplier map to Odoo Contact (with is_supplier=True). Counterparties with both customer and supplier status generate two Contact records linked to a shared Company. The Kladana counterparty ID is preserved in a custom field for dedupe and audit. Transaction history (outstanding invoices, order history) links to the Contact record via the Odoo account.move and sale.order references.

Kladana Sales Orders in draft, confirmed, reserved, fulfilled, and invoiced states map to Odoo Sale Order records with the corresponding state preserved. Order headers, pricing, discounts, and shipping address migrate directly. Fulfillment status maps to Odoo's delivery count and delivered quantity fields. If the Kladana order references a shipment record, we create a corresponding Odoo stock.picking. Open orders (not fully invoiced) are flagged for priority migration so that revenue pipeline continuity is maintained at cutover.

Kladana Purchase Orders map to Odoo Purchase Order records. Supplier reference, expected delivery date, and receipt status carry forward. Pending inbound receipts map to Odoo RFQs or confirmed POs with the appropriate state. Purchase Order line items reference the mapped Product Template and Vendor Pricelist entries created during the product migration phase.

Kladana's multi-warehouse structure with bin storage maps to Odoo's Location hierarchy (Physical Locations under Warehouse). Each Kladana warehouse becomes an Odoo stock.warehouse with child locations for each bin. Per-warehouse stock-on-hand quantities, reserved quantities, and pending inbound and outbound moves map to Odoo stock.quant records linked to the correct location. In-transit movements become Odoo stock.picking records with the in-transit location as source or destination.

Kladana BOMs (multi-level and multi-version) require pre-migration version selection. Odoo supports only a single active BOM per product variant, so we export all BOM versions during scoping and present the customer with a version selection worksheet. We recommend the most recently used or highest-revision BOM as canonical. Multi-level subassemblies map to Odoo nested BOMs via the bom_line and routing_workcenter_link tables. After version resolution, the BOM structure migrates as a single Odoo mrp.bom record with all components and operations.

Kladana Production Orders referencing a BOM and routing map to Odoo mrp.production records. Planned quantities, actual output, material consumption, labour hours, and variance data migrate to the Odoo production record's move_raw_ids (component consumption), workorder_ids (operation tracking), and the production record's state field. Open production orders in-progress are migrated with their current state preserved so that production continuity is maintained. Completed production orders with variance data are migrated as historical records for cost analysis.

Kladana Sales Invoices linked to orders and counterparties map to Odoo account.move records with move_type=out_invoice. Invoice headers, line items, tax codes, payment status, and outstanding balances migrate. Fully paid invoices are migrated as historical locked records. Partially paid or unpaid invoices carry forward their residual amounts as Odoo move lines with the appropriate account receivable mapping. Odoo's invoice PDF attachments migrate as Odoo ir.attachment records linked to the move.

Kladana Purchase Invoices map to Odoo account.move records with move_type=in_invoice or move_type=in_refund. Vendor references, line items, tax codes, and payment status migrate. Outstanding amounts map to Odoo vendor bill lines with the appropriate account payable reference. Reconciliation with related Purchase Orders is preserved where the original Kladana linkage exists.

Kladana Tasks and Workflow configurations are proprietary rule sets that do not map to Odoo's project-task model as code. We export task assignments, statuses, and linked objects as Odoo project.task records with the task name, description, assigned user (via email match), and deadline preserved. Kladana workflow rules are documented in a written inventory that maps each workflow's trigger, conditions, and actions to Odoo Automated Actions (ir.actions.server) and Studio workflow alternatives. The customer's Odoo administrator rebuilds these as Odoo workflows post-migration.

Kladana custom field definitions and their values migrate as Odoo custom fields created via Settings or XML definition. We create the field in Odoo with a matching type (char, integer, float, selection, many2one, etc.) on the corresponding model before data import begins. Custom field values on Items, Counterparties, Orders, and other objects populate the new Odoo fields during the data migration phase. Field labels and help text are preserved from the Kladana custom field metadata.

Kladana CRM records (contact interactions, activity notes, custom offers) linked to counterparties map to Odoo crm.lead records if the customer activates the CRM app, or to note records (mail.message) if CRM is not part of the destination scope. Sales history and custom offer data migrate to the contact's chatter (message_ids) or to a dedicated opportunity record. The customer confirms CRM app activation during scoping.