Migrate from Actindo Core1 to Odoo ERP

Actindo Customer records map to Odoo res.partner with partner_type set to 'contact' or 'invoice' based on Actindo's customer segment field. Address, contact, and segment fields migrate 1:1 where field types match. We flag any res.partner required-field gaps (country_id, lang) for Odoo-specific configuration before import.

Actindo Materials represent product catalog items with SKU, pricing, and attribute data. Materials map to Odoo product.template as the master record, with the Actindo SKU preserved in product.template.default_code. Stock levels per warehouse migrate to stock.quant records linked to the product.template. Variant pricing and channel-specific pricing stored in Actindo Materials require a pre-migration decision on whether to use Odoo's product.pricelist or product.template.list_price fields.

Actindo Articles extend Materials with channel-specific content, descriptions, and media managed via the PIM module. Articles have a parent-child relationship with Materials linked by SKU. We export Article content separately and reconstruct the linkage in Odoo by matching Article.parent_sku to Material.sku, then generating Odoo product.product variant records using the Article's channel-specific attributes as product.attribute.value entries.

Actindo Orders consolidate transactions from webshop, marketplace, POS, and B2B channels into a unified format. Each Order maps to an Odoo sale.order, with order lines migrated as sale.order.line records. The Actindo fulfillment_status field maps to Odoo's procurement.group and stock.picking state. Channel source (webshop, marketplace, POS, B2B) is preserved as a Char field on the sale.order for reporting segmentation.

Actindo Warehouse entities define stock locations with bin-level structure. Each Actindo Warehouse maps to an Odoo stock.warehouse record. Actindo's bin-level assignments migrate to stock.location records under the warehouse's view_location_id hierarchy. Multi-warehouse routing configurations from Actindo require rebuild in Odoo using stock.route and stock.rule records post-migration.

Actindo Purchase Orders track procurement from vendors, linked to Materials and inbound receipts. PO headers map to Odoo purchase.order, line items to purchase.order.line, and vendor-specific reference numbers preserved in purchase.order.partner_ref. Inbound receipts map to stock.picking with picking_type_id set to 'incoming'. We flag any vendor-specific reference numbers for manual verification against Odoo's partner_po_shipping_policy.

Actindo Invoice records link to Orders and track financial postings across accounting integrations. Invoices map to Odoo account.move with move_type set to 'out_invoice' or 'in_invoice' based on Actindo's invoice_direction field. Tax codes and payment status normalize to Odoo's account.tax and account.payment.record models. We apply the customer's existing Odoo chart of accounts structure before invoice import to ensure proper account mapping.

Actindo Vendor master records store supplier data, payment terms, and lead times. Vendors map to Odoo res.partner with supplier_rank = 1 and the appropriate property_supplier_payment_term_id set from Actindo's payment_terms field. Contact information migrates as res.partner child records. Vendor-specific PO history links via purchase.order.partner_id resolution at migration time.

Actindo POS data includes transaction records synced from Venduo POS. POS transactions migrate as Odoo sale.order records with a pos_source Char field set to the original store identifier. Register reconciliation data does not migrate as a carry-forward record; we deliver a POS register closure template for the customer's admin to initialize Odoo PoS session balances at go-live.

Actindo Workflow Engine definitions encode business process logic as low-code visual flows that are not natively exportable in a standard schema. We export workflow JSON configurations and rule descriptions, then build a written rule-mapping matrix recommending Odoo Automated Actions or Server Actions equivalents. Complex conditional routing requires manual translation by the customer's Odoo admin or implementation partner. This is a documentation deliverable, not a code migration.