Migrate from ERP BOS to Dolibarr ERP

ERP BOS customer records map to Dolibarr ThirdParty (societe) with the soptype field set to customer (C). The customer's billing address maps to the address fields in Dolibarr, and credit limits map to credit_note_reason. We preserve the ERP BOS account balance as a reference note and flag accounts with zero activity in the past 24 months for customer-side review before migration to avoid inflating Dolibarr's record count with stale data.

ERP BOS supplier records map to Dolibarr ThirdParty with soptype set to supplier (F). Payment terms, tax registration numbers, and banking details migrate to Dolibarr's supplier-specific fields. Supplier-specific contact persons map to Dolibarr contacts linked to the ThirdParty record. We validate that ERP BOS tax registration values conform to a recognized format before insert to avoid Dolibarr validation errors on import.

ERP BOS Items (both stock and non-stock) map to Dolibarr Product. The ERP BOS SKU becomes product ref, description becomes label, and unit of measure maps to unit_of_measure. Physical stock items use product type = 0 (stockable); non-stock items use type = 1 (service). Cost price from ERP BOS becomes the pmp (weighted average price) field in Dolibarr. We extract the full item custom field schema during scoping and map each to Dolibarr extrafields where the CustomFields module is enabled.

ERP BOS multi-level BOMs with routing steps require flattening for Dolibarr. Dolibarr's standard install handles product kits (multi-unit recipes) but lacks native production routing. We extract the full BOM tree, collapse it to a flat kit structure in Dolibarr (parent product with sub-product lines), and document the original routing sequence in the product's description field. Customers requiring full manufacturing routing in Dolibarr need the production module (community or paid) or a post-migration custom extension.

ERP BOS hierarchical Chart of Accounts maps to Dolibarr's Accounting chart with account codes, descriptions, and classification (Asset, Liability, Income, Expense) preserved. We export the full COA as a structured record set and insert into Dolibarr's accounting_account table. Account code length and hierarchy depth must be validated against Dolibarr's account mask settings before import.

ERP BOS multi-entity ledgers (separate branch or legal entity books) require cross-reference mapping. Dolibarr's multi-company module lets organizations define multiple entities with separate journals. We extract per-entity ledgers from ERP BOS, assign corresponding Dolibarr company codes, and map inter-entity journal entries to elimination holding accounts that your finance team must review and approve before go-live. This is the highest-risk step and requires customer-side sign-off on elimination account treatment.

ERP BOS outstanding payables and receivables migrate to Dolibarr as open customer invoices (半) and supplier invoices (半) with original due dates, amounts, and status preserved. Aged trial balance data is reconciled against the general ledger during scoping; we flag discrepancies and require customer-side resolution in ERP BOS before transfer to prevent Dolibarr from opening with imbalanced AP/AR that affects credit limit calculations and reporting.

ERP BOS general ledger journal entries migrate to Dolibarr Accounting's é尊贤 entries. Each journal line maps account code, debit amount, credit amount, and counterparty. We migrate transaction date, journal code, and piece reference to preserve audit trail. Historical records beyond 24 months are migrated selectively based on the customer's scope; we recommend retaining only records needed for statutory reporting to avoid inflating Dolibarr's database.

ERP BOS bank and cash ledgers are part of the Chart of Accounts structure. We extract bank accounts and cash ledgers separately during scoping, map them to Dolibarr's bank account module (comptes), and set opening balances from the last ERP BOS statement date. Bank transaction history migrates as journal entries linked to the bank account.

ERP BOS tax codes and rates (jurisdiction-based VAT, sales tax) map directly to Dolibarr's tax configuration table (c_tva). We extract the full tax code table including rate percentages, applicable jurisdictions, and reverse-charge flags, and insert them into Dolibarr before any invoice or journal migration to ensure tax calculations are correct from day one.

ERP BOS service records (customer enquiry tracking and opportunity management from the Service Manager module) split across Dolibarr objects based on record type. Open service tickets with active status migrate to Dolibarr Intervention (llx_rh_evenement or the Service module if enabled). Opportunities map to Dolibarr Project with a commercial link. Each migrated record is associated with the corresponding ThirdParty using the customer account lookup resolved during the earlier object mapping phase.

ERP BOS document management module stores binary files (invoices, purchase orders, images, signed documents) linked to transaction records. Our migration pipeline extracts document metadata (filename, document type, linked entity reference) and produces a file-index CSV, but binary blobs do not transfer through the data pipeline. We coordinate the file-index output alongside the data migration so your team can execute a parallel file transfer via SFTP, rsync, or the Dolibarr document upload interface. This step is executed independently to avoid timeout issues with large attachment volumes.