Skip to content
Get a quote

ERPNext to Odoo ERP migration

We migrate Customers, Suppliers, Items, BOMs, Stock, Sales Orders, Purchase Orders, Invoices, Projects, and Employees from ERPNext into Odoo ERP with DocType-to-model translation resolved upfront, BOM routing reconstructed for Odoo's MRP module, and the ERPNext v14+ Payment Ledger resolved before any invoice lands in Odoo.

Short answer

FlitStack AI migrates res.partners, product.template + product.products, mrp.bom + mrp.routing + mrp.workcenters, stock.warehouse + stock.location + stock.quants and sale.orders from ERPNext to Odoo ERP, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

By

Source ERPNext
DestinationOdoo ERP
res.partnerproduct.template + product.productmrp.bom + mrp.routing + mrp.workcenterstock.warehouse + stock.location + stock.quantsale.order
Mapped field by field · sample run · one-click rollback

What moves from ERPNext to Odoo ERP?

Moving from ERPNext to Odoo ERP is a schema translation, not a record copy.

Read the full summary

ERPNext uses a document-based DocType architecture stored in MariaDB where every entity (Customer, Item, Sales Order, Project) is a first-class DocType with a structured schema defined in the UI. Odoo uses a relational model with separate res.partner, product.template, product.product, and stock.quant objects, plus Odoo-specific flags (customer, supplier, seller) on partner records that ERPNext stores as separate DocTypes. We extract ERPNext data via CSV or direct MariaDB query, map each DocType to its Odoo counterpart, and load through Odoo's native import or direct SQL depending on volume and schema complexity. Custom fields stored in ERPNext's Custom Field DocType must be inventoried separately and recreated in Odoo Studio or as XML definitions before data loads begin. Workflows, approval rules, and Frappe server scripts do not migrate; we deliver a written inventory for the customer's Odoo partner to rebuild in Studio or as Python modules.

1:1

Customer → res.partner (customer flag = True)

ERPNext Customer DocType maps to Odoo res.partner with the customer boolean set to True.

How it maps

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.

1:1

Supplier → res.partner (supplier flag = True)

ERPNext Supplier DocType maps to Odoo res.partner with the supplier boolean set to True.

How it maps

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.

1:1

Item → product.template + product.product

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).

How it maps

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.

mapping

BOM (Bill of Materials) → mrp.bom + mrp.routing + mrp.workcenter

ERPNext BOMs with multi-level nesting and operation routing require flattening during extraction and reconstruction in Odoo's MRP module.

How it maps

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.

mapping

Stock Ledger / Warehouse → stock.warehouse + stock.location + stock.quant

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).

How it maps

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.

1:1

Sales Order → sale.order

ERPNext Sales Order with line items, taxes, discounts, and delivery schedules maps to Odoo sale.order and sale.order.line.

How it maps

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.

What moves11 objects
ERPNextOdoo ERP
  • Customerres.partner1:1
  • Supplierres.partner1:1
  • Itemproduct.template1:1
  • BOMmrp.bomtransformed
  • Stock Ledgerstock.warehousetransformed
  • Sales Ordersale.order1:1

+ 5 more in the mapping below

How ERPNext and Odoo ERP differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionERPNextOdoo ERP
Architecture modelDocument-based DocType in MariaDB, schema defined per-docRelational model with res.partner, product.template, stock.quant, project.project objects
Customer vs SupplierSeparate Customer and Supplier DocTypesSingle res.partner with customer and supplier boolean flags
Product structureItem DocType with UOM, valuation, barcodes as fieldsproduct.template (definition) + product.product (variants) split
BOM routingNested multi-level BOMs with operation routing and workstationsmrp.bom with operations table; routing as mrp.routing object
Payment tracking (v14+)Separate Payment Entry DocType linked via Payment Ledgeraccount.move with reconciled flag and payment_ids relation
Customization methodCustom fields via UI + server scripts in Python stored in DBOdoo Studio (no-code), custom fields, or Python modules
Pricing modelFree self-hosted or ~$10/user/mo on Frappe CloudCommunity free; Enterprise ~$25/user/mo

What to watch for in a ERPNext to Odoo ERP migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

