ERP migration

Migrate from Acumatica to Dolibarr ERP

Field-level mapping, validation, and rollback between Acumatica and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.

Acumatica logo

Acumatica

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

12 of 13

objects map 1:1 between Acumatica and Dolibarr ERP.

Complexity

BStandard

Timeline

5-8 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Dolibarr ERP
Acumatica

Overview

What this migration involves

Acumatica and Dolibarr occupy different positions in the ERP landscape. Acumatica is a cloud-native, multi-tenant ERP with sophisticated customization (UDFs, extension DACs, Generic Inquiries), per-tier API rate limits, and a license model that scales by suite rather than by user. Dolibarr is an open-source, PHP-based ERP and CRM with a modular plugin architecture, a flat single-entity data model, and a CSV-import wizard that loads one table at a time. Migrating from Acumatica to Dolibarr means decomposing a normalized, multi-tenant relational schema into Dolibarr's simpler flat entity structure, activating the correct Dolibarr modules before importing, and handling Acumatica's custom fields and linked-note tables as separate extraction passes. We do not migrate workflows, automations, Acumatica Report Designer reports, or Generic Inquiries as code; we deliver a written inventory of these objects for the customer's admin to rebuild in Dolibarr.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Acumatica logo

Acumatica

What's pushing teams away

  • A steep learning curve and complex initial setup frustrate new users, with the report designer drawing particular criticism for its unintuitive interface.
  • Missing features force reliance on customizations or add-ons — a 2023 survey shows nearly a quarter of reviewers cite feature gaps as a pain point.
  • Implementation timelines stretch to 6-12 months for complex deployments, creating a significant resource commitment before any productivity return.
  • The difficult and overwhelming setup experience leads some companies to seek alternatives that offer faster time-to-value.
  • Integration with e-commerce and third-party platforms requires custom development effort that many SMBs underestimate during vendor selection.

Choosing

Dolibarr ERP logo

Dolibarr ERP

What's pulling them in

  • Free open-source core with no per-user license fee makes it the lowest-cost entry point for small teams needing ERP and CRM in one package.
  • Self-hosted deployment gives full data ownership and eliminates vendor lock-in, especially attractive to businesses with compliance requirements.
  • Modular architecture means teams enable only the features they use, keeping the interface uncluttered and reducing learning curve.
  • Fast installation with no technical knowledge required — one reviewer set up multiple businesses in minutes using their own hosting.
  • Active community forum and marketplace of third-party add-ons provide support and extension options without mandatory subscription costs.

Object mapping

How Acumatica objects map to Dolibarr ERP

Each row shows how a Acumatica object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Acumatica

Business Account

maps to

Dolibarr ERP

Third Party

1:1
Fully supported

Acumatica Business Accounts map to Dolibarr Third Parties (type Societe or Contact). Acumatica's AccountClass (Customer/Vendor/Both) maps to Dolibarr's Client and Fournisseur flags on the Third Party. Address, phone, email, tax ID, and payment terms map directly. Multi-tenant CompanyID isolation is enforced during extraction so that records from the correct tenant are mapped to a single Dolibarr instance.

Acumatica

Vendor

maps to

Dolibarr ERP

Third Party (Supplier)

1:1
Fully supported

Acumatica Vendors map to Dolibarr Third Parties with the Fournisseur flag enabled. AP settings, tax categories, and payment terms map to Dolibarr's payment term and bank account fields on the Third Party. Vendor-specific custom fields (UDFs on Vendor DAC) require pre-discovery via Acumatica's schema endpoint and manual configuration of matching Extra fields in Dolibarr before migration.

Acumatica

Inventory Item (Stock/Non-Stock)

maps to

Dolibarr ERP

Product

1:1
Fully supported

Acumatica Inventory Items map to Dolibarr Products. Stock items carry warehouse-specific quantity data (AvailabilityQty) that migrates to Dolibarr's warehouse stock report if the Stock module is activated. Unit of measure, item category, cost method (Standard/Average/FIFO), and the stock/non-stock flag map to Dolibarr's Product type, nature, and cost accounting fields.

Acumatica

Chart of Accounts (GL Account)

maps to

Dolibarr ERP

Account (Accounting plan)

1:1
Fully supported

