Migrate from ERPNext to Microsoft Dynamics 365 Business Central

ERPNext Customer DocType holds both company accounts and individual contacts under one record. 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.

ERPNext Supplier maps directly to Dynamics 365 Vendor. 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.

ERPNext Item DocType maps to the destination's product or item master. 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.

ERPNext nests BOMs to arbitrary depth with operation routing, workstation types, and hour-rate costing. 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.

ERPNext Warehouse DocType maps to Warehouse in Business Central or to Site plus Warehouse in Finance and Operations. 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.

ERPNext Stock Ledger Entry records carry warehouse, item, qty, valuation rate, and fiscal year. 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.

ERPNext Sales Invoice maps to Microsoft Dynamics 365 Sales Invoice. The invoice number becomes Invoice Number; customer maps to Account; posting_date maps to Invoice Date. Line items map to invoice lines with item number, quantity, and unit price resolved. ERPNext taxes and charges migrate as tax lines on the invoice. Open-invoice payment status is resolved by joining the Payment Ledger (v14+) or Payment Entry DocType before setting the invoice status, so partially paid invoices reflect the correct remaining amount.

ERPNext Purchase Invoice maps to Dynamics 365 Vendor Invoice. Supplier maps to Vendor; posting_date maps to Invoice Date; the ERPNext bill_no becomes Vendor Invoice Number. Line items map by matching the ERPNext item or expense account to the destination's item or ledger account. Prepaid invoices from ERPNext Payment Entry with apply_to document type 'Purchase Invoice' migrate as partially paid vendor invoices with the payment reference recorded.

ERPNext Sales Order maps to Sales Order with the ERPNext per_delivery_note_map flag resolved into Delivery Terms. Order status (Draft, Submitted, Cancelled) maps to the corresponding Dynamics 365 document status. Packed items and product bundle components from ERPNext become separate order lines with a bundle relationship preserved as a Sales Order BOM or kit item in the destination.

ERPNext Purchase Order maps to Dynamics 365 Purchase Order. Supplier maps to Vendor; the ERPNext schedule_date per line maps to the confirmed delivery date on the purchase order line. Purchase Order status migrates as document status. ERPNext drop shipment and loop hole flags map to the corresponding purchase order line types in Dynamics 365.

ERPNext Payment Entry documents (v14+ independent of invoices) map to payment journal lines in Business Central or to ledger entries with voucher type JournalVoucher in Finance and Operations. We extract the Payment Entry, its mode_of_payment, and the invoice references (paid_amount per linked invoice) and reconstruct the payment in the destination with the correct invoice settlement record. This resolves the common issue where an open invoice appears unpaid in the destination if the payment linkage is not migrated.

ERPNext Project DocType nests Tasks with assignees, time logs, and milestone dates. We extract the full project hierarchy, map ERPNext's project_type (billable vs non-billable) to the project type in Dynamics 365, and flatten tasks as project tasks with start and end dates. Time logs from ERPNext's timesheet-detail records map to TimesheetLine or Journal Line depending on whether the destination uses Timesheet for billable tracking.

ERPNext Employee DocType maps to the HR worker or employee master in Dynamics 365. Department, designation, date of joining, and salary structure details carry over. ERPNext's salary slip and salary component structure maps to the Pay Statement / Earnings / Deduction model in Business Central or to Payroll elements in Finance and Operations (which requires a payroll integration add-on not in base Finance and Operations). Attendance and leave records export as separate line entries.

ERPNext custom fields are stored in the Custom Field DocType with parent_doctype, fieldname, fieldtype, and options. We export the full registry and recreate each as a custom field in the destination: Extended fields in Finance and Operations require a developer environment (Visual Studio, metadata XML) or the Power Platform field maker; custom fields in Business Central are created in the page designer. Custom field values on records migrate as standard field data in the same migration pass as the parent record.

ERPNext File DocType stores binary data 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 to the destination SharePoint document library or Business Central document attachments, linking each file to the migrated record via its ID. ERPNext comments and communication records migrate as Notes or Activities in Dynamics 365.