Migrate from Fulfil to Dolibarr ERP

Fulfil Sales Orders map to Dolibarr Customer Orders (ThirdParty as customer). Order status, line items, fulfillment state, channel attribution, and shipping details transfer as structured CSV rows matched to Dolibarr's llx_commande and llx_commandedet tables. We resolve the Fulfil customer reference to a Dolibarr ThirdParty ID before order insert to satisfy the foreign key constraint.

Fulfil Items (SKU, description, cost, price, reorder point, bin location) map to Dolibarr Products. Custom fields on the Item object require explicit field-level mapping per tenant. Lot and serial number assignments carry through as Dolibarr stock lot entries. We generate one product row per Fulfil item, with the type field set to 0 (product) or 1 (service) based on the Fulfil item type attribute.

Fulfil Purchase Orders map to Dolibarr Supplier Orders. We sequence PO migration after warehouse stock records are landed, because Dolibarr's receiving workflow ties receipts to the supplier order and inventory location. Open POs with partial receipts carry both the order header and associated receiving lines. Vendor assignment resolves to the Dolibarr ThirdParty ID before order insert.

Multi-warehouse configurations with bin-level location data map to Dolibarr Warehouses. We map each Fulfil location and its associated stock levels as separate inventory snapshots imported into Dolibarr's llx_product_stock table. Bin-level detail in Fulfil that cannot be represented as a Dolibarr Warehouse is noted in the scoping document for manual configuration post-migration.

Fulfil Customers map to Dolibarr Third Parties. Contact details, billing address, shipping addresses, and account-level pricing tiers transfer as structured rows. Custom fields on the Customer object require explicit field-level mapping per tenant. Dolibarr consolidates customers and suppliers into a single ThirdParty object with a Type field (Customer/Supplier/Both), so we set the type value based on Fulfil's customer classification.

Fulfil vendor invoice records in the financials module export to Dolibarr Supplier Invoices. Mapping depends on the destination's chart of accounts structure, which we establish during scoping. Open invoices transfer as unpaid; historical invoices transfer with payment status. We do not migrate paid and fully reconciled invoices unless the customer specifically requests historical financial audit data.

Fulfil stores custom product attributes as extended attributes on Sales Order Lines rather than as a standalone object. We extract these as structured line properties and map them to Dolibarr product variant rows (one variant per attribute combination) or to product_extra fields if the Dolibarr installation has a custom attributes module enabled. The flattening approach is validated during sandbox migration before production import.

Lot tracking and serial number assignments on Fulfil Items carry through as Dolibarr stock lot entries. Each lot is tied to a product and an inventory transaction (receiving or adjustment) at migration time. We preserve traceability by setting lot_number, batch_number, and expiry date from the Fulfil lot record, and linking the lot to the corresponding product stock entry.

Where Fulfil's manufacturing module is in use, work orders, BOMs, and production steps are accessible via API. Complex BOM hierarchies with multi-level assemblies may require manual sequencing in Dolibarr because Dolibarr's BOM module handles single-level bills of materials natively but nests BOMs through production orders rather than through a recursive product structure. We map top-level BOM and work order data; deeply nested assemblies are flagged for manual post-migration configuration.

Financial accounts are exportable from Fulfil but require manual mapping against Dolibarr's chart of accounts. Multi-entity Fulfil deployments (each legal entity with its own chart of accounts) require separate account mapping tables per entity. We collect the full account tree for each entity during scoping, build the manual mapping table with the customer's finance team, and apply it as an account code crosswalk CSV before any transaction records transfer.

Fulfil Owners map to Dolibarr Users. We resolve owners by email match. Any Fulfil Owner without a matching Dolibarr User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Dolibarr's user model is simpler than Salesforce's — users are internal staff, not external contacts, so contact records attached to an owner reference migrate separately as ThirdParty records.

Fulfil fulfillment records map to Dolibarr Shipments. Each shipment carries the linked customer order, shipped items, quantities, carrier, and tracking number. We resolve the order reference to the migrated Dolibarr order ID before shipment insert. Partial shipments from the same Fulfil order become separate Dolibarr shipment records.