Acumatica GL Accounts map to Dolibarr Accounting accounts. Account class, type, subaccount mask, and active/inactive status migrate to Dolibarr's account category, type, and active flags. Subaccount segmentation in Acumatica (subaccount mask defines segment count and length) must be flattened or restructured for Dolibarr's flat accounting plan. We flag this for the customer's accountant to validate the chart restructuring before migration.

Acumatica

Project

maps to

Dolibarr ERP

Project

1:1
Fully supported

Acumatica Projects map to Dolibarr Projects if the Project module is activated. Project hierarchy, budget data, tasks, and employee assignments migrate as Dolibarr Project tasks and time tracking entries. Project attributes and custom fields require manual Extra field setup in Dolibarr before data load. Note that Dolibarr Projects lacks the advanced change-order and project-billing workflows available in Acumatica's Project Accounting module; we document the gap for the customer.

Acumatica

Sales Order

maps to

Dolibarr ERP

Customer Order

1:1
Fully supported

Acumatica Sales Orders map to Dolibarr Customer Orders (with the Orders module activated). Line items, fulfillment details, and document status (quote, sales order, partially shipped, shipped, invoiced) migrate to Dolibarr's order lines with product references resolved to the migrated Product records. Tax calculation settings on Acumatica customers and items are translated to Dolibarr tax rules and must be reconfigured post-migration.

Acumatica

Purchase Order

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

Acumatica Purchase Orders map to Dolibarr Supplier Orders. Vendor reference, line items, receipt links, and amendment history migrate as Dolibarr order lines and reception records. Receipts and amendments are separate schemas in Acumatica and map to Dolibarr receptions linked to the supplier order. Document status maps to Dolibarr's order status workflow (draft, validated, approved, received).

Acumatica

AR Invoice

maps to

Dolibarr ERP

Customer Invoice

1:1
Fully supported

Acumatica AR Invoices migrate to Dolibarr Customer Invoices. Open invoices carry payment schedules and aging data; historical invoices migrate as closed records. Tax, payment terms, and aging schedules map to Dolibarr's invoice lines and due date settings. Note that Dolibarr's invoice numbering is controlled by the fiscal year template; we coordinate the numbering sequence to avoid conflicts with existing Dolibarr documents.

Acumatica

AP Invoice

maps to

Dolibarr ERP

Supplier Invoice

1:1
Fully supported

Acumatica AP Invoices map to Dolibarr Supplier Invoices with the same mapping logic as AR invoices applied to the supplier side. Payment terms, tax categories, and GL allocation from Acumatica's distribution table migrate to Dolibarr's invoice lines and accounting account assignments.

Acumatica

Employee

maps to

Dolibarr ERP

User / Third Party (Contact)

1:1
Fully supported

Acumatica Employee records map to Dolibarr Users (for system access) and optionally to Third Parties (for HR-related records such as sick leave and expense reports if the HR module is activated). Employment status, department, job title, and earning codes migrate. Effective-dated compensation rows migrate as separate entries.

Acumatica

Warehouse / Location

maps to

Dolibarr ERP

Warehouse

1:1
Fully supported

Acumatica Warehouses with bin structures map to Dolibarr Warehouses. Multi-warehouse configurations are preserved with location-specific inventory assignments on items. Bin structures in Acumatica do not have a direct Dolibarr equivalent; we map warehouse-level stock only and flag the bin-level detail for manual reconciliation.

Acumatica

Note

maps to

Dolibarr ERP

Note / Attached Document

1:1
Fully supported

Acumatica Note records store entity-linked text in the Note table with NoteID as the key. We extract Note text, EntityID, and EntityType and map them to Dolibarr Notes attached to the corresponding migrated Third Party, Product, or Project record. Dolibarr stores attachments in /documents/ with database links; we extract NoteDoc binaries from Acumatica and re-link them as Dolibarr attachments on the same entity.

Acumatica

Tax Category / Zone

maps to

Dolibarr ERP

Tax / VAT

lossy
Fully supported

Acumatica tax categories, zones, and rules migrate to Dolibarr Tax and VAT setup as configuration data rather than records. Tax rules in Acumatica use customer and item tax settings combined with zone-based rates; Dolibarr uses a simpler tax model with taxes assigned per product/category and per supplier/customer. We deliver a tax mapping table and the customer configures Dolibarr's tax rules before the invoice migration phase begins.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Acumatica logo

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Dolibarr ERP logo