ERPNext DocType schema does not map directly to Odoo model structure

ERPNext uses a document-based DocType model where each entity (Customer, Supplier, Item) is a self-contained schema defined in the UI.

How we handle it

Odoo uses a relational model with typed objects (res.partner, product.template, stock.quant) and Odoo-specific flags (customer, supplier, seller) that don't have direct ERPNext equivalents. Mapping ERPNext Customer and Supplier as separate DocTypes to a single res.partner with two boolean flags requires upfront schema design and deduplication of partner records that exist in both ERPNext DocTypes. We resolve this during discovery and validate partner uniqueness before migration loads begin.

high

Multi-level BOMs with operation routing require manual flattening and reconstruction

ERPNext Manufacturing supports nested BOMs with operation routing, workstation types, and piece-rate or hour-rate costing stored across the BOM, BOM Item, and Operation rows tables.

How we handle it

Odoo's MRP module uses a different data model with mrp.bom, mrp.bom.line, mrp.workcenter, and mrp.routing as separate tables. We export the full ERPNext operation tree, identify each workstation's Odoo equivalent, and reconstruct the routing sequence. If Odoo MRP is not included in the destination instance, routing data must be flattened into product description fields or a separate lookup table, and we present that choice to the customer during scoping.

medium

ERPNext v14+ Payment Ledger decouples payments from invoices

ERPNext v14 introduced a split Payment Ledger where payments are stored as independent Payment Entry documents linked to invoices via a separate table.

How we handle it

An invoice with full payment appears unpaid in a naive export because the paid status is not a field on the invoice document itself. We run a Payment Ledger join query during data extraction to resolve each invoice's actual payment state, set Odoo account.move payment_state accordingly, and create the corresponding account.payment records. Migrations that skip this step arrive in Odoo with every open invoice showing an unpaid balance even when settled.

medium

ERPNext custom fields must be inventoried and recreated before data loads

ERPNext stores custom fields in the Custom Field DocType, which references the parent DocType and defines field type, options, and mandatory flags.

How we handle it

These custom fields are not exported by the standard CSV export tool and must be queried separately from the database. Odoo has no automatic custom field import; we must create them in Odoo Studio or via XML definition before data loads. If custom fields exist on a DocType but are not pre-created in Odoo, the import skips those columns silently or throws a field-mismatch error. We inventory every custom field during discovery and deliver a recreation checklist with the migration scope.

low

Odoo module dependencies can block data loads if activation order is wrong

Odoo enforces module dependencies at install time.

How we handle it

Installing the Sales module before the Contacts module creates a different partner model than installing Contacts first. If the Odoo modules are activated in the wrong order relative to the migration schema, certain fields may not exist when we attempt the import. We design the Odoo module activation sequence during schema design, install modules in dependency order before any data loads, and validate the field registry against our import template before production migration begins.

