Migrate from Herbst Insight ERP to Odoo ERP

Herbst Customers export as a single master record containing billing address, shipping address, and contact details. We map directly to Odoo res.partner records where partner_id.partner_type = 'customer'. Credit limits from Herbst become custom fields on res.partner; payment terms map to Odoo's account_payment_term lookup. Any customer with a Herbst default_price_list_id becomes an Odoo pricelist record linked to the partner before import.

Herbst Suppliers export with address, banking details, and purchasing terms. We map to Odoo res.partner records where partner_id.partner_type = 'supplier'. Herbst vendor hierarchy (parent vendor, sub-vendor) maps to Odoo's parent_id on res.partner. Open Purchase Orders linked to the supplier are reconciled separately using the Purchase Order mapping. Supplier banking details migrate to Odoo's res.partner.bank_ids with appropriate account type flags.

Herbst Items carry pricing, cost, stock-control flags, and BOM data for manufacturing variants. We map primary SKU to Odoo product_product.default_code as the dedupe key. Herbst item type (stockable, consumable, service) maps to Odoo product_product.type. Variant attributes from Herbst BOMs map to Odoo product_template.attribute_line_ids with corresponding product_product variants created at import time. Cost price from Herbst becomes product_product.standard_price.

Herbst COA exports with account codes, account names, and posting-level flags. We preserve the full account code structure (numeric, alphanumeric) from Herbst as Odoo account_account.code, because code is the Odoo account lookup key used on journal entries. Tax codes from Herbst become Odoo account_tax records linked to the appropriate sales or purchase account. This entity loads first before any journal entries or AP/AR balances can be posted.

Open payables migrate as Odoo account_move records with move_type = 'in_invoice' and state = 'draft' (or 'posted' if the balance has been cleared in Herbst). Herbst's AP header carries the supplier reference, invoice date, due date, and total amount; line items carry account code, description, and debit amount. We resolve each Herbst supplier_id to a res.partner vendor record and each Herbst account code to an Odoo account_account.code before loading. Unmatched AP lines are flagged to a reconciliation queue.

Open receivables migrate as Odoo account_move records with move_type = 'out_invoice' and state = 'draft' or 'posted' depending on Herbst payment status. Herbst's AR header carries the customer reference, invoice date, due date, and open balance. We resolve Herbst customer_id to res.partner.customer_rank = 1 and Herbst account codes to Odoo account_account records. Orphaned lines (no matching partner or account) are escalated before load.

Herbst Sales Orders export with header status, line items, and fulfillment links. Status values from Herbst (Quoted, Confirmed, Despatched, Invoiced, Void) map to Odoo sale_order.state values. Line items carry product_id, quantity, and unit_price referencing the product mapping. Fulfillment references from Herbst become Odoo stock_picking records linked to the sale_order. Voided or partially voided orders are imported as draft records with a status flag for customer review.

Herbst Purchase Orders migrate to Odoo purchase_order with header status mapped to state values. Line items carry product_id, quantity, and purchase_price referencing the Items mapping. Herbst vendor_id resolves to res.partner.supplier_rank = 1. Open PO references attached to a supplier account are preserved as Odoo purchase_order.name for reconciliation against received goods and vendor invoices.

Herbst stock records include warehouse location, batch, and serial number fields that vary by warehouse configuration. We create Odoo stock_location records per Herbst warehouse site, then map Herbst stock_on_hand quantities to Odoo stock_quant records with the resolved location_id and product_id. Multi-warehouse setups in Herbst generate multiple Odoo stock_location parent records. Bin-level data migrates to stock_quant with dedicated lot_id or lot_name references. Validation against Odoo's stock valuation method occurs before final load.

Herbst time entries and attendance logs export as dated records with employee_id, clock_in, clock_out, and attendance_type fields. We map to Odoo hr_attendance records for clock-in/out events and to hr_timesheet_sheet.sheet_line records for timesheet data linked to project tasks. Integration dependencies on the Herbst Time and Attendance module are flagged; Odoo's native Attendance app may require configuration to match the Herbst rule set.

Herbst manufacturing data (production orders, Bills of Materials, routing information) maps to Odoo mrp_production and mrp_bom records where the Odoo Manufacturing app is activated. Herbst BOM components map to mrp_bom_line records with component product_id and quantity_bom resolved against the Items mapping. Custom production workflows from Herbst are catalogued as configuration notes for Odoo manufacturing route setup.

Binary document storage (invoice PDFs, images, uploaded files) is not accessible via Herbst's standard export tools and is marked as not migratable. We export document metadata (filename, file type, linked module, record reference) into an Odoo ir_attachment inventory, and the file transfer is handled separately by the customer via the Herbst Web Portal download or direct server access. Note attachments that are text-based may be extracted as Odoo mail.message records.