Migrate from ERPNext to Odoo ERP

ERPNext Customer DocType maps to Odoo res.partner with the customer boolean set to True. We use the customer_name or cust_name field as the partner display name and map customer_name, customer_group, territory, and primary contact details (email, phone, mobile) to their Odoo equivalents. Address records (ERPNext Address DocType) map to res.partner with address_type (invoice, delivery) via the address fields in Odoo's partner model.

ERPNext Supplier DocType maps to Odoo res.partner with the supplier boolean set to True. ERPNext stores supplier-specific fields like default_currency, supplier_type, and country. We map these to Odoo partner fields and populate the seller_ids on the mapped product records after products are loaded so that purchase pricing links correctly. A supplier record that also has customer records in ERPNext creates a single res.partner with both flags set True.

ERPNext Item maps to Odoo product.template as the definition record with product.product as the variant record (single variant for items without option-based variants). We map item_name to name, item_code to default_code (used as SKU), item_group to product_category, and stock_uom to the Odoo uom_id. Valuation method (FIFO vs Moving Average) maps to Odoo's valuation_type on the product category. Barcodes map to product.barcode on product.product. Item description (HTML) maps to description_sale for the sales description and description_purchase for procurement.

ERPNext BOMs with multi-level nesting and operation routing require flattening during extraction and reconstruction in Odoo's MRP module. We export the full BOM tree, resolve ERPNext workstations to Odoo mrp.workcenter records (with capacity, time efficiency, and cost per hour), and build mrp.routing as the operation sequence. The routing is then linked to mrp.bom via the bom_id on each routing operation. If the destination Odoo instance does not include the MRP module, we present three options: install MRP (recommended for manufacturing), flatten to product variants with bill-of-materials as product description text, or maintain BOM detail in a linked product attribute table.

ERPNext warehouse structure (including bin-level data via the Bin DocType) maps to Odoo's stock.warehouse and stock.location hierarchy (View, Internal Location, Partner Location, Virtual Location). Open stock ledger entries map to stock.quant with reserved_qty and available_qty resolved per warehouse. We flag whether ERPNext uses perpetual or periodic inventory and configure Odoo's inventory valuation (manual or automated) to match, so that inventory valuation reports are consistent post-migration.

ERPNext Sales Order with line items, taxes, discounts, and delivery schedules maps to Odoo sale.order and sale.order.line. We extract the full order header (customer reference, currency, payment terms) and all child table rows (packed items, product bundle components) as separate relational CSVs so that the parent-child relationship is preserved at import time. Delivery schedule dates map to sale.order.line.commitment_date. Order status (Draft, Submitted, Cancelled, Closed) maps to Odoo state with ERPNext's workflow states reconciled against Odoo's sale order workflow.

ERPNext Purchase Order maps to Odoo purchase.order using the same line-item extraction approach as Sales Order. We map supplier from ERPNext's supplier field to Odoo's partner_id on purchase.order, line items to purchase.order.line with product, quantity, and price resolved against the product and seller records loaded earlier. Taxes, discounts, and delivery dates transfer similarly. Received and billed quantities in ERPNext map to Odoo's qty_received and invoice_lines for accurate order-to-invoice tracking.

ERPNext Sales Invoice maps to Odoo account.move (type = out_invoice or out_refund). ERPNext v14+ decouples payments into a separate Payment Entry DocType linked via the Payment Ledger, meaning an invoice with full payment still shows as open unless we query the Payment Ledger. We run the payment resolution query during extraction, set the Odoo account.move payment_state to matched when full settlement is confirmed, and create account.payment records for partial or full payments. Purchase invoices follow the same pattern with in_invoice and in_refund types. Chart of accounts mapping is validated against the customer's Odoo chart of accounts template before any invoice loads.

ERPNext Project DocType with nested Tasks, assignees, time logs, and milestone dates maps to Odoo project.project and project.task. ERPNext task hierarchy (parent_task field) maps to Odoo's parent_id on task. Time logs map to account.analytic.line linked to the project if Odoo Accounting is active. ERPNext project_type (External vs Internal) maps to Odoo's privacy_visibility. Task status and ERPNext's workflow states map to Odoo's stage_id on task.

ERPNext Employee master data (department, designation, date of joining, salary structure) plus attendance and leave records are stored across multiple DocTypes. We consolidate employee profile fields into hr.employee, attendance records into hr.attendance (check_in and check_out per day), and leave applications into hr.leave. ERPNext salary structure assignments map to hr.contract records in Odoo HR if the payroll module is active. If the destination Odoo instance does not include HR Payroll, we preserve salary structure assignments as custom fields on hr.employee for reference.

ERPNext custom fields stored in the Custom Field DocType (which references parent DocType, defines fieldtype, options, and mandatory flags) must be inventoried separately and recreated in Odoo before data import. We export the full custom field registry during discovery and create Odoo custom fields via Studio (for simpler fieldtypes) or via XML data file for complex fieldtypes, validation rules, and conditional mandatory settings. Data cannot import into non-existent custom fields, so custom field creation must complete before the main data load phase.