Migrate from ERPnext Enterprise - Bespoke to Dolibarr ERP

ERPNext Customer DocType maps to Dolibarr Third Party with the customer flag enabled. We extract name, territory (preserved in a custom field for downstream reporting), contact details, and tax ID. The Dynamic Link table in ERPNext stores contact-address relationships as separate records; we resolve these relationships during export to produce flat contact records with embedded address data compatible with Dolibarr's structure. Territory linkage is preserved so reporting hierarchies carry forward.

ERPNext Supplier DocType mirrors Customer in structure. We migrate supplier type, payment terms, and address records. ERPNext supplier-specific tax categories are carried forward as Dolibarr Custom Fields on the Third Party. Email addresses are set as the dedupe key so duplicate suppliers do not re-import.

ERPNext Items carry a broad attribute set — item code, description, item group, stock UoM, valuation method, and barcodes. We preserve the full item master including barcodes and custom fields at the item level. Item groups map to Dolibarr categories, and the ERPnext valuation method (FIFO, Moving Average) is stored as a custom field since Dolibarr's default stock valuation uses Moving Average.

ERPNext BOMs are nested structures referencing Items with quantity ratios and operation routing. We map BOM hierarchies directly but validate that all child item codes exist in Dolibarr before committing to avoid orphaned assembly records. If Dolibarr's production module is not enabled at the destination, BOMs are exported as a reference file rather than imported. BOMs referencing ERPNext-specific operation routing (workstation types, operation timings) cannot be fully represented in Dolibarr without manual reconstruction of the routing steps.

ERPNext Sales Orders contain document headers, line items, taxes, discounts, and shipping details. We map the full header and child rows into Dolibarr Commercial Proposal or Sales Order depending on the order status at migration time. For open orders, we preserve the qty-delta logic against linked Delivery Notes as Dolibarr does not natively track partial delivery ratios. Closed orders migrate as invoice records.

ERPNext Purchase Orders mirror Sales Orders in structure. We migrate PO headers and line items, flagging any advance allocation records that require separate handling as Payment Entries in Dolibarr. PO status mapping: Draft and Submitted map to Dolibarr Draft and Validated; Ordered maps to Ordered; Received maps to Received; Cancelled is not migrated.

ERPNext Delivery Notes map to Dolibarr Shipments. We preserve the linked Sales Order reference as a custom field on the Dolibarr record since Dolibarr's shipment-to-order linkage is module-dependent. Items, quantities, and batch numbers (if tracked) migrate with the shipment.

ERPNext Purchase Receipts map to Dolibarr Reception records. We preserve the linked Purchase Order reference, incoming items, received quantities, and any quality inspection results. Rejected quantities are stored as a custom field on the reception line since Dolibarr's standard reception does not natively record rejection sub-quantities.

ERPNext Sales Invoices map to Dolibarr Customer Invoice. Header fields (customer, currency, payment terms, due date) migrate directly. Line items map with qty, rate, tax, and discount. The ERPNext outstanding amount and write-off amount migrate to Dolibarr fields. Paid invoices migrate with payment records attached.

ERPNext Purchase Invoices map to Dolibarr Supplier Invoice. The mapping mirrors the Sales Invoice path in reverse. ERPNext's cost centre and project references on invoice lines are preserved as custom fields on Dolibarr invoice lines.

ERPNext uses a voucher-based double-entry system with voucher rows carrying account code, debit, and credit. Dolibarr handles general ledger through its banking and expense modules with direct database entries rather than a formal journal voucher interface. This is the most complex mapping in an ERPNext-to-Dolibarr migration. We map journal entry rows to Dolibarr account codes but validate that the destination chart of accounts has matching account numbers, which frequently requires pre-migration account restructuring. If ERPNext multi-company setup is in use, Dolibarr's inter-company module must be explicitly enabled and configured before GL data can be meaningful in the destination.

ERPNext SLEs track individual stock movements with timestamp, warehouse, item, qty, and valuation rate. Dolibarr does not maintain a full movement ledger; it stores current stock position per warehouse-item. We migrate the latest stock snapshot as Dolibarr opening quantities and export historical SLEs as a reference file. The reference file is provided as a CSV so the customer can run analytics on historical stock trends outside Dolibarr.

ERPNext Projects carry a nested task hierarchy with assignees, start/end dates, billable hours, and billing rates. We map the full project-task tree including custom task fields and hourly rate settings. ERPNext's project-specific billing types (based on hours, task, or fixed) are preserved as Dolibarr project task categories.

ERPNext User records include email, name, enabled status, and role profiles. We export enabled users and match by email to Dolibarr User records. ERPNext role permission rules and DocType-level access controls do not have a direct Dolibarr equivalent and must be reconstructed manually based on the exported configuration. The FlitStack AI inventory document captures the full role matrix for the admin to rebuild.

ERPNext Custom Fields attach to any DocType via the Custom Field DocType. We export all custom field definitions separately and create matching fields in Dolibarr before importing data so that target fields exist at import time. ERPNext custom field types (Check, Table MultiSelect, Dynamic Link) require mapping to Dolibarr equivalent field types, which we define during the schema design phase. Custom fields referencing deprecated ERPNext v15 modules (Social Media, TaxJar, Exotel, Lending, e-commerce) are flagged and excluded from migration.

ERPNext Fixed Asset records include purchase details, depreciation schedule, and current value. We map asset masters and active depreciation schedules. Assets already fully depreciated to zero are migrated as historical records unless the customer specifically requests them carried forward as active.

ERPNext Employee DocTypes expose employment details, department, and reporting structure. We migrate active employees and current compensation records including department and reporting manager linkage. ERPNext payroll history and historical salary records are out of scope; those are better handled through a dedicated HR system migration or a separate payroll data export.

ERPNext file attachments — scanned documents on Purchase Receipts, images on Item masters, PDFs on Sales Invoices — are stored in the file store (file system or S3 bucket) and are not included in the standard CSV Data Export or REST API response. We export attachments separately via direct file system access or bench export-background-files, preserve the folder hierarchy, and re-associate files with the correct records in Dolibarr using filename-to-record mapping during post-migration.