Migrate from ERPNext to Dolibarr ERP

ERPNext Customer DocType records map to Dolibarr Third-Party objects with the IsCustomer flag set to 1. Customer name, primary contact details, GST/HST number, territory, and default currency migrate directly. Customer group maps to Dolibarr's Category system or a custom customer-type field. We extract all customer address and contact child table rows as separate relational CSVs and re-link them through Dolibarr's Contact and Address modules using the external ID pattern for deduplication during import.

ERPNext Supplier DocType maps to Dolibarr Third-Party with IsSupplier flag set to 1. Supplier name, primary contact, PAN/GST number, and default currency transfer directly. ERPNext's supplier price list maps to Dolibarr's supplier catalog if the purchasing module is activated. Address and contact child rows follow the same external-ID linking pattern as Customer.

ERPNext Item records map to Dolibarr Product (for stockable items) or Service (for non-stockable items) based on the Item's is_stock_item flag. Item code, item name, description, item group, brand, UOM, and barcodes migrate directly. Valuation method (FIFO, Moving Average, Standard Rate) stores as a custom field in Dolibarr since Dolibarr's stock valuation is simpler. ERPNext's item defaults per company map to Dolibarr's multi-entity price list configuration if the multi-company module is active.

ERPNext's multi-level nested BOM structure with operation routing and workstation definitions has no native Dolibarr equivalent. We extract the full BOM operation tree (items, quantities, operations, workstation types, cycle times) and present the customer with two options: store the flattened BOM as a linked custom configuration record in Dolibarr's Product module, or collapse multi-level BOMs into a simplified product recipe stored as custom fields. Operation routing and workstation costing do not migrate to standard Dolibarr fields; these are documented in the custom configuration record for manual reference.

ERPNext Sales Order maps to Dolibarr Order (with module Societe, Product, and Commande activated). Order header fields (customer, currency, payment terms, incoterms) migrate directly. Order items map as OrderLine records with product reference, qty, rate, and discount. Taxes and charges from ERPNext's taxes and charges child table migrate to Dolibarr's extra-fee line model. Packed items and product bundle components are extracted as separate relational rows and linked via the OrderLine relationship during import.

ERPNext Purchase Order maps to Dolibarr SupplierOrder (supplier order). Supplier reference, order date, currency, and payment terms migrate directly. PO line items map to Dolibarr SupplierOrderLine records with the supplier's product reference, ordered qty, and rate. Taxes and charges migrate as extra-fee lines following the same pattern as Sales Order.

ERPNext Sales Invoice maps to Dolibarr Facture (customer invoice). We resolve each invoice's payment status from ERPNext v14+'s split Payment Ledger before migration — an invoice appears open in ERPNext's invoice table even when settled, and the actual payment state is stored in Payment Entry and Payment Ledger records. We query the payment ledger, compute the resolved status (paid, partial, unpaid), and set the Dolibarr invoice status accordingly so open invoices do not appear overdue on day one.

ERPNext Purchase Invoice maps to Dolibarr Facture (supplier invoice). The same payment ledger resolution applies for ERPNext v14+ instances: we join Purchase Invoice with Payment Entry and Payment Ledger to compute the actual settled status before setting the Dolibarr invoice status. ERPNext's taxes withheld field maps to a custom field in Dolibarr since Dolibarr's standard tax model does not include withholding at the invoice line level.

ERPNext Payment Entry records map to Dolibarr Payment records linked to the resolved invoice via the invoice reference we compute during payment ledger resolution. For v13 and earlier, the paid/unpaid state is directly on the invoice; for v14+, we join Payment Entry to Payment Ledger to determine the settlement amount per invoice and create Dolibarr Payment records accordingly. Payment method (cash, bank, journal) maps to Dolibarr's PaymentMode field.

ERPNext Project DocType maps to Dolibarr Project with Task sub-objects. We extract the full project hierarchy: project name, customer (via Third-Party external ID), status, planned start and end dates, and billing type. Tasks nested under the project are exported as separate rows and inserted as Dolibarr Task records linked to the parent Project. ERPNext time logs and milestone dates are stored as Task fields or custom fields in Dolibarr depending on the customer's reporting needs.

ERPNext Employee DocType records map to Dolibarr User records when Dolibarr's HR module (RH) is activated. Employee name, date of joining, department, designation, and employment type migrate directly. Salary structure and bank details store as custom fields on the User object since Dolibarr's standard HR module stores these in separate child tables that require module activation. ERPNext attendance and leave records migrate as Dolibarr Holiday and Attendance records if the corresponding Dolibarr modules are activated.

ERPNext Stock Entry records map to Dolibarr StockMovement records (with Stock module activated). We flag whether ERPNext uses perpetual or periodic inventory because Dolibarr's default stock module assumes perpetual. Open stock ledger entries with future effective dates are exported and inserted with their original posting dates to preserve the financial period in which they should have been recorded.

ERPNext Custom Field DocType registry is exported as a separate catalog of field definitions (fieldname, fieldtype, label, options, mandatory flag, depends_on condition). We provide a written guide for reconstructing each custom field in Dolibarr's CustomFields module, which uses PHP hook injection rather than a UI-based custom field builder. The customer or a Dolibarr partner recreates these in Dolibarr before the data import phase so that fields exist on the destination schema before records are loaded.

ERPNext File records reference blob storage (Frappe private files or S3-compatible). We export file metadata (filename, URL, doctype reference, creation date) and copy binary files to the Dolibarr documents directory. The file's parent reference is reconstructed in Dolibarr by matching the source doctype and document name against the migrated record IDs. Large binary attachments may require FTP or direct file copy into the Dolibarr documents directory rather than API upload.