Migrate from ERPnext Enterprise - Bespoke to Odoo ERP

ERPnext Customer DocType maps to Odoo Contact (res.partner with customer_rank > 0). We preserve territory hierarchy, tax ID, payment terms, and credit limits as Contact fields. Dynamic Link relationships to address and contact sub-records are resolved during export to produce flat contact records with embedded address data compatible with Odoo's address model (street, city, country, zip). Customer type (Individual vs Company) maps to Odoo's is_company flag.

ERPnext Supplier DocType maps to Odoo Contact (res.partner with supplier_rank > 0). Supplier type, payment terms, and tax category custom fields carry forward as Contact fields. We separate supplier-specific fields from customer fields so that the same res.partner record can serve as both a customer and a supplier without duplication.

ERPnext Item DocType maps to Odoo Product (product.template with product.product variants). Item code becomes the Product's default_code; item name becomes the Product name. Item group hierarchy maps to Odoo product.category tree. Valuation method (FIFO, Moving Average, Standard), barcodes, UoM, and custom fields migrate as typed Product fields. Variant attributes from ERPnext's Item Variant Settings map to Odoo's product.attribute and product.template.attribute.line structure.

ERPNext BOMs are nested DocType trees with item ratios and operation routing. We map BOM headers to Odoo mrp.bom and child item lines to mrp.bom.line. Each child line must reference a destination product code that exists before the BOM import runs. Operation steps map to mrp.workcenter.line with workstation and cycle time. We validate the entire BOM tree and flag any orphan item codes (children with no matching Odoo product) before committing.

ERPnext Sales Order DocType maps to Odoo sale.order. Order lines (items, qty, rate, discount) migrate to sale.order.line with product_uom_qty and price_unit. Taxes and shipping details map to Odoo order-level fiscal fields and delivery method. We carry forward the link between Sales Order and Delivery Note (Odoo stock.picking) so that partial deliveries initiated in ERPnext can be completed in Odoo. Order status (Draft, Submitted, Cancelled) maps to Odoo state.

ERPnext Purchase Order maps to Odoo purchase.order with order lines mapping to purchase.order.line. Advance allocation records from ERPnext require separate handling as Odoo account.payment entries against the PO. The supplier address resolves to the vendor res.partner record created in the Supplier migration phase.

ERPNext uses voucher-based double-entry via GL Vouchers and Journal Entry DocTypes with debit and credit rows. These map to Odoo's account.move (move_type = entry). Account code mapping is the critical dependency: we validate that the destination Odoo chart of accounts has matching account numbers before importing journal entry rows. Multi-currency journal entries are supported but require exchange_rate precision mapping from ERPNext's exchange_gain_loss fields.

ERPNext Stock Ledger Entries (SLEs) link warehouse, item, and valuation rate. We migrate current open stock positions as Odoo stock.quant records (actual qty per product per location). Historical movement logs migrate as stock.move records linked to the originating document (Delivery Note, Purchase Receipt) only if those documents are also being migrated; standalone historical moves without a parent document migrate as ad-hoc stock moves with a reference note.

ERPNext Project DocType maps to Odoo project.project. The nested task hierarchy maps to project.task with parent_id resolution. Assignees, start and end dates, billing type, and hourly rate custom fields carry forward. We preserve the task tree depth and the project-task parent-child linkage in the task migration phase.

ERPNext custom field definitions stored in the Custom Field DocType are exported separately and applied on the Odoo destination before data import begins. Each custom field definition is translated to an Odoo ir.model.fields record with the correct field_type (varchar, int, float, date, select, check, etc.) and a matching field_name in the target model. Custom fields that reference deprecated or removed ERPNext modules (Social Media, Lending, e-commerce) are flagged and excluded from the migration plan so they do not create dead references in Odoo.

ERPNext Asset records include purchase details, depreciation schedule, and current value. These map to Odoo account.asset with asset.profile linking to the depreciation account from the chart of accounts mapping. Already-depreciated-to-zero assets are excluded unless the customer requests them for audit trail purposes. Depreciation lines migrate as account.move entries in the draft state for review before posting.

ERPNext Employee DocType maps to Odoo hr.employee with employment details, department, and reporting structure. Active employees and current compensation records migrate. Payroll history and historical salary records migrate only if selected during scoping; they are large-volume tables that many customers prefer to archive rather than import.