Skip to content
Get a quote

ERPNext to Business Central migration

We migrate Customers, Vendors, Items, Invoices, Projects, and BOMs from ERPNext into Microsoft Dynamics 365 with ERPNext's document-based DocType extraction handled through the Frappe API or MariaDB, Payment Ledger resolution for v14+ open invoices, and BOM routing flattened into the destination's equivalent schema before cutover.

Short answer

FlitStack AI migrates account + contacts, vendors, items, bom + routes and warehouse + sites from ERPNext to Business Central, 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: 5-8 weeks.

By

Source ERPNext
DestinationBusiness Central
Account + ContactVendorItemBOM + RouteWarehouse + Site
Mapped field by field · sample run · one-click rollback

What moves from ERPNext to Business Central?

ERPNext and Microsoft Dynamics 365 are architecturally different systems.

Read the full summary

ERPNext stores every entity as a DocType document in MariaDB with a document-ownership model; Dynamics 365 stores entities as typed rows in Dataverse or SQL with relational foreign keys. That structural difference shapes the entire migration: we extract from ERPNext via the REST API, direct database query, or CSV export, then transform each DocType into the equivalent Dynamics 365 entity. ERPNext's v14+ Payment Ledger decouples invoice payment status from the invoice itself, requiring a join query to resolve open-invoice status before setting the Dynamics 365 invoice record state. Multi-level BOMs with operation routing must be flattened into a separate lookup table or collapsed into custom fields since no standard Dynamics 365 object captures nested routing. Custom server scripts, Frappe App DocTypes, Workflow rules, and document-state approval chains do not migrate — we deliver a written inventory of every automation and script for the customer's admin to rebuild in Dynamics 365. We do not handle post-migration admin support, training, or workflow rebuild as standard scope.

1:N split

Customer → Account + Contact (split by type)

ERPNext Customer DocType holds both company accounts and individual contacts under one record.

How it maps

We split on the customer_type field: customer_type = 'Company' maps to Dynamics 365 Account; customer_type = 'Individual' maps to Contact attached to a parent Account. The customer_name becomes Account Name or Contact Last Name; website from ERPNext maps to Account Website. Address and contact details split into Dynamics 365 Address and Contact composite fields.

1:1

Supplier → Vendor

ERPNext Supplier maps directly to Dynamics 365 Vendor.

How it maps

Supplier name becomes Vendor Name; supplier_group maps to Vendor Group. Default currency and payment terms migrate to the vendor master. ERPNext supplier addresses and contact persons map to Vendor Address and Vendor Contact respectively.

1:1

Item → Item (Released Product in Finance and Operations; Item in Business Central)

ERPNext Item DocType maps to the destination's product or item master.

How it maps

Item code becomes Item Number; item_name becomes Product Name; item_group maps to Product Group; stock_uom becomes the default unit of measure. Valuation method (FIFO, Moving Average, Periodic) maps to Costing Method; standard_rate maps to Standard Cost. Custom fields on the Item DocType migrate as extended fields.

configuration

BOM (Bill of Materials) → BOM (Engineering or Manufacturing BOM) + Route (Finance and Operations)

ERPNext nests BOMs to arbitrary depth with operation routing, workstation types, and hour-rate costing.

How it maps

We flatten the full operation tree, map each BOM level to a parent-child BOM structure in Dynamics 365, and store routing operations as a Route record (Finance and Operations) or custom fields (Business Central). If the destination is Business Central without the Manufacturing extension, we collapse routing detail into a text field on the BOM header and present the customer with a rebuild recommendation for the route layer.

1:1

Warehouse → Warehouse + Site (Finance and Operations)

ERPNext Warehouse DocType maps to Warehouse in Business Central or to Site plus Warehouse in Finance and Operations.

How it maps

Bin-level stock data from ERPNext's Stock Ledger Entry (tabBin) maps to inventory dimensions in Dynamics 365, with the dimension combination preserved as an Inventory Dimension Group configuration.

1:1

