Migrate from Expand ERP to Dolibarr ERP

Expand ERP Customer records map to Dolibarr Third Party with Type=Customer. Contact details, billing and shipping addresses, payment terms, and GST/tax identification fields migrate as standard Dolibarr fields. We preserve any custom properties as Dolibarr extrafields. The dedupe key is the customer's email address or phone number, whichever is populated in the source.

Expand ERP Vendor records map to Dolibarr Third Party with Type=Supplier. Vendor contact info, address, and payment terms migrate directly. Like Customers, we use email or phone as the dedupe key and preserve any custom properties as Dolibarr extrafields. Vendor-specific fields such as TIN/GST registration that have no Dolibarr standard equivalent become extrafields with explicit labeling.

Expand ERP Items map to Dolibarr Products (for physical goods) or Services (for non-stock items). We map SKU, product name, unit of measure, and pricing directly. Stock quantities map to Dolibarr Warehouse Stock entries. If Expand ERP uses barcodes or lot numbers, these migrate as product extrafields. The product type classification (stockable, service, assembly) is determined during scoping based on the item's stock tracking setting.

Expand ERP Sales Orders map to Dolibarr Order (commande client). Order header fields (order number, date, customer reference, payment terms) migrate directly. Line items migrate with product reference, quantity, unit price, tax, and discount preserved. We resolve the customer Third Party reference by email match before inserting orders so that Dolibarr's customer-linked order view renders correctly.

Expand ERP Purchase Orders map to Dolibarr Supplier Order (commande fournisseur). Vendor reference resolves to the Supplier Third Party by email match. PO line items, expected delivery dates, and purchase pricing map directly. Any import-related fields (port of entry, HS code, country of origin) that have no Dolibarr standard field become extrafields on the Supplier Order.

Expand ERP Leads with no confirmed sales relationship map to Dolibarr Lead. Leads with an attached confirmed Sales Order or Purchase Order map to a Dolibarr Third Party with Type=Prospect or Customer. We apply the split based on whether the Lead has a linked commercial document in Expand ERP, preserving the lead source and status as Dolibarr extrafields.

Expand ERP Warehouses map directly to Dolibarr Warehouse. We transfer warehouse name, location, and the current stock balance per item. Bin-level or lot-level stock details that are not exposed in Expand ERP's standard export are flagged for supplemental inventory report extraction and cross-referenced against the standard stock export before finalizing the import.

Expand ERP POS Billing transactions (transaction ID, date, payment method, line items) map to Dolibarr POS Transaction entries. However, Expand ERP's register-specific identifiers and shift summaries may not export via standard routes. We extract transaction headers and line items as a prioritized migration object and flag any missing register reconciliation data in the handoff document, noting that shift settlement reports may require manual re-entry in Dolibarr POS.

Expand ERP Production Jobs (work orders, bill of materials, output quantities, material consumption) map to Dolibarr Project or Stock Module depending on the customer's Dolibarr module configuration. We map production job headers and material consumption lines as Project Tasks. BOM versioning requires per-record field review because Expand ERP's BOM version tracking may not have a direct Dolibarr equivalent; we document each BOM's versioned structure in the handoff and recommend a Dolibarr BOM setup aligned to the most recent version.

Expand ERP export documentation records (licence numbers, shipping marks, customs fields, country-specific attributes) have no native Dolibarr equivalent. We extract document references and key fields as structured Notes attached to the relevant Third Party or Project. The original licence numbers and customs fields are preserved as searchable note content. We flag any mandatory fields that require re-entry in Dolibarr's linked document section or a custom export documentation module from the Dolistore.

Expand ERP account codes and names map to Dolibarr Accounting module accounts. Account type mapping (Asset vs Expense vs Revenue) must be confirmed against the destination's chart of accounts structure during scoping. If the customer enables the Dolibarr double-entry accounting module, we map account codes and names, flag any accounts with no Dolibarr equivalent, and document them for manual account creation before the accounting data migration phase.

Expand ERP User accounts (name, email, role) map to Dolibarr User records. Role-based access structures differ between platforms, so we migrate user identities and flag role mapping as a post-migration configuration step. The customer's Dolibarr admin assigns Dolibarr permission profiles (Standard User, Read-Only, Admin) based on the migrated role descriptions we document during scoping.