Dolibarr ERP gotchas

High

Foreign key constraint errors on cross-distribution database restore

High

SQL injection vulnerabilities in version 9.0.1

Medium

Custom fields stored as JSON in extraoptions require field-by-field deserialization

Medium

Decimal precision and rounding configuration affects price fields

Low

No native iOS/Android app forces reliance on browser

Pair-specific challenges

  • Acumatica multi-tenant extraction requires explicit CompanyID scoping

    Acumatica's multi-tenant architecture uses CompanyID on every table and a CompanyMask bitmask for shared records. Every extraction query must include the correct tenant filter or data from the wrong company contaminates the export. We require the tenant ID during scoping and apply it as a filter on every query. If the customer runs multiple subsidiaries in separate Acumatica tenants, each requires a separate migration scope and Dolibarr instance or a post-migration consolidation strategy because Dolibarr does not natively support multi-entity isolation.

  • Dolibarr imports are table-by-table CSV; there is no native bulk REST import

    Dolibarr has no REST or Bulk API equivalent to Acumatica's web services. Data loads through the built-in CSV import wizard (menu: Tools > Mass imports) which processes one entity type at a time and must be preceded by the correct module activation. We sequence imports in strict dependency order: Third Parties before Invoices, Products before Orders, Users before anything that assigns an Owner. If a module is not activated, its import option is absent from the menu. Dolibarr's PHP execution time and memory limits on shared hosting can also cause large file imports to fail mid-load, requiring a split-and-resume strategy.

  • Acumatica user-defined fields require separate discovery and Dolibarr Extra field pre-configuration

    UDFs in Acumatica are stored in extension DACs under a 'custom' namespace and are not visible in the standard API entity schemas. The Acumatica community documents that submitting multiple UDF updates as separate nested objects causes only one field to update, which is a common mistake in data extraction. We discover all UDF definitions via the entity schema endpoint before building field mappings, then manually configure matching Extra fields in Dolibarr (Setup > Various > Extra fields per entity) before importing any records that carry those custom values.

  • Dolibarr's document numbering is fiscal-year-based; Acumatica sequences may conflict

    Dolibarr generates document numbers using a template that includes the fiscal year (AY format). If Acumatica uses a non-year-prefixed or alphanumeric numbering scheme for invoices, orders, or projects, the migration must reconcile numbering sequences before go-live to avoid duplicate-key errors or numbering gaps. We extract the highest used number per document type from Acumatica and configure Dolibarr's sequence to start beyond that value.

  • Dolibarr lacks a direct equivalent to Acumatica's Generic Inquiry and Report Designer

    Acumatica's Generic Inquiries (saved searches) and Report Designer are custom reporting constructs that have no direct Dolibarr equivalent. Dolibarr ships with predefined report templates per module and allows list exports to CSV, but complex multi-table queries built as Generic Inquiries in Acumatica must be rebuilt as custom PHP queries or third-party reporting integrations in Dolibarr. We extract the Generic Inquiry definitions from Acumatica's GI schema and deliver them as written specifications for the customer's Dolibarr administrator or a Dolibarr developer to implement.

Migration approach