Stock Ledger Entry → Warehouse Entry (Business Central) or Inventory Transactions (Finance and Operations)

ERPNext Stock Ledger Entry records carry warehouse, item, qty, valuation rate, and fiscal year.

How it maps

We extract open entries (Qty > 0) as current inventory snapshot and archive closed entries by fiscal year. The destination system's inventory model (periodic vs perpetual) determines whether the valuation rate is set as a fixed cost on the item master or carried as individual warehouse entry records.

What moves15 objects
ERPNextBusiness Central
  • CustomerAccountsplit
  • SupplierVendor1:1
  • ItemItem1:1
  • BOMBOMtransformed
  • WarehouseWarehouse1:1
  • Stock Ledger EntryWarehouse Entry or Inventory Transactions1:1

+ 9 more in the mapping below

How ERPNext and Business Central 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.

DimensionERPNextBusiness Central
Architecture modelDocument-based DocType stored in MariaDBTyped relational rows in Dataverse or Azure SQL (Finance and Operations)
Contact modelSingle Customer DocType for both companies and individualsSeparate Account (company) and Contact (person) with parent-child relationship
Payment trackingIndependent Payment Entry documents decoupled from invoices (v14+)Payment linked to invoice via CustomerLedgerEntry / VendorLedgerEntry journal lines
BOM structureArbitrarily nested BOM with operation routing and workstationsSingle-level BOM (Engineering or Manufacturing); routing stored as route operations table or custom fields
LicensingOpen-source GPL-3.0; hosting cost onlyPer-user subscription ($70-$210/user/mo) with Azure infrastructure add-on
Custom fieldsCustom Field DocType registry, editable per siteCustom fields defined in solution layer or Power Apps maker portal per entity
AutomationCustom server scripts, DocType workflows, and document state rulesPower Automate flows, Dataverse plugins, or X++ extensions for Finance and Operations
Upgrade riskCustom scripts break silently on major version upgradesExtension-first model reduces direct code risk on minor updates

What to watch for in a ERPNext to Business Central migration

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

high

ERPNext v14+ Payment Ledger decouples payment from invoice

ERPNext v14 introduced a split Payment Ledger where Payment Entry documents are independent of invoices.

How we handle it

An invoice's paid/unpaid state depends on a separate query joining Payment Ledger Entry to the invoice. When migrating open invoices to Dynamics 365, a naive import sets every invoice as unpaid even if it has been fully settled, because the payment linkage is not present in the invoice document itself. We run the payment resolution query against the ERPNext database during extraction, compute the actual paid_amount and outstanding_amount per invoice, and set the Dynamics 365 invoice status accordingly. Skipping this step produces incorrect aged receivables and payables reports at go-live.

high

ERPNext custom server scripts do not migrate to non-Frappe platforms

Frappe server scripts hook into document save, validate, and submit events and are stored in the database, not in a version-controlled file.

How we handle it

When migrating away from ERPNext to Dynamics 365, there is no portable equivalent: server scripts must be inventoried during discovery, their business logic documented, and their Dynamics 365 equivalent rebuilt manually in X++ (Finance and Operations) or Power Automate / Dataverse plugins (Business Central). We audit the full script registry during discovery and deliver a written compatibility report listing each script, its trigger, and the recommended rebuild path. Custom DocTypes from third-party Frappe Apps cannot be migrated without access to the app source code and a compatible Frappe environment.

high

Multi-level BOM routing has no direct Dynamics 365 equivalent without configuration

ERPNext supports arbitrarily nested BOMs with operation routing, workstation types, and piece-rate or hour-rate costing across multiple production steps.

How we handle it

Dynamics 365 Finance and Operations stores BOM routing as a separate Route record with operations linked to work centers, but Business Central without the Manufacturing extension has no native routing object at all. We extract the full operation tree from ERPNext, flatten it, and present the customer with two options during scoping: maintain routing detail in a linked lookup table in Dynamics 365 or collapse the BOM to a simplified single-level structure. The choice depends on whether the customer uses Dynamics 365 Finance and Operations (with the Manufacturing module) or Business Central.

