Migrate from Lead Commerce to Dolibarr ERP

Lead Commerce order records with fulfillment status (pending, processing, shipped, completed) map to Dolibarr's Order (Facture/Avoir) object depending on invoice status. We separate fulfilled orders (mapped to Dolibarr Invoice) from open orders (mapped to Dolibarr Order) during the pre-import transform. Order dates, customer reference, line items, and shipping address migrate as-is. We flag any orders with null or malformed line items for customer review before import.

Lead Commerce inventory items with SKU, stock levels, and unit cost map to Dolibarr Product2 records. We create Dolibarr Product entries with ref (from SKU), label, description, price, and cost price fields populated. Items with zero or negative quantities that may indicate data quality issues are flagged in the pre-import validation report. Stock levels per warehouse are migrated to Dolibarr's Warehouse Stock module after warehouse records are established.

Lead Commerce warehouse records map directly to Dolibarr Warehouse. Each warehouse record carries a name, address, and description that migrates as-is. We validate that the destination Dolibarr instance has the Warehouse module activated before import, as this module is not enabled by default in a standard installation. Multi-warehouse configurations from Lead Commerce transfer as separate Dolibarr warehouse records with stock levels linked via product-warehouse associations.

Lead Commerce customer records (name, email, phone, address, company) map to Dolibarr Third Party records. We deduplicate by email during the import transform and preserve the customer-to-order linkage so that historical order context attaches to the correct Third Party in Dolibarr. Lead Commerce customers that include a company name are created as Dolibarr Organizations; sole-contact records are created as Dolibarr Contacts linked to the Third Party.

Lead Commerce purchase order records map to Dolibarr Supplier Orders. We separate received lines from open lines during pre-import: received lines represent landed inventory that we map to stock entries against the relevant warehouse; open lines represent supply commitments that become open supplier order lines in Dolibarr. The supplier contact referenced on each PO must exist as a Dolibarr Third Party before PO import begins, so we sequence supplier data first.

Lead Commerce user accounts and role assignments export as a flat list. We map role names from Lead Commerce to Dolibarr permission groups. The destination Dolibarr instance requires users to be created manually by the admin (Dolibarr does not have a programmatic user provisioning API at the Community edition level), so we provide a user import CSV with the correct Dolibarr field mapping that the customer's admin can import via the Tools > Users import wizard.

If Lead Commerce custom apps store structured data in the Lead Commerce database, we identify those data tables during discovery and map them to Dolibarr ExtraFields where the data fits within existing objects. The custom app logic itself (PHP code, workflows, UI extensions) has no migration path and is flagged in the non-migratable inventory. Any custom app data that does not fit the Dolibarr schema is documented as a separate data export for manual re-entry or a custom Dolibarr module build.

Lead Commerce order line items (product reference, quantity, unit price, discount) map to Dolibarr Commandedet lines. We resolve the product reference against the migrated Product records before order import begins. If a Lead Commerce order line references a product that did not migrate (deleted or inactive at source), we create a placeholder product record in Dolibarr and flag it for the customer to resolve post-migration.

Lead Commerce does not expose a documented export for saved reports or historical analytics snapshots. We do not migrate reporting data. As part of the pre-migration checklist, we direct the customer's team to export key reports as PDF before the cutover date. In Dolibarr, the reporting module (if activated) and Dolistore analytics addons provide a fresh reporting environment. We deliver a written inventory of every saved Lead Commerce report with its parameters as a reference for rebuilding in Dolibarr.

Lead Commerce's Custom Apps framework produces application code that is non-portable by design. The application logic, UI extensions, and any custom business rules built in Lead Commerce cannot be extracted or transferred to Dolibarr. We document any custom app data that lives in Lead Commerce's database separately, flag the associated data export for customer review, and note that the application logic must be rebuilt as a Dolibarr module or Dolistore addon as a separate engagement.

Lead Commerce supplier records referenced on purchase orders map to Dolibarr Third Party records of type Supplier. We deduplicate by supplier email or name during the transform. Supplier contact details (name, email, phone, address) migrate to Dolibarr's supplier contact card. The Dolibarr CRM module must be active to create supplier records with contact associations.

Lead Commerce stores per-warehouse stock levels on inventory items. We migrate these as Dolibarr stock movements of type 'import' linked to the relevant warehouse and product. Each stock level entry records the product, warehouse, quantity, and a migration timestamp. We validate that Dolibarr's Warehouse module and Stock module are both active before this phase and that the warehouse records exist in Dolibarr to satisfy the foreign key relationship.