Six steps for a successful Acumatica to Dolibarr ERP data migration

  1. Scoping and Acumatica license audit

    We audit the Acumatica instance across the licensed modules, active UDF definitions, custom DAC extensions, and API rate limits visible in the License Monitoring Console (SM604000). We confirm the CompanyID for the target tenant, count records per entity (Business Accounts, Vendors, Inventory Items, GL Accounts, Projects, Orders, Invoices), and identify any locked or voided documents. The output is a written scope document with record counts, module activation checklist for Dolibarr, and a rate-limit-safe extraction schedule that respects the API concurrency cap of the licensed tier.

  2. Dolibarr module activation and schema pre-configuration

    We activate the required Dolibarr modules (Third Parties, Products, Stock, Projects, Orders, Invoices, Accounting, HR/Employees, etc.) in a staging Dolibarr instance before any data import. We configure Extra fields to match the discovered Acumatica UDF inventory so that custom field values have a destination. We set the accounting plan template, tax rules, payment term defaults, and document numbering sequences. This phase cannot run in parallel with extraction because Dolibarr's import wizard is unavailable until each module is activated.

  3. Data extraction from Acumatica with CompanyID isolation

    We extract from Acumatica in entity-dependent batches, applying the CompanyID filter on every query. Notes and attachments are extracted from the Note and NoteDoc tables separately and linked to entity records by EntityID and EntityType. We run the extraction in dependency-aware batches: Business Accounts and Vendors first, then Inventory Items, then GL Accounts, then Projects, then transactional records. We respect the API rate limit and run concurrent request throttling to avoid mid-extraction throttling on lower license tiers.

  4. Transformation and Dolibarr CSV preparation

    We transform extracted records into Dolibarr's CSV format per entity type, resolving Acumatica foreign keys (such as customer ID on an order) to their migrated Dolibarr IDs. We split compound Acumatica fields (such as combined address fields) into Dolibarr's structured address format. UDF values are written to the Dolibarr Extra field columns. We produce one CSV per entity and run a row-count reconciliation against the Acumatica source before loading.

  5. Staged CSV import and reconciliation

    We load CSVs into the staging Dolibarr instance in strict dependency order: Third Parties first (required for all transactional records), then Products (required for order lines), then Users/Employees, then Projects, then Orders, then Invoices, then Notes and attachments. Each phase emits a reconciliation report comparing imported row count against the extracted CSV row count. We run the Dolibarr /install/repair.php repair script after loading to check for orphaned links and missing fields, and document any records that failed to import with their error codes.

  6. Production migration, cutover, and post-migration handoff

    We run the production migration into the live Dolibarr instance after sign-off from the staged reconciliation. We freeze writes in Acumatica during the cutover window, run a final delta extraction of any records modified during migration, load the delta, and disable the Acumatica API user. We deliver a written inventory of Acumatica Workflows, Generic Inquiries, and Report Designer reports requiring rebuild in Dolibarr, along with a tax mapping table and document numbering sequence reconciliation. We do not rebuild automations or reports as part of the migration scope.

Platform deep dives

Context on both ends of the pair

Acumatica logo

Acumatica

Source

Strengths

  • Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
  • Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
  • Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
  • Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
  • Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

  • Steep learning curve and complex initial setup create significant onboarding friction.
  • Report Designer is widely cited as unintuitive and difficult to use for non-developers.
  • Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
  • Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
  • API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.
Dolibarr ERP logo

Dolibarr ERP

Destination

Strengths

  • Free core software with AGPL license and no per-user mandatory fee for self-hosted deployments.
  • Modular architecture lets teams activate only needed features, keeping the interface focused and the database lean.
  • Self-hosted option provides full data sovereignty and avoids recurring SaaS subscription costs.
  • Built-in CSV/Excel import and export wizard with saved profiles simplifies recurring data operations.
  • Low-code Module Builder allows functional extensions without writing PHP code.

Weaknesses

  • No native documented REST API for programmatic bulk operations — all migrations depend on the import/export wizard or direct database access.
  • Reporting and analytics are weak without paid add-ons, and built-in charts are limited compared to modern SaaS platforms.
  • UI design is described as dated by multiple reviewers, with infrequent visual updates to the default theme.
  • Community-only support for self-hosted deployments means no SLA or guaranteed response time for issues.
  • Security vulnerabilities (CVE-2024-5314, CVE-2024-5315) in version 9.0.1 with no immediate patch reported.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Acumatica and Dolibarr ERP.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Acumatica: Licensed by tier — limits visible in License Monitoring Console (SM604000). Community reports suggest ~100 API calls/minute on standard licenses, with higher limits on Enterprise. Concurrent web service sessions are also license-restricted..

  • Data volume sensitivity

    B

    Acumatica doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Acumatica to Dolibarr ERP migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Acumatica to Dolibarr ERP data migrations

Answers to the questions buyers ask most during Acumatica to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Acumatica to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between five and eight weeks for accounts with under 10,000 Business Accounts, 5,000 Inventory Items, and no Projects or complex UDF coverage. Migrations with Projects, large transactional histories (over 50,000 invoices or orders), complex UDF sets, or multi-entity Acumatica configurations move to twelve to twenty weeks because the Dolibarr module activation, Extra field configuration, and CSV sequencing steps must complete before any data loads, and each phase requires customer sign-off before the next begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Acumatica.
Land in Dolibarr ERP, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day