medium

ERPNext Chart of Accounts structure may conflict with Dynamics 365 GL design

ERPNext uses a strict parent-child account hierarchy where every account must belong to a root company and an account type (Asset, Liability, Income, Expense).

How we handle it

Dynamics 365 Finance and Operations uses a financial dimensions model with a more flexible account structure and mandatory dimensions on journal lines. Business Central uses a standard chart of accounts with account categories. Migrations that carry over the ERPNext COA without restructuring produce journals that fail Dynamics 365 dimension validation. We audit the ERPNext COA, identify accounts with non-standard root types or missing company assignment, and flag structural changes required before account import begins.

medium

Custom fields and Frappe App extensions require manual schema recreation

ERPNext custom fields are stored in the Custom Field DocType and referenced per DocType.

How we handle it

There is no bulk export of custom field definitions — each field must be queried individually from the database or read from the Data Export tool's per-Doctype output. We export the full Custom Field registry separately, but recreating those fields in Dynamics 365 requires manual entry in the Power Platform maker portal, Visual Studio metadata, or Business Central page designer depending on the Dynamics 365 app. We recommend allocating two to three weeks of admin time for custom field recreation after migration, separate from the data migration work.

How the migration runs

  1. Discovery and destination edition selection

    We audit the source ERPNext instance across version (v13, v14, v15), DocType inventory, custom field registry, active server scripts, Frappe App extensions, BOM complexity, and historical transaction volume.

    What this step covers

    We extract a data quality sample from the live database (or CSV export) to assess duplicates, missing required fields, and account structure gaps. We pair this with a Dynamics 365 edition decision: Business Central ($70-$100/user/mo) suits companies under 250 users with standard accounting and distribution needs; Finance and Operations ($180/user/mo) is required for manufacturing with BOM routing, advanced warehouse management, or multi-entity legal structure. The discovery output is a written migration scope, a Dynamics 365 edition recommendation, and a custom field recreation work estimate.

  2. Source extraction and payment ledger resolution

    We extract ERPNext data via the REST API (for smaller volumes) or direct MariaDB query (for large or custom DocTypes).

    What this step covers

    For v14+ instances, we run a payment resolution query that joins the Payment Entry, Payment Ledger Entry, and Sales/Purchase Invoice tables to compute the accurate outstanding_amount for each open invoice before extraction. We export BOMs with their operation routing as a separate relational dataset. We query the Custom Field DocType to produce the full custom field registry. All extractions produce de-duplicated CSVs or JSON with parent-record references preserved. We run a pre-import data quality pass to identify duplicates and missing required fields, and we present a remediation file for the customer's review before ingestion begins.

  3. Destination schema design and BOM routing decision

    We design the Dynamics 365 destination schema: Chart of Accounts structure (with dimension configuration if Finance and Operations), Item product types and costing methods, warehouse and site layout, BOM structure (flat or parent-child with route), and custom field recreation plan.

    What this step covers

    For BOM routing, we present the customer with two options and document their choice before transformation begins. We create the Dynamics 365 entities in a Sandbox environment using the Data Management Framework (Finance and Operations) or directly in Business Central for validation. ERPNext Workflow and Document State rules are documented as a separate automation inventory for the customer to rebuild post-migration.

  4. Sandbox migration and reconciliation

    We run a full migration into a Dynamics 365 Sandbox using production-like data volume.

    What this step covers

    The customer's finance lead reconciles trial balance (total debits equals total credits across the Chart of Accounts), open invoice counts and values, inventory on-hand quantities per warehouse, and BOM structure completeness. The operations lead spot-checks 25-50 random records against the ERPNext source. Any field mapping corrections, data quality fixes, or BOM routing decisions are resolved in the Sandbox before production migration begins.

  5. Owner and account reconciliation

    We extract every distinct ERPNext user referenced as an owner on transactions and match by email against the Dynamics 365 destination User table.

    What this step covers

    Users without a match go to a reconciliation queue for the customer's admin to provision. Account and contact reconciliation ensures no duplicates on insert: we use ERPNext customer_name as the deduplication key against Account Name in Dynamics 365. Payment reconciliation is confirmed by matching total paid amounts per invoice from the ERPNext Payment Ledger query against the destination payment records.

  6. Production migration in dependency order

    We run production migration in record-dependency order: Chart of Accounts and Dimensions (if Finance and Operations), Warehouses and Sites, Items and Products (with pricing), BOMs and Routes (flattened from ERPNext), Customers and Suppliers (with company-individual split applied), open Sales and Purchase Orders, open Invoices (with Payment Ledger resolution applied), historical closed transactions (by fiscal year), Projects and Tasks, Employee records, File attachments and notes.

    What this step covers

    Each phase emits a row-count and value reconciliation report. We freeze ERPNext writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record.

  7. Cutover, validation, and automation rebuild handoff

    We validate the production migration against the Sandbox reconciliation baseline: trial balance balances, open invoice outstanding amounts match ERPNext's payment ledger state, inventory on-hand matches the Stock Ledger snapshot, BOM operations are present in the route.

    What this step covers

    We deliver the Server Script and Custom Field inventory document to the customer's admin team. We support a one-week hypercare window to resolve any data reconciliation issues raised by the business. We do not rebuild ERPNext server scripts as X++ or Power Automate flows inside the migration scope; that is a separate engagement or an internal development task.

