Migrate from Unit4 ERP to Dolibarr ERP

Unit4 Customer records hold billing and delivery addresses, payment terms, and tax registration. These map to Dolibarr Third Party records with contact sub-records for individual points of contact. Credit limits and custom fields migrate into Dolibarr Additional Fields. We resolve any customer address duplicates during transformation using postal code and company name as a dedupe key.

Unit4 Supplier master data includes bank details, W-9/W-8 status, and multi-address support. These map to Dolibarr Third Party records with the Supplier flag enabled. Bank details migrate to Dolibarr's supplier bank account fields. We preserve tax registration numbers in Additional Fields on the Third Party record.

Unit4's multidimensional account structures with cost centres, departments, and projects as natural posting axes require flattening into Dolibarr's standard double-entry chart. We discuss with the customer whether to preserve cost centre as a Dolibarr project tag, map to Additional Fields, or accept a simplified account hierarchy. Account type, posting controls, and currency settings map to Dolibarr account type and the multi-currency module if enabled.

Unit4 Items with GL mapping, cost price, sales price, and stock control flags map to Dolibarr Product and Service records. Complex Unit4 pricing matrices that include cost-centre or project dimensions are simplified to flat price lists in Dolibarr unless the customer activates Dolibarr's multi-price module. We map Unit4's item type (stock vs service) to the corresponding Dolibarr product type during transformation.

Unit4 General Ledger accounts with account type, posting controls, and currency settings map directly to Dolibarr Account records. Account codes and descriptions transfer directly. Posting rules that reference cost centres or departments in Unit4 are flagged for the customer to reconfigure in Dolibarr's accounting setup because Dolibarr does not enforce posting-rule dimensional constraints in the same way.

Outstanding Unit4 invoices, credit memos, and payment applications carry forward as open Dolibarr Invoice records. Document headers and line items map with due dates, amounts, and currency preserved. We set Invoice status to unpaid/open and preserve the original invoice reference as an external reference field for audit. Payment terms from Unit4 map to Dolibarr payment condition fields.

Posted Unit4 journal entries transfer as locked Dolibarr Accounting Entry records. Posting dates, source references, and user stamps migrate to preserve the audit trail. Each journal line maps to a debit or credit line in Dolibarr's accounting module. We flag any journal entries that reference cost centres or departments for manual verification because Dolibarr's accounting entries do not carry dimensional tags.

Unit4's country-specific tax matrices with rates, jurisdictions, and posting rules map to Dolibarr's tax setup module. We create Dolibarr tax codes for each Unit4 rate, set the applicable third-party type (customer, supplier, both), and configure posting account mapping. Any jurisdiction combinations that do not have a direct Dolibarr equivalent are flagged during scoping for manual review, particularly for multi-country organizations.

Unit4 Asset master records include depreciation schedules, cost centre assignments, and insurance values. We map to Dolibarr Asset records with depreciation method and accumulated depreciation preserved. Unit4 and Dolibarr depreciation methods may differ per asset class; we align on a conversion approach per asset category during discovery and document any depreciation basis adjustments for the customer's accountant to verify post-migration.

Unit4 document attachments against transactions and master records are extracted and re-associated in Dolibarr's document management (GED) module. File-size and format restrictions in Dolibarr may require file conversion for formats Dolibarr does not natively render. We map document links to the corresponding Dolibarr record ID and preserve the original file name and upload date for traceability.

Unit4 bank account masters with currency, account type, and reconciliation settings map to Dolibarr Bank Account records. Opening balances migrate as the first journal entry on the account, and we reconcile them post-migration. Unit4 bank reconciliation data (matched transactions, reconciliation dates) does not have a direct Dolibarr equivalent; we preserve transaction details and document the reconciliation approach for the customer's finance team.

Unit4 HCM records hold employment history, compensation, job titles, and department assignments. Employee records map to Dolibarr User records with the Employee flag enabled. Effective-dated changes in Unit4 require careful sequencing; we migrate the current active employment state and flag historical changes for manual review if required for compliance. Department and job title map to Dolibarr Additional Fields or the project-based cost-centre proxy if the customer has enabled Dolibarr's project module.

Unit4 Projects are the primary work-identification layer with WBS elements, cost objects, billing rates, and resource assignments. Project structures are heavily customer-configured in Unit4 and require a detailed mapping strategy established during discovery. We map project headers, tasks, time tracking, and cost budgets to Dolibarr Project records, and flatten Unit4's multi-dimensional cost-centre assignments into Dolibarr project categories or Additional Fields unless the customer activates a cost-tracking extension.

Unit4 Grant management handles donor restrictions, fund balances, and reporting for nonprofits and public-sector bodies. We map grant codes, funding allocations, and spend-versus-budget records to Dolibarr Project records with Additional Fields carrying the grant code, donor, funding amount, and spend tracking columns. Nonprofits and public-sector organizations should know upfront that Dolibarr lacks a native multi-fund ledger, so multi-fund organizations must redesign their grant tracking and reporting approach to fit Dolibarr's flat project structure.

Unit4 stores years of journal history in relational tables. Bulk extraction requires GCON4 MFL or direct SQL access. We scope the date range during discovery, discussing whether to migrate full history or a configured window (typically the current and prior fiscal year for reporting continuity). Very large histories (over 100,000 lines) are chunked and loaded in batches with row-count reconciliation between each batch.