Migrate from Shipedge to Dolibarr ERP

Shipedge Orders map to Dolibarr Commande client (third-party order). Each order carries its omnichannel source (Shopify, Amazon, Walmart), fulfillment status, shipping method, and tracking number. We map Shipedge's order_status and fulfillment_status to Dolibarr's statuts (draft, validated, shipped, closed) and preserve the original marketplace order ID as ext_shipedge_id for reconciliation. Line items migrate with SKU, quantity, and unit price mapped to CommandLineDetail.

Shipedge Products (SKUs with variants, supplier links, barcodes) map to Dolibarr Product records. We extract SKU, product_name, variant_attributes (size, color), and barcode from Shipedge and map to Dolibarr's ref, label, barcode, and the variant attributes to separate product custom fields or as a multi-line description. Supplier links migrate as Product-Supplier price rows in Dolibarr.

Shipedge's warehouse-site-specific inventory with location, lot number, and bin assignment maps to Dolibarr's Stock module. Dolibarr natively supports stock per warehouse if the multi-warehouse module is enabled; otherwise, we consolidate inventory into a single warehouse location. Lot and serial numbers migrate to Dolibarr's lot/serial tracking if the relevant module is activated. Note that Dolibarr lacks Shipedge's bin-level picking optimization; location data migrates as warehouse notes rather than structured bin records.

Shipedge Suppliers map to Dolibarr ThirdParty records with the Supplier flag enabled. Standard fields (name, email, phone, address) migrate directly. Lead times and supplier-specific notes migrate to the ThirdParty's note field or a custom field. Custom Supplier fields vary by Shipedge account configuration; we map only those confirmed present during discovery.

Shipedge Customers map to Dolibarr ThirdParty records with the Customer flag enabled. Billing and shipping addresses migrate as separate addresses linked to the ThirdParty. Order history associations migrate as linked Commande records. Email and phone fields map directly; contact name and company split migrate as Dolibarr expects separate contact persons linked to the ThirdParty if more than one contact exists.

Shipedge Shipment records map to Dolibarr Expedition linked to the originating Commande. Carrier, service level, tracking number, weight, and dimensions migrate as shipment metadata. Dolibarr's Expedition module must be enabled (it is not active by default in all installations). Tracking URLs generate as Dolibarr Expedition lines with carrier reference. Note that Dolibarr does not have native rate-shopping; carrier selection migrates as a data point rather than an automated routing capability.

Shipedge Return Authorizations map to Dolibarr Order records with a return type flag (or separate order status if the customer uses a return status convention) and linked Expedition for inbound receipt. Return reasons and disposition codes (restock, dispose, return to supplier) migrate to order notes or custom fields. Stock returned to inventory generates a Dolibarr StockMouvement with Entree (reception) type linked to the Product and Warehouse. Disposition mappings are documented during scoping.

Shipedge Batch Fulfillment records (v11+ feature) group orders for warehouse picking. Batch number, order count, SKU count, units, and ship method migrate as linked metadata on each Commande record rather than as a standalone object (Dolibarr has no native batch grouping object). We preserve the batch association via a custom field batch_number__c on Commande so that picking context can be reviewed post-migration.

Shipedge Kit configurations (bundle composition, on-the-fly vs. pre-built assembly) map to Dolibarr BOM structures. Component SKUs and quantities migrate as BOM lines under the parent kit product. Kit type (phantom vs. assembled) maps to Dolibarr's BOM assembly type. Customers choosing Dolibarr's Stock module can activate the BOM submodule; if not enabled, kit structures migrate as product descriptions and are not enforced at inventory level.

Shipedge Warehouses map to Dolibarr Entrepot records with address, operating hours, and carrier account associations. If the multi-warehouse module is not enabled in the destination Dolibarr installation, we consolidate warehouse records into a single Entrepot with warehouse name as a note. Carrier accounts (FedEx, UPS, etc.) do not have a native Dolibarr equivalent; we document them for manual reconfiguration in the customer's shipping integration.

Shipedge User accounts (name, email, role, warehouse assignment) map to Dolibarr User records. Authentication credentials (passwords, OAuth tokens) cannot transfer; users must be provisioned fresh in Dolibarr. We export user name, email, and role as a provisioning spreadsheet, and the customer's Dolibarr admin creates accounts before or immediately after cutover. Active vs. inactive status migrates as user status in Dolibarr.

Shipedge Order Rules define automated routing logic (warehouse selection, carrier assignment, split-order conditions) that has no Dolibarr equivalent. We export all active Order Rules during discovery and deliver them as a written inventory document specifying each rule's trigger conditions, actions, and recommended manual implementation in Dolibarr (manual order assignment, warehouse notes, or third-party workflow module). This is typically a one-to-three-day manual exercise depending on rule complexity.