Migrate from WinMan ERP to Dolibarr ERP

WinMan's integrated financial module exports to Dolibarr's Accounting (Comptabilite) module. Account codes and cost-centre assignments map 1:1 using the account code as the dedupe key. Dolibarr requires the Accounting module to be explicitly activated (it is not in the core download), so we confirm activation during discovery. Multi-entity cost-centre assignments in WinMan map to Dolibarr's analytique (analytical accounting) accounts if the customer has the analytical accounting module enabled.

WinMan Items map to Dolibarr Products with the type (product, service, assembly) set per item category. WinMan product codes map to the ref field, descriptions to label, and the sales price to the price_ttc or price_ht depending on whether the customer uses incoterms and tax inclusion. We deduplicate on product code during import. Inactive WinMan items are flagged for the customer's review before import to avoid carrying legacy dead SKUs into Dolibarr.

WinMan BOMs map to Dolibarr's BOM (Bill of Materials) feature. WinMan's BOM lines (component, quantity per, wastage, operation) map to Dolibarr BOM lines. Dolibarr BOMs support batch manufacturing and kit explode on sales order. We import BOM definitions before any Work Order or sales order referencing them so that the product links are satisfied at import time. BOM import requires the Manufacturing module to be activated in Dolibarr.

WinMan's product configurator generates configured BOMs with feature/option matrices and dependency rules. Dolibarr does not have a native product configurator with rule-based option selection. We explode each WinMan configured product into its component BOM lines as individual Dolibarr Product records linked via the BOM parent relationship, preserving the configuration header in a custom field cfg_source__c and a cfg_options__c text field for manual reconstruction in Dolibarr. This is documented explicitly rather than silently dropped.

WinMan multi-level BOMs (BOM referencing sub-assemblies that are themselves BOMs) map to Dolibarr's nested BOM structure. We preserve the parent-child nesting depth by importing from the deepest sub-assembly upward, ensuring each sub-assembly exists before its parent BOM is created. WinMan routing steps and work-centre assignments do not have a direct Dolibarr equivalent and are stored in custom fields for manual process mapping post-migration.

WinMan Customers map to Dolibarr ThirdParty records in customer mode. Customer code, name, addresses, contact details, credit terms, and multi-currency assignments map directly. WinMan's customer-to-site mapping (multi-site customers) maps to Dolibarr's contact-address hierarchy (one ThirdParty with multiple addresses of type 'delivery' or 'invoice'). We deduplicate on WinMan customer code.

WinMan Vendors map to Dolibarr ThirdParty records in supplier mode. Vendor code, name, addresses, purchasing terms, lead times, and contract references migrate. WinMan vendor pricing agreements and quantity breaks are stored in Dolibarr as SuppliercatalogPrice records associated with the supplier ThirdParty. We map vendor currency assignments to Dolibarr's multi-currency supplier price fields.

WinMan Sales Orders map to Dolibarr Commande (Customer Order). Order lines reference Dolibarr Product records resolved from the WinMan Items import. WinMan order status (open, confirmed, dispatched, closed) maps to Dolibarr statuts: draft, validated, sent, delivered, closed. Pricing migrates with unit price and discount percentage preserved. Open orders are migrated last per WinMan guidance; we capture a snapshot immediately before cutover and define a delta-capture window with the customer to avoid duplicate invoicing.

WinMan Purchase Orders map to Dolibarr CommandeFournisseur (Supplier Order). Line items reference resolved Dolibarr Product records. Where WinMan purchase orders reference configured BOMs, we preserve the item-link by referencing the top-level product; component BOM explosion happens on the manufacturing side. Order status maps similarly to sales orders: draft, validated, received, closed.

WinMan Work Orders with routing steps, labour allocations, and work-centre assignments require a two-part migration. The production header maps to a Dolibarr Project of type 'Manufacturing' with the linked WinMan sales order or BOM as project reference. Routing steps and work-centre assignments are stored as custom fields and task descriptions within the Project, since Dolibarr's project module handles task management but does not natively model work-centre routing. Stock consumption and output are handled via Dolibarr's Stock-Mouvement records at the time of Work Order completion.

WinMan stock levels, bin locations, and warehouse-zone assignments map to Dolibarr Stock records with warehouse association. Batch and serial numbers from WinMan migrate as lot_serial values on Dolibarr Stock product entries. WinMan's real-time stock visibility maps to Dolibarr's stock warehouse reporting. We import current stock snapshots at cutover; live stock movement during the migration window is captured as a delta import at go-live.

WinMan batch and serial traceability links (incoming material batch -> finished goods batch) map to Dolibarr Lot/Serial records with traceability preserved through Stock-Mouvement entries. The traceability graph linking raw material batches to finished goods batches migrates as linked Lot records with a custom traceability_link__c field pointing to the parent Lot. This preserves the recall and compliance reporting capability that WinMan batch traceability provides.

WinMan user-defined fields on standard objects map to Dolibarr ExtraFields (extra parameters). We extract WinMan custom field definitions and their data types during discovery and pre-create matching Dolibarr ExtraField definitions in the destination before data import. Picklist, date, numeric, and text ExtraField types are matched directly. Any WinMan custom fields without a Dolibarr equivalent are flagged for manual entry or a Dolibarr custom module development decision.

WinMan user accounts with role-based permissions export by email match to Dolibarr User records. WinMan roles are mapped to the nearest Dolibarr permission set (read/write for module-level access). WinMan's multi-site user assignments (users scoped to specific sites) map to Dolibarr's warehouse and project user assignments. Users without an email in WinMan are reconciled manually with the customer's Dolibarr admin before import.