Migrate from eCommerce Pro to Dolibarr ERP

eCommerce Pro Products map to Dolibarr Product records. The product title becomes Dolibarr's label, the SKU maps to ref, and description maps to the description field. eCommerce Pro variants (size, color, material) are flattened into separate Dolibarr Product records because Dolibarr does not have a native attribute-driven variant matrix; we use the Module Builder to create a product_subitem relationship if the variant count exceeds 200 and the customer requires a parent-child structure. Multi-language descriptions are imported as separate Dolibarr description entries per language module if activated.

eCommerce Pro product categories map to Dolibarr Categories (categories table). The category tree hierarchy is preserved by setting parent_id to the Dolibarr Category of the parent. Categories are imported before Products so that the category lookup is satisfied at product import time.

eCommerce Pro Customer records map to Dolibarr Third Party records with the Client checkbox enabled. The customer's email maps to email, first name and last name map to the name fields (or the full name splits by space if a first-last convention is detected), and phone maps to phone. Customer addresses map to separate Dolibarr Address records linked via the fk_socaddr foreign key. acceptsmarketing and account creation timestamps are stored in custom fields that we configure via Module Builder before import.

eCommerce Pro Orders map to Dolibarr Order (Commande) records. The order number becomes the ref, order status maps to Dolibarr's statuts (DRAFT, VALIDATED, SHIPPED, CLOSED, CANCELED), and the creation timestamp maps to date_creation. Order line items are imported via the CommandLineFournisseurDistant table or mapped CSV import with fk_product resolved to the imported Product record. Payment status from eCommerce Pro (paid, pending, refunded) maps to Dolibarr's Facture (Invoice) records created from the Order.

eCommerce Pro Fulfillment records with tracking numbers and carrier information map to Dolibarr Shipment records. The shipment is linked to the corresponding Dolibarr Order via fk_commande. Tracking URLs and carrier names are stored in Dolibarr's tracking_number and tracking_url fields if the Expedition module is activated. Historical fulfillments are replayed as closed Shipment records.

eCommerce Pro inventory quantities per warehouse/location map to Dolibarr Stock Movement records. Multi-warehouse setups require us to configure Dolibarr warehouses before migration and map each eCommerce Pro location to the corresponding Dolibarr warehouse_id. Stock quantities are imported as Stock Mouvement records (type = input for stock_on_hand) rather than direct quantity writes to prevent triggering unwanted stock alerts. Post-migration, we recommend a weekly reconciliation report comparing eCommerce Pro stock to Dolibarr stock per NextGestion's guidance on aligning references first and running weekly reconciliation.

If eCommerce Pro generates invoices, they map to Dolibarr Facture records. The invoice number maps to ref, the total amount maps to total_ht (net) and total_ttc (gross with tax), and the status maps to Dolibarr's statut (DRAFT, VALIDATED, PAID, CANCELED). VAT amount maps to total_tva. Payments received on the invoice map to Dolibarr Payment records linked via fk_paiement.

eCommerce Pro discount codes (percentage, fixed amount, buy-X-get-Y) map to Dolibarr's Prix Special (special price) rules or the Discount/Promotion module if installed. Percentage discounts map directly; tiered quantity discounts are flattened into multiple Prix Special entries per quantity threshold. Buy-X-get-Y rules have no direct Dolibarr equivalent and are flagged for manual rebuild using Dolibarr's Module Builder or a third-party promo module.

eCommerce Pro product images migrate to Dolibarr Product documents (type = image). We validate image URLs, optionally re-host assets to the Dolibarr-hosted file system, and link them to the corresponding Product record via the document_dir and ref_content fields. Variant images are linked to the corresponding variant Product record.

eCommerce Pro shipping methods (carrier name, estimated delivery days, rate) map to Dolibarr Carrier records. The carrier name maps to nom, and shipping cost maps to price if the customer uses Dolibarr's expedition module for order fulfillment.

eCommerce Pro tax codes and nexus settings require manual reconfiguration in Dolibarr Admin > Setup > Tax. Dolibarr's tax engine has its own rules engine independent of source tax mappings. We export the source tax configuration as a written table (tax code, rate, applicability) for the customer's admin to recreate in Dolibarr's Setup > Tax menu.

eCommerce Pro Enterprise custom objects migrate to Dolibarr entities created via Module Builder. We pre-define the entity schema in Dolibarr's Module Builder (including all custom fields, foreign keys, and validation rules) before any data import. The customer's Dolibarr developer or a Dolibarr partner implements the Module Builder template; FlitStack AI configures the data mapping to the generated table. Custom object migration is scoped separately from standard object migration because of the schema-first requirement.