Migrate from Solution ERP to Dolibarr ERP

Account codes, names, and hierarchies transfer cleanly from Solution ERP into Dolibarr's accounting module. Gulf-specific VAT and Services excise tax codes that have no native Dolibarr equivalent require extension development or manual chart-of-accounts mapping. We extract the full tax code catalogue during scoping, build a mapping table to Dolibarr's closest equivalent accounts or VAT product types, and flag any codes with no destination match for the customer's accountant to resolve before import. Active versus inactive account flags map to the active checkbox in Dolibarr's account record.

Customer records including company name, contact details, addresses, and payment terms migrate as Dolibarr Third Party records with the Customer flag enabled. Arabic company names are preserved in UTF-8 encoding throughout the migration; we verify that the destination Dolibarr instance's character set supports full Unicode before import and confirm RTL rendering configuration with the hosting provider if Arabic-language interface is active. Payment terms migrate to Dolibarr's condiciones de pago (payment conditions) lookup.

Vendor master records including tax registration numbers, IBAN and bank account details, and addresses migrate as Dolibarr Third Party records with the Supplier flag enabled. We validate IBAN format against the destination country's banking standards for any vendors outside the Gulf region. Tax registration numbers migrate as a custom field or into the TVA/SIRET equivalent depending on whether the vendor is EU-based or Gulf-based, since tax registration field semantics differ between jurisdictions.

Items with pricing, stock levels, and unit-of-measure hierarchies require unit-of-measure mapping between the two systems as naming conventions differ. Solution ERP's stock quantity and warehouse assignments map to Dolibarr's product stock levels and entrepots. Products that are services rather than physical goods are flagged with the Service type in Dolibarr to bypass stock management. SKU (hs_sku equivalent in Solution ERP) maps to the ref field in Dolibarr Product.

Outstanding payables and receivables require careful date-range scoping around the migration cutoff. We match open invoice numbers from Solution ERP to prevent duplicate creation in Dolibarr and flag any partial payments that span the migration date. Outstanding AR balances post as Dolibarr Customer Invoice records in open status; outstanding AP balances post as Supplier Invoice records. Historical paid invoices are migrated last as closed records to maintain audit continuity without cluttering open aging reports.

Past journal entries transfer on request with full line-item detail. Volume-based chunking applies for large histories (we chunk in batches of 5,000 lines) to avoid memory exhaustion on the migration server. We preserve original posting dates and fiscal periods to maintain audit continuity, and we quarantine historical records older than three to five years separately for data quality remediation before import. Any inconsistent date formats or duplicate ledger entries accumulated through years of manual corrections are flagged in the pre-migration cleaning report.

Project records including budgets, milestones, and cost allocations transfer. Dolibarr's native project module provides basic task and milestone management; construction-specific phases and billing schedules that require advanced cost tracking may need the third-party projetex module or a custom extension. We flag any Solution ERP project fields with no Dolibarr equivalent during scoping and deliver a written list of those fields for the customer's admin to assess against available Dolibarr extensions or for custom development post-migration.

Solution ERP POS transaction logs require reclassification because retail POS entries in Solution ERP often lack the cost-of-goods-sold split needed for accurate financial posting in Dolibarr's accounting module. We identify POS-specific transaction types during discovery, split them into a Customer Invoice record for the sales side and a COGS journal line referencing the appropriate cost account, and apply the destination's COGS accounts during migration. POS cash-drawer and payment-method information migrates to Dolibarr's payment conditions and bank/cash account links on the invoice.

Attached files and records require file-type filtering. We extract document metadata (date, author, document type) separately from binary content because Dolibarr stores documents in a documents directory with a specific naming convention that differs from Solution ERP's structure. Binary file migration is limited to common formats (PDF, DOCX, XLSX, images); legacy binary formats are logged as unsupported and delivered in an archive for manual handling. Document links to Third Parties, Products, and Projects are recreated in Dolibarr's object linkage model.

User accounts and role assignments migrate as Dolibarr User records with role names mapped from Solution ERP's permission structure. Permission structures are fundamentally different between platforms, so we do not map permissions directly. We flag admin-level accounts during scoping for explicit review, and we deliver a written role-matrix showing each Solution ERP role's nearest Dolibarr permission group so the customer's admin can configure access in Dolibarr post-migration. Users without a matching email or login in the destination are placed in a reconciliation queue.

Custom properties on any standard object in Solution ERP are exported as key-value pairs. We map these to Dolibarr's Extra fields module (champs perdus) where the destination field type is supported, and we flag any Solution ERP custom field types (such as Gulf-specific dropdown values or calculated fields) with no Dolibarr equivalent for manual resolution. The customer's admin reviews and activates each extra field in Dolibarr's module configuration before the migration phase begins.

Bank account balances and cash account records migrate as Dolibarr Bank Account records. We apply a migration-date cutoff balance adjustment to reconcile any transactions posted after the export snapshot, and we flag any accounts with a material discrepancy (>1% of stated balance) for the customer's finance team to investigate before finalising. IBAN and SWIFT/BIC codes migrate to the appropriate Dolibarr Bank Account fields with format validation applied.

Asset registers including acquisition dates, depreciation methods, and net book value transfer to Dolibarr's Asset module. We validate depreciation schedules against the destination's tax depreciation rules, particularly for assets originally booked under Gulf tax treatment that may have different depreciation rates than EU or international equivalents. Any assets with partially completed depreciation cycles are flagged for the customer's accountant to confirm the remaining schedule before import.