Migrate from Omni ERP to Dolibarr ERP

Omni ERP's Chart of Accounts maps directly to Dolibarr's Accounting module with account codes preserved as-is. We extract the fullcoa export from Omni ERP including segment structure (if multi-dimensional), then map each account code to Dolibarr's pcg_type and pcg_subtype categories. Account references in journal lines are remapped by code at import time; if Dolibarr uses a different chart of accounts numbering convention, we apply the remap during the transform step and flag any orphaned journal lines for manual correction.

Omni ERP Customer records with contact hierarchies, addresses, and payment terms map to Dolibarr ThirdParty records with the customer flag set. We preserve parent-child relationships where the source uses a hierarchy; Dolibarr represents these as separate ThirdParty records with a parent_id link. Payment terms migrate to Dolibarr's payment condition module and are attached to the ThirdParty record. Owner/User assignments from Omni ERP are stored as a custom field on the Dolibarr record since Dolibarr's native user-permission model assigns access at the role level rather than per-record ownership.

Omni ERP Vendor records map to Dolibarr ThirdParty records with the supplier flag set. The same address, contact, and payment term mapping logic applies. Vendor-specific fields like W-9 status or tax registration numbers map to Dolibarr's extf field structure or a custom field group created during schema setup.

Omni ERP Items with serial and batch tracking and multi-warehouse costing map to Dolibarr Products with stock management enabled. Serial numbers migrate to Dolibarr's lot/serial tracking if the Dolistore extension is installed; without it, serial-level detail is stored as a custom field note and batch-level lot numbers migrate as Dolibarr lot entries. Multi-warehouse costing from Omni ERP maps to Dolibarr's warehouse-level stock reporting; Dolibarr calculates weighted average cost per warehouse, which may produce small variances from Omni ERP's source costing that we flag for reconciliation. Items without active stock (service items, non-stocked parts) map to Dolibarr Products with the Stock field disabled.

Omni ERP BOMs with multi-level routing, work center assignments, and production order tracking have no native Dolibarr equivalent. Dolibarr has no built-in manufacturing module; the Dolistore marketplace offers a third-party production extension, but it is not part of the standard GPL distribution. We export the full BOM structure (finished good, component items, quantities, scrap rates, work center assignments) as a structured CSV and deliver it alongside the migration as a written BOM inventory document. The customer's admin rebuilds the BOMs in their chosen production module post-migration.

Open vendor invoices from Omni ERP map to Dolibarr FactureFournisseur records. We sequence the AP import after the Chart of Accounts and Vendor records so that account code remapping and vendor lookups are satisfied at insert time. Invoice line items referencing inventory items are mapped to Dolibarr Products. Payment status (unpaid, partial) migrates with the balance amount preserved as the remaining due. If Omni ERP stores multi-currency AP, we capture the transaction-date exchange rate and record the original currency amount and converted base amount separately; Dolibarr's multi-currency AP support is basic and may require manual review of any post-migration discrepancies.

Open customer invoices from Omni ERP map to Dolibarr Facture records. Customer lookups are resolved against the ThirdParty records imported in the vendor/customer phase. Invoice status (draft, validated, unpaid, paid) migrates with the remaining balance preserved. Multi-currency AR is handled with the same date-specific exchange rate capture as AP. Historical paid invoices (for reporting continuity) are imported as paid invoices rather than open AR to preserve the full revenue history in Dolibarr's reporting.

Historical journal entries from Omni ERP map to Dolibarr Accounting with each debit and credit line as a separate entry row referencing the remapped account code. Multi-currency line items store the original currency amount and base currency converted amount; we capture the transaction-date exchange rate from Omni ERP and apply it at import. Entries with complex multi-currency assignments or inconsistent account references in Omni ERP are flagged in a pre-import validation report for the customer's finance team to resolve before posting. Entries that fall outside Dolibarr's fiscal year open period are held in a draft state pending period configuration.

Omni ERP Fixed Asset records including acquisition cost, accumulated depreciation, depreciation method, and asset category map to Dolibarr Assets. Depreciation schedules are preserved as a series of depreciation entries in Dolibarr's asset depreciation module. If Omni ERP uses a depreciation method (declining balance, sum-of-years digits) that Dolibarr does not natively support, we store the method as a custom field on the asset record and create a manual depreciation schedule to replicate the source amortization curve. Asset category maps to Dolibarr's asset classification structure.

Omni ERP department and cost center hierarchies referenced in journal entries, budgets, and user assignments map to Dolibarr Projects as cost center proxies, or to a custom field group if the customer prefers a dedicated cost center structure. We preserve the full department hierarchy and remap IDs against the target org structure. Circular references in department hierarchies are flagged for manual resolution before import. Projects used solely for cost center tracking in Omni ERP are imported as Projects with the is_teampm flag disabled and the cost tracking fields enabled.

Omni ERP user records with role assignments and department affiliations map to Dolibarr User accounts. We map Omni ERP role names to Dolibarr permission groups (Admin, ReadOnly, Standard, etc.). Users whose access scope exceeds Dolibarr's permission model granularity are flagged in the user mapping output with the nearest equivalent Dolibarr permission set. The customer's admin reviews and approves the permission mapping before user records are activated in the production instance.

Documents and file attachments stored within Omni ERP's document management module cannot be exported via the documented CSV workflow. We flag all document attachment records during the scoping audit and deliver a file listing with record-level references so that the customer's IT team can execute a parallel file migration through Omni ERP's UI export or direct database access. Dolibarr's document storage is structured differently (file system under /documents by entity type), so a separate file migration engagement is required for any documents that must be accessible from within Dolibarr post-migration.