How the migration runs

  1. Discovery and DocType inventory

    We audit the source ERPNext instance across DocTypes in active use, ERPNext version (v13, v14, or v15, since v14 introduced the Payment Ledger split), custom field registry (queried from the Custom Field DocType, not from CSV), active custom server scripts and Frappe Apps, BOM count and routing complexity, open invoice count and payment state, warehouse structure, and project/task hierarchy depth.

    What this step covers

    We also identify any Frappe Apps with third-party DocTypes that cannot migrate portably. The discovery output is a written migration scope with a DocType-to-Odoo-object mapping table and a BOM routing recommendation.

  2. Odoo module selection and schema design

    We design the destination Odoo module configuration based on the DocType inventory.

    What this step covers

    We map each ERPNext DocType to its Odoo equivalent, decide which Odoo modules to install (CRM, Sales, Purchase, Inventory, Manufacturing, Project, HR), configure the chart of accounts (Odoo provides country-specific templates; we map ERPNext account codes against the selected template), and create the custom field registry in Odoo Studio or XML. For BOM routing, we present the customer with a structured choice: install Odoo MRP and map full routing, or flatten to simple product BoM without routing. Schema design is validated in a staging Odoo database before production.

  3. Staging migration and reconciliation

    We run a full migration into a staging Odoo database using production-like data volume.

    What this step covers

    The customer's operations lead reviews record counts, spot-checks 25-50 records against the ERPNext source (partner details, invoice amounts and payment states, BOM component lists, project task counts), and validates that the custom field values populated correctly. BOM routing reconstruction is validated by generating an Odoo manufacturing order from a sample migrated BoM and confirming the operation sequence matches the ERPNext original. Any mapping corrections are documented and applied to the production migration script before cutover.

  4. Custom field recreation in Odoo

    Before any data loads begin, we create the full ERPNext custom field registry in the production Odoo instance.

    What this step covers

    Simple fields (Data, Float, Int, Check, Select, Long Text) are created in Odoo Studio. Complex fields with validation rules, conditional display logic, or non-standard fieldtypes are defined as XML data files and loaded via the Odoo module system. This step must complete before data loads because ERPNext custom fields contain business-critical data that cannot be omitted without corrupting reporting.

  5. Production migration in dependency order

    We run production migration in this sequence: chart of accounts (if migrating opening balances), then res.partner (customers and suppliers with deduplication applied), then product.template and product.product, then mrp.workcenter and mrp.bom with routing operations, then stock.quant with warehouse and location hierarchy, then sale.order and purchase.order with line items and child rows, then account.move with payment reconciliation (v14+ Payment Ledger query applied), then project.project and project.task with time logs, then hr.employee with attendance and leave, then attachments as binary fields on their parent records.

    What this step covers

    Each phase emits a row-count reconciliation report. We use Odoo's native CSV import for structured data and direct SQL for large volumes or complex relations that exceed CSV capacity.

  6. Cutover, validation, and rebuild handoff

    We freeze ERPNext writes during cutover, run a final delta migration of any records modified during the migration window, then set Odoo as the system of record.

    What this step covers

    We deliver a written inventory of all ERPNext workflows, approval rules, and custom server scripts with Odoo Studio rebuild instructions and a note that Studio can replace most custom field and form logic without code. We do not rebuild ERPNext workflows as Odoo Automations or server actions within migration scope; that work is a separate engagement or handled by the customer's Odoo partner. We provide a one-week hypercare window for reconciliation issues raised by the business team.

ERPNext Odoo ERP
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Odoo ERPRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-8 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with record volume, BOM complexity, custom field count, and module scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for ERPNext to Odoo ERP →

Why teams move from ERPNext to Odoo ERP

  • ERPNext targets small-to-medium businesses and performance degrades on large transaction volumes without MariaDB backend tuning, indexed query optimization, and adequate server resources. Teams with high order throughput, multi-warehouse inventory, or manufacturing operations find that ERPNext's default configuration constrains them and requires ongoing infrastructure investment to remain stable. Odoo's modular architecture and Odoo.sh managed cloud handle higher transaction volumes without requiring a dedicated DBA to tune the database layer.
  • ERPNext requires Python and JavaScript developers to extend the platform beyond custom fields. Modifying DocTypes, writing server scripts, or building Frappe Apps requires code access and Frappe Framework knowledge. Odoo Studio provides a no-code visual builder for creating custom fields, defining relationships, and adjusting forms and views, which reduces reliance on developers for ongoing configuration changes and lowers the total cost of ownership for teams without in-house Python expertise.
  • ERPNext has no native e-commerce module. Businesses needing to sell online must implement a separate platform (Shopify, WooCommerce, Magento) and maintain a custom integration with ERPNext. Odoo includes native e-commerce, Point of Sale, and marketplace modules that share the same product catalog, inventory, and sales order pipeline as the rest of the ERP, eliminating the integration surface and reducing monthly software spend for companies that need online selling.
  • ERPNext has no vendor SLA for self-hosted deployments and community support lacks contractually defined response times. Odoo offers an Enterprise Edition with Odoo Enterprise subscription support, a global certified partner network, and a larger ecosystem of implementation partners who can deliver SLA-backed support. Businesses with compliance obligations or that require a named support contact find Odoo's commercial support structure more aligned with enterprise governance requirements than ERPNext's community model.
  • ERPNext's module ecosystem is narrower than Odoo's app marketplace, with fewer certified third-party integrations and industry-specific vertical solutions. Odoo's open-core model funds an ecosystem of certified apps for manufacturing, agriculture, healthcare, education, and e-commerce that are maintained and version-compatible. Businesses requiring specialized integrations often find they exist for Odoo but not for ERPNext, which reduces custom API development work and lowers the total implementation cost for vertical-specific deployments.

