Migrate from metasfresh to Dolibarr ERP

metasfresh Business Partners with partner_type=CUSTOMER map to Dolibarr Third Parties with the Tiers: Customer module enabled and a client checkbox flag. Address data (C_BPartner_Location) maps to Dolibarr's address and contact tables (llx_societe_address). Financial relationship data (payment terms, bank accounts) transfers as reference data into llx_societe_account and llx_societe_remise. The metasfresh is-vendor flag is preserved as a separate Third Party record when the same partner is both a customer and supplier.

metasfresh Business Partners with partner_type=VENDOR map to Dolibarr Third Parties with the Tiers: Supplier module enabled and a fornecedor flag. Vendor-specific fields including purchase payment terms and default warehouse assignment transfer to llx_societe_fournisseur.

metasfresh M_Product records map to Dolibarr llx_product. Products marked as is-stocked map to Dolibarr Product type=1 (storable), while non-stocked items map to type=0 (service). Product categories from M_Product_Category map to Dolibarr llx_product_category. The metasfresh product cost and sales price fields map to llx_product_price for the default price list.

metasfresh M_PricingSystem with M_PriceList and M_PriceList_Version entities map to multiple Dolibarr llx_product_price rows per product. Effective dates from M_PriceList_Version become validity dates on Dolibarr price entries. If metasfresh has customer-specific pricing overrides, these become Dolibarr llx_societe_remise entries linked to the Third Party.

metasfresh C_Order records with doctype=SALES_ORDER map to Dolibarr llx_commande_fournisseur (or llx_commande if using the order-to-invoice workflow). Order lines from C_OrderLine map to llx_commandedet with the product reference and quantity resolved. Document status (draft, in progress, completed, cancelled) transfers directly. The metasfresh C_DocType determines whether this is a sales or purchase order.

metasfresh C_Order records with doctype=PURCHASE_ORDER map to Dolibarr llx_commande_fournisseur. Header-to-line relationships are preserved via the order_id reference. Purchase order totals and currency transfer from the metasfresh C_Currency reference.

metasfresh C_Invoice records (both C_Invoice and C_InvoiceLine tables) map to Dolibarr llx_facture and llx_facturedet. AR invoices link to the Third Party customer record; AP invoices link to the supplier record. The invoice header status and payment terms transfer, and line item totals recompute against the migrated price list to catch any rounding drift.

metasfresh pp_product_bom and pp_product_bomline records map to Dolibarr's BOM module (llx_bom and llx_bom_bomline) if the customer has purchased this module. We inspect the pp_product_bom tables during discovery and include BOM data only when the MRP module is confirmed active and the BOM records are populated. Without the Dolibarr BOM module purchased, we flag this as an excluded deliverable and note the module purchase requirement.

metasfresh C_Project records with C_ProjectLine child rows map to Dolibarr llx_projet and llx_projet_task. Phase and milestone data from metasfresh becomes task hierarchy in Dolibarr. The owning Business Partner reference links the project to the corresponding Third Party in Dolibarr. Time and cost tracking fields map to llx_projet_task_time.

metasfresh C_BP_BankAccount records map to Dolibarr llx_societe_bank linked to the Third Party. IBAN, BIC, and bank name fields transfer directly. Bank accounts are imported after Third Parties so the foreign key reference is satisfied.

metasfresh C_PaymentTerm records (net 30, 2/10 net 30, etc.) map to Dolibarr llx_c_payment_term. Effective date ranges and discount percentages transfer. Payment terms are imported as reference data before any Invoice or Order import so that the foreign key is available on line items.

metasfresh C_TaxCategory and C_Tax records map to Dolibarr llx_c_tva and llx_c_tva. Tax rates tied to geographic zones transfer with effective date ranges preserved. The metasfresh tax rate percentage and tax type (sales vs purchase) determine the Dolibarr taux and applicable type flags.

metasfresh custom fields discovered in AD_Column (custom=Y flag) map to Dolibarr Extra fields per object. We query AD_Column during the discovery phase to enumerate all custom columns per table and include them as additional fields in the export. In Dolibarr, the receiving object must have the extra fields module enabled for the custom data to land.