Migrate from Relic ERP to Dolibarr ERP

Relic ERP's customer and supplier records map to Dolibarr's ThirdParty object, which uses a single table for both types distinguished by the Tiers type field (Customer or Supplier). We preserve the customer or supplier classification from Relic ERP, map address fields to Dolibarr's address fields (address, zip, town, country), and preserve any payment term references as text in the notes field. If Relic ERP stores separate customer and supplier taxonomies, we create two distinct ThirdParty subsets during import.

Relic ERP products and services map to Dolibarr Product records. Product type (stockable, service, assembly) translates from Relic ERP's classification. Units of measure, minimum stock thresholds, and descriptive fields migrate as-is. If Relic ERP stores product variants or sub-assemblies, we flatten them into separate Product records since Dolibarr's base product model does not natively support variant trees without the Variants module extension.

Relic ERP production bills of materials (BOMs) map to Dolibarr's BOM module if the customer activates it, or to Product linked records if the manufacturing module is not in scope. We map each BOM line item to a Dolibarr BOM line with the correct quantity and unit. Products referenced in BOMs must import before BOMs to satisfy referential integrity.

Relic ERP quotations map to Dolibarr Commercial Proposals (Propale). The proposal status, line items with pricing and tax rates, and validity dates migrate. We preserve the quotation reference as Dolibarr's ref_ext for cross-system audit. If Relic ERP stores version history on a quotation, the most recent version migrates as the active proposal.

Relic ERP sales orders map to Dolibarr Customer Orders. Order status (draft, validated, shipped, closed) maps to Dolibarr's statuts. Line items including product, quantity, unit price, and tax move directly. The linked customer ThirdParty must resolve before order import, so we run customer import as a prerequisite phase.

Relic ERP purchase orders map to Dolibarr Supplier Orders. Line items, supplier reference, and expected delivery dates migrate. Dolibarr's supplier order workflow includes receipt and invoice reconciliation steps that Relic ERP may not have; we map status conservatively and note that the customer reconciles the workflow states post-migration.

Relic ERP sales and purchase invoices map to Dolibarr Facture records. We handle date field preprocessing to strip any timestamp component, since Dolibarr's import expects YYYY-MM-DD format and rejects YYYY-MM-DD HH:MM:SS with a validation error (GitHub issue #24700). Invoice status, payment terms, and linked customer or supplier references migrate. If Relic ERP tracks partial payments against an invoice, we create corresponding Dolibarr payment records.

Relic ERP payment records map to Dolibarr Payment records linked to the corresponding Facture. Bank reconciliation entries from Relic ERP map to Dolibarr Bank Account transactions. We preserve payment method, amount, date, and the link to the originating invoice so that Dolibarr's accounts receivable aging reports reflect the migrated history.

Relic ERP projects and work orders map to Dolibarr Project records. Project status, dates, and descriptions migrate. If Relic ERP stores task breakdowns, we map them to Dolibarr Task records under the project. Billable flag and budget fields map to equivalent Dolibarr project fields. Project associations visible directly on invoice pages in Relic ERP translate to Dolibarr's element_link mechanism.

Relic ERP employee records map to Dolibarr User accounts if the HR module is activated. Employee contact information, department, and role migrate to Dolibarr User fields. If Relic ERP stores salary or attendance data, we flag these as requiring separate HR module setup and do not migrate them as standard employee records because Dolibarr HR handles these differently.

Relic ERP custom fields require Dolibarr's extra fields to be pre-created with matching data types before record import. We extract the Relic ERP custom field schema during discovery, define equivalent Dolibarr extrafield definitions (type, length, dropdown options), and deploy them into Dolibarr before any data phase begins. Without this pre-creation step, Dolibarr silently ignores unknown custom field columns during CSV import.

Relic ERP custom reports have no direct Dolibarr equivalent because report definitions are platform-specific. We deliver a written report inventory listing every Relic ERP report with its filters, groupings, and output format. The customer's admin rebuilds each report in Dolibarr's built-in report builder or exports to Excel for ad-hoc analysis. Historical report outputs are exported as PDFs and archived alongside migrated data.