ERPNext Business Central
  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 · Business CentralRollback 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

5-8 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with transaction volume, BOM complexity, number of custom fields, and whether the destination is Business Central (Dataverse-backed) or Finance and Operations (Azure SQL). Every quote is scoped with you; there is no self-serve pricing.

Get a quote for ERPNext to Business Central →

Why teams move from ERPNext to Business Central

  • ERPNext's community-driven support lacks SLA-backed guarantees that enterprises with compliance obligations require. Organizations moving to regulated industries (manufacturing, healthcare, finance) or those carrying ISO 27001, SOC 2, or GDPR processor requirements find the absence of a vendor contractually defined response time difficult to accept. Microsoft Dynamics 365 ships with contractual SLA commitments per tier, and Azure's compliance certifications cover the infrastructure layer transparently.
  • ERPNext performance degrades on large transaction volumes unless the MariaDB backend is tuned, indexed, and running on provisioned infrastructure. Manufacturing and distribution operations with thousands of daily stock transactions, multi-level BOM evaluations, or high-frequency POS postings frequently outgrow the default configuration and require dedicated DBA work. Dynamics 365 Finance and Operations scales horizontally on Azure SQL with Microsoft-managed performance tuning, removing the infrastructure tuning burden.
  • Deep customization through Frappe server scripts and third-party Frappe Apps creates upgrade paralysis. Reviewers on G2 and Capterra describe being locked to an older ERPNext version because a critical third-party app has not been updated for the latest Frappe release, blocking security patches and new features. Dynamics 365's extension-first model and the Power Platform AppSource ecosystem provide upgrade stability without the risk of third-party apps breaking silently on version change.
  • Organizations already invested in the Microsoft ecosystem (Microsoft 365, Azure, Power BI, Teams, SharePoint) find Dynamics 365's native integration removes friction that ERPNext requires custom API work to achieve. Single sign-on via Entra ID, native Power BI reporting without an intermediate data warehouse, and Dataverse as a shared data layer across the Power Platform reduce integration overhead significantly compared to ERPNext's REST API configuration for the same connections.
  • Version upgrades between major ERPNext releases (v13 to v14, v14 to v15) frequently break custom server scripts because the Frappe API surface changes with each Python runtime upgrade. Organizations report spending weeks on regression testing before each upgrade, and some find their customizations cannot survive the next release without being rewritten. Dynamics 365's twice-yearly update cadence is managed by Microsoft with deprecation notices published 12 months in advance.

Questions, answered

ERPNext to Business Central migration questions

How long does an ERPNext to Microsoft Dynamics 365 migration take?

