Migrate from Standard ERP to Dolibarr ERP

Standard ERP's structured GL chart with parent-child account hierarchy maps to Dolibarr's third-party account directory. We extract account type (asset, liability, equity, revenue, expense), currency assignments, and cost-center tags, then replicate the hierarchy in Dolibarr's Plan_comptable (French PCMN) or a custom chart structure. Account codes and names serve as the dedupe key during import. Multi-company chart segments require one Dolibarr chart per company entity.

Standard ERP Customer records including billing and shipping addresses, payment terms, and contact associations map directly to Dolibarr Third-Party records with the Customer subtype. Customer-specific pricing tiers migrate as custom properties in Dolibarr. We preserve address formats and validate against Dolibarr's country-specific validation rules, flagging any that require post-migration cleanup.

Standard ERP Vendor master records including bank details, 1099 flags, and purchase terms map to Dolibarr Third-Party records with the Supplier subtype. We validate vendor address formats against Dolibarr's country-specific requirements and map Standard ERP payment terms to Dolibarr's Conditions_reglement system. Bank account details migrate to Dolibarr's Rib (RIB/bank account) fields.

Standard ERP Items include inventory, non-inventory, and service variants with BOM linkages. Dolibarr uses a flat Product object with sub-types (stock, service, assembly) and optional BOM through its Manufacturing module. We map inventory items to Dolibarr Products with stock management enabled, service items to Products of type Service, and BOM structures to Dolibarr's Bill of Materials object. Variants in Standard ERP may require manual product-line setup in Dolibarr if the BOM complexity exceeds the native assembly model.

Outstanding Standard ERP invoices, credit memos, and payments are extracted with full aging detail and mapped to Dolibarr's invoices and credit note objects. We match each open document to its corresponding GL entry to ensure balances reconcile. Payment terms and aging buckets align to Dolibarr's Conditions_reglement and Echeancier. Open AR reconciles against the corresponding Customer Third-Party; open AP reconciles against the Supplier Third-Party.

Standard ERP stores closed periods separately from open ones. We extract the full transaction register including journal entries and map them to Dolibarr's Accounting module by posting to the corresponding account codes with original dates and amounts preserved. Closed fiscal periods in Standard ERP may be locked and require temporary reactivation or reconstruction as current-period adjustments in Dolibarr; we flag this during scoping and plan accordingly to avoid post-migration balancing gaps.

Standard ERP job costing links labor, materials, and overhead to specific projects. Dolibarr has a Project module that supports tasks, time tracking, and expense recording but does not have native job-costing phase breakdowns. We map Standard ERP job phases to Dolibarr Project tasks with cost-line entries for labor and materials, preserving phase-level financial breakdowns as task-level expenses. If the customer requires granular phase-level reporting, we recommend a post-migration Dolistore module or manual reporting procedure.

Standard ERP BOM-linked production orders include routing, work-center assignments, and actual vs. estimated costs. Dolibarr's Manufacturing module supports BOM definitions and production orders with stock movements. We transfer the order header and line structure to Dolibarr production orders; work-center routing detail may require manual reconfiguration in Dolibarr's Manufacturing setup since Dolibarr handles work centers differently from Standard ERP's routing model.

Standard ERP stores file attachments in a proprietary internal vault that does not export as standard files by default. We extract vault packages via HAL or direct database queries, producing a file package with filename-to-record-ID mapping built during discovery. In Dolibarr, we associate each extracted file with the corresponding migrated record (Customer, Supplier, Product, or Project) using the filename mapping. Large attachment volumes may require staged transfer with a manifest delivered before the production migration window.

Standard ERP User accounts, roles, and permission sets migrate as a role-mapping exercise in Dolibarr's User management. We map Standard ERP user IDs to Dolibarr User records by email match, assigning Dolibarr's permission groups (Admin, Director, Commercial, etc.) to approximate the source role. HAL-scripted permission extensions that have no direct Dolibarr equivalent are flagged in the discovery report for manual assignment post-migration.

Organizations using HAL to extend Standard ERP's data model create custom fields, workflows, and integrations that have no direct equivalent in Dolibarr's standard objects. We catalog every HAL custom property during discovery, then map each to a Dolibarr Extrafields entry (custom field) on the corresponding Dolibarr object. HAL workflows and integrations that exceed the Extrafields model are documented in the migration handoff as manual procedures or Dolistore module recommendations, quoted as a separate engagement.

Standard ERP handles multi-currency at the transaction level with exchange rate tables and effective dates. Dolibarr's MultiCurrency module stores rates per currency pair with effective dates. We preserve the effective date and rate for every foreign-currency transaction during extraction, normalize them to a consistent base currency for migration, and load them into Dolibarr's currency rate table. At go-live, the customer reviews and updates Dolibarr's current rates against their preferred rate source.