Questions, answered

ERPNext to Odoo ERP migration questions

How long does an ERPNext to Odoo ERP migration take?

Most ERPNext to Odoo migrations land between four and eight weeks for small-to-medium businesses with standard modules (CRM, Sales, Inventory, basic Accounting) and under 2,000 partners and 1,000 products. Migrations with complex manufacturing BOMs, routing operations, multiple warehouses, large open invoice histories with v14 Payment Ledger reconciliation, or extensive custom field usage move to ten to sixteen weeks because of BOM tree flattening, routing reconstruction, and Odoo Studio custom field creation that must precede data loads.

Do ERPNext workflows, approval rules, and server scripts migrate to Odoo?

No. ERPNext workflows, Document State rules, and Frappe server scripts are stored as DocType records with event-handler hooks that do not have portable equivalents in Odoo's automation model. We deliver a written inventory of every active workflow and server script with its trigger conditions, actions, and Odoo equivalent (Odoo Studio Automations for simple rules, Python record rules for complex ones). Custom fields stored in ERPNext's Custom Field DocType also do not migrate automatically; we inventory them during discovery and recreate them in Odoo Studio or XML before data loads begin. Frappe App-specific DocTypes and custom modules require manual rebuild in Odoo by a Python developer.

Can we migrate ERPNext manufacturing data including BOM routing to Odoo?

Yes, with upfront design work. ERPNext nested BOMs with operation routing and workstation definitions map to Odoo MRP module's mrp.bom, mrp.bom.line, mrp.workcenter, and mrp.routing objects. We extract the full ERPNext BOM tree, resolve workstations to Odoo mrp.workcenter records with capacity and cost-per-hour data, and reconstruct the routing sequence as Odoo mrp.routing operations linked to the mrp.bom. If the destination Odoo instance does not include the MRP module, we present three options during scoping: install MRP (recommended for manufacturing businesses), flatten the routing to product description text in a simple product BoM, or maintain routing detail as a linked product attribute table for manual reference.

How does ERPNext v14 Payment Ledger affect the invoice migration?

ERPNext v14 and v15 decouple payments from invoices into a separate Payment Entry DocType linked via the Payment Ledger. A naive invoice export shows every open invoice as unpaid even when settled. We run a Payment Ledger join query during data extraction that resolves each invoice's actual payment state by matching Payment Entry records against the invoice's accounting ledger. We set Odoo account.move payment_state to matched (or partially_matched) and create corresponding account.payment records. Without this step, every migrated invoice appears unpaid in Odoo's aging report and payment follow-up workflow fires incorrectly for settled invoices.

How do you handle ERPNext's separate Customer and Supplier DocTypes in Odoo?

ERPNext maintains Customer and Supplier as separate DocTypes. Odoo uses a single res.partner model with boolean flags (customer, supplier) set independently, meaning a supplier can also be a customer. We extract both DocTypes, deduplicate any partner records that appear in both, and create a single res.partner with the appropriate flags set. If the same entity appears as both Customer and Supplier in ERPNext with different addresses, contact persons, or pricing tiers, we preserve both records and map them as separate address contacts on the unified partner.

Can we migrate ERPNext Projects and Tasks with the full hierarchy intact?

Yes. ERPNext Project with nested Tasks, assignees, time logs, and milestone dates maps to Odoo project.project and project.task. We preserve the task parent-child hierarchy by mapping ERPNext parent_task to Odoo task parent_id, extract time logs as account.analytic.line records linked to the project (requires Odoo Accounting to be active), and map ERPNext project_type (External vs Internal) to Odoo's privacy_visibility setting. Milestone dates migrate as deadline fields on tasks. We validate hierarchy depth and assignee resolution during the staging migration before running the production migration.

Get a quote

Moving from ERPNext to Odoo ERP?

Tell us roughly how many records and objects you have. We scope the mapping and the Odoo ERP setup with you, then send a quote.

Get a quote