Most migrations land between five and eight weeks for accounts with under 50,000 master records, fewer than 200 BOMs, and no complex payment ledger reconciliation. Migrations with multi-level BOMs, large historical transaction volumes (over 200,000 invoices), extensive custom field registries, or a Finance and Operations destination move to twelve to twenty weeks because of BOM flattening, GL restructuring, and payment state resolution work.

Do ERPNext Workflows and server scripts migrate to Dynamics 365?

No. ERPNext server scripts, DocType workflows, and document state approval rules are Frappe Framework concepts that have no portable equivalent in Dynamics 365. Server scripts must be rebuilt in X++ (Finance and Operations) or Power Automate / Dataverse plugins (Business Central); workflows must be rebuilt in Dynamics 365 Workflow, Power Automate, or Business Central's native workflow engine. We deliver a written inventory of every active server script and workflow with its trigger, conditions, actions, and a recommended rebuild path. The customer's admin or a Dynamics 365 partner rebuilds them post-migration.

Can we migrate our ERPNext BOMs with operation routing to Dynamics 365?

Partially. ERPNext's arbitrarily nested BOMs with operation routing, workstation types, and hour-rate costing require flattening before migration. If the destination is Dynamics 365 Finance and Operations with the Manufacturing module, we map the flattened BOM to a Manufacturing BOM plus a Route record with work center operations. If the destination is Business Central without the Manufacturing extension, we collapse routing detail into a text or custom field and present the customer with a rebuild recommendation for the route layer. We do not attempt to preserve the full nested BOM depth as a native Dynamics 365 BOM structure without prior customer sign-off on the structural choice.

How does ERPNext v14+ Payment Ledger affect invoice migration?

ERPNext v14 and later decouples payments from invoices. A Sales Invoice in ERPNext v14 does not store its payment status internally — it depends on a separate Payment Ledger Entry table. When migrating open invoices to Dynamics 365, we run a join query against the ERPNext database that computes the actual paid_amount and outstanding_amount per invoice before setting the destination invoice status. Without this step, every open invoice appears unpaid in Dynamics 365 even when it has been fully settled, producing incorrect aged receivables reporting at go-live.

Do ERPNext custom fields and Frappe App extensions migrate?

Custom field definitions on ERPNext DocTypes are stored in the Custom Field DocType. We export the full registry (fieldname, fieldtype, options, mandatory flag) and recreate each as a custom field in Dynamics 365: Extended fields in Finance and Operations require Visual Studio metadata or the Power Platform maker portal; custom fields in Business Central are created in the page designer. Custom field values migrate as standard field data in the same migration pass as the parent record. Frappe App third-party DocTypes cannot migrate without access to the app source code and a compatible Frappe environment; we document them as out-of-scope with a rebuild recommendation.

Can FlitStack AI migrate ERPNext data into Dynamics 365 Finance and Operations specifically?

Yes. Finance and Operations uses the Data Management Framework with entity-based import rather than direct table insert. We transform extracted ERPNext data into Finance and Operations data entity format (for example, CustomerV3Entity, VendorV2Entity, EcoResReleasedProductV2Entity, SalesInvoiceHeadersV2Entity) and load via the Data Management Framework's staging table and execution framework. BOMs and routes load via the BOM Designer and Route entities. GL restructuring for account type conflicts happens during transformation before staging table load. We run Sandbox validation before any production Finance and Operations import.

What happens to our ERPNext attachments and file history during migration?

ERPNext File DocType records reference binary data stored in the Frappe private files folder or an S3-compatible bucket. We export file metadata (filename, URL, reference doctype and docname) and copy the binary file to the destination SharePoint document library (Finance and Operations / Business Central with Microsoft 365 integration) or as Business Central document attachments, linking each file to the migrated record by its Dynamics 365 ID. ERPNext comments and communication records migrate as Notes or Activities in Dynamics 365. The Frappe private files folder must remain accessible during migration for us to retrieve the binary data.

Get a quote

Moving from ERPNext to Business Central?

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

Get a quote