Migrate from ECOUNT ERP to Odoo ERP

ECOUNT Items (inventory masters with codes, descriptions, units, cost, price, and BOM links) map to Odoo Product records. If ECOUNT Items carry size, color, or dimension variants, we split them into Odoo Product Template with Product Variants linked via attribute lines. Standard cost and list price from ECOUNT transfer to Odoo's standard_price and list_price fields. The ECOUNT item_code becomes Product's default_code (SKU). Warehouse quantity on hand at migration date becomes Odoo's on-hand quantity via a stock.quant import after the Product record is created.

ECOUNT BOMs with multiple sub-material links and process-level inventory adjustments map to Odoo MRP BOM records. Each ECOUNT BOM component becomes an mrp.bom.line entry referencing the sub-product as a product_id with product_uom_id and product_qty. ECOUNT process steps that perform inventory adjustments map to Odoo mrp.routing entries linked to Work Centers, which carry time efficiency, blocked quantity, and costing information. We flag any ECOUNT BOM that references a component not yet imported as a Product and hold it in a dependency queue until the component record exists.

ECOUNT Customer master records (contact details, payment terms, credit limits, outstanding balances) map to Odoo res.partner records with the customer flag set to True. Payment terms from ECOUNT map to Odoo account.payment.term entries created during schema setup. Outstanding balances at migration date load as Odoo account.move (invoice) records in Draft state so that the AR aging report reflects pre-migration open items. ECOUNT's auto-retrieved balance fields are preserved as Odoo custom fields on the partner for reconciliation.

ECOUNT Vendor records mirror the Customer structure with supplier-specific fields. They map to Odoo res.partner with supplier flag True. Vendor payment terms and the supplier info (lead times, minimal quantity) from ECOUNT transfer to the Odoo product.supplierinfo table linked to the vendor partner, enabling Odoo's Purchase module to suggest the correct supplier for reordering.

ECOUNT Sales Slips (the transactional document for recording revenue, including line items, quantities, prices, and tax codes) map to Odoo sale.order and sale.order.line records. We extract them by period from the ECOUNT report download, cleaning merged-cell artifacts from the Excel export before mapping. The ECOUNT document number becomes Odoo's name field. Tax codes from ECOUNT map to Odoo account.tax records created during the tax mapping phase. Historical sales orders load in 'sale' state so they appear in reporting but are locked from editing.

ECOUNT Purchase Slips (incoming inventory and expenses, including incidental cost allocations) map to Odoo purchase.order and purchase.order.line. Both slip headers and incidental cost allocations migrate. Landed costs from ECOUNT incidental expense allocations are represented as Odoo landed cost records attached to stock.picking entries, preserving the total cost of goods received.

ECOUNT's accounting structure uses accounts, departments, and cost centers with customizable account codes. We map each ECOUNT account to an Odoo account.account record with the matching code, name, account_type (asset, liability, equity, revenue, expense), and an Odoo recon attribute where appropriate. ECOUNT department-level restrictions map to Odoo analytic account entries for cost-center reporting. The customer chooses whether to activate Odoo's analytic accounting module during schema design.

ECOUNT vouchers and export invoices generated from sales slips map to Odoo account.move records in the 'posted' state for historical accuracy. Each invoice line maps to account.move.line with debit and credit entries satisfying Odoo's double-entry accounting constraints. L/C issuing bank and shipper details from ECOUNT invoice exports become Odoo custom fields on the account.move for audit traceability. Customer and vendor invoice types are differentiated by the move_type field.

ECOUNT Employee data including attendance, compensation, and payroll history maps to Odoo hr.employee and hr.contract. Effective-dated compensation changes are loaded as hr.contract records with their start and end dates, preserving the historical compensation record. Attendance history from ECOUNT maps to Odoo hr.attendance if Odoo HR is activated. We flag payroll processing as a separate scope item because Odoo's payroll module is country-specific and may require an Odoo-validated payroll provider or a separate HR system depending on the customer's jurisdiction.

ECOUNT allows customers to add, rename, or delete input fields per screen with calculation formulas, stored in screen configuration rather than a published schema. We request the customer's upload templates or screen exports during discovery to identify all active column names and their data types. Each discovered custom field is created as an Odoo custom field (ir.model.fields with custom=True) on the appropriate Odoo model (res.partner, product.product, etc.) before any data import. Calculation formulas in ECOUNT do not migrate; we document them as a separate list for the customer's Odoo developer to implement in Python or Odoo Studio.

File attachments linked to ECOUNT slips and records are extracted from ECOUNT's file storage during the export phase and re-linked in Odoo via ir.attachment records pointing to the migrated record's res_model and res_id. We resolve the attachment-to-record linkage by matching the ECOUNT record identifier to the Odoo record ID created during migration. Any ECOUNT attachment without a resolvable parent record is held in a catch-all 'ecount_orphaned_attachments' folder for manual re-association.