Migrate from Industry Software to Dolibarr ERP

Industry Software Customer records map to Dolibarr ThirdParty objects with the Client checkbox enabled. The Industry Software customer code becomes the ThirdParty code field for dedupe. Address, phone, email, and payment terms migrate to ThirdParty fields. If Industry Software stores multiple contacts per customer, additional contacts migrate as Dolibarr Contact objects linked to the parent ThirdParty via the contact type field.

Industry Software Vendor records map to Dolibarr ThirdParty objects with the Supplier checkbox enabled. Vendor code, address, and payment terms migrate directly. If Industry Software uses separate contact records for vendors, these map to Dolibarr Contact objects linked to the supplier ThirdParty. Vendor-specific fields such as tax ID or DUNS number migrate to the ThirdParty extra fields if the DoliStore对应的module is enabled.

Industry Software product and SKU records map to Dolibarr Product objects. Product type (stockable, service, inventory) maps from the Industry Software inventory flag. Unit of measure, barcodes, and warehouse assignment migrate to Dolibarr Product fields and MultiPrice module if multiple price lists exist. Cost price and sales price migrate to the Product cost and selling price fields.

Industry Software inventory levels per warehouse map to Dolibarr Stock records under the Warehouse module. Warehouse location in Industry Software becomes a Dolibarr Warehouse. Stock quantities per product per warehouse migrate as Stock Movement records linked to the product and warehouse. Valuation methods differ between platforms; Dolibarr uses average weighted cost or PMP, which we align with during scoping if the customer requires cost-of-goods-sold accuracy.

Industry Software open Accounts Payable records map to Dolibarr Supplier Invoice objects in draft or unpaid status. The invoice number, vendor reference, due date, amount, and line items migrate. Payment terms from the Vendor record carry forward. We flag any partially paid invoices that require allocation of partial payments, as Dolibarr handles partial payments at the payment register level rather than at the invoice level.

Industry Software open Accounts Receivable records map to Dolibarr Customer Invoice objects in draft or unpaid status. Invoice number, customer reference, due date, amount, and line items migrate. Payment terms from the Customer record carry forward. Historical paid invoices are migrated as closed invoices only if the customer requests full transactional history; otherwise, we migrate open AR items only and archive closed history in CSV format.

Industry Software Chart of Accounts records map to Dolibarr Accounting Account entries under the Accounting module. Account number, name, and type (asset, liability, equity, income, expense) migrate to Dolibarr's PlanComptable-compatible account records. If Industry Software uses a non-standard account code structure, we apply a transformation during load to match the target accounting chart. Account validation rules in Dolibarr are reviewed post-migration to ensure debit/credit direction aligns with the original system's logic.

Industry Software customer payment records map to Dolibarr Payment objects linked to the corresponding Customer Invoice. The payment date, amount, and payment method (cash, check, bank transfer) migrate. Each payment creates a Bank Account transaction record in Dolibarr for reconciliation. If Industry Software records partial payments against a single invoice, we create multiple payment records to match the granularity.

Industry Software vendor payment records map to Dolibarr Supplier Invoice Payment objects linked to the corresponding Supplier Invoice. The payment date, amount, and payment method migrate. Bank Account transaction records are created for each payment to support Dolibarr's bank reconciliation feature.

Industry Software custom fields tied to its vertical-specific modules may not have direct Dolibarr equivalents. We create Dolibarr extrafields on the corresponding standard objects (ThirdParty, Product, Facture) during the schema phase, using text, numeric, or select field types as appropriate. Fields with no viable mapping are flagged in the migration report and listed for the customer's admin to evaluate post-migration. Complex custom objects that exist only in the Industry Software vertical module are archived as CSV exports rather than migrated, as Dolibarr has no native custom object framework without third-party modules.

Industry Software open sales orders map to Dolibarr Customer Orders. Order number, customer reference, order date, and line items migrate in draft status. If Industry Software tracks order status separately, we map to the equivalent Dolibarr order status (draft, validated, in progress, shipped, closed). Completed orders are migrated as closed orders only if transactional history carryover is requested during scoping.

Industry Software open purchase orders map to Dolibarr Supplier Orders. PO number, vendor reference, order date, and line items migrate in draft status. Status mapping mirrors the customer order logic. Completed purchase orders are migrated as closed records only if explicitly requested.