ERP migration
Field-level mapping, validation, and rollback between Acumatica and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Acumatica
Source
Dolibarr ERP
Destination
Compatibility
12 of 13
objects map 1:1 between Acumatica and Dolibarr ERP.
Complexity
BStandard
Timeline
5-8 weeks
Try the reverse
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Acumatica platform overview
Scorecard, SWOT, gotchas, and pricing for Acumatica.
Destination platform
Dolibarr ERP platform overview
Scorecard, SWOT, gotchas, and pricing for Dolibarr ERP.
Data migration guide
The complete Dolibarr migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
Acumatica migration guide
Understand the data you're exporting from Acumatica before mapping it.
Destination checklist
Dolibarr migration checklist
Pre- and post-cutover tasks for moving onto Dolibarr ERP.
Source checklist
Acumatica migration checklist
Exit checklist for unwinding your Acumatica setup cleanly.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Dolibarr ERP
Third Party
1:1Acumatica 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
Dolibarr ERP
Third Party (Supplier)
1:1Acumatica 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)
Dolibarr ERP
Product
1:1Acumatica 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)
Dolibarr ERP
Account (Accounting plan)
1:1Acumatica 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
Dolibarr ERP
Project
1:1Acumatica 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
Dolibarr ERP
Customer Order
1:1Acumatica 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
Dolibarr ERP
Supplier Order
1:1Acumatica 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
Dolibarr ERP
Customer Invoice
1:1Acumatica 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
Dolibarr ERP
Supplier Invoice
1:1Acumatica 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
Dolibarr ERP
User / Third Party (Contact)
1:1Acumatica 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
Dolibarr ERP
Warehouse
1:1Acumatica 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
Dolibarr ERP
Note / Attached Document
1:1Acumatica 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
Dolibarr ERP
Tax / VAT
lossyAcumatica 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.
| Acumatica | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Business Account | Third Party1:1 | Fully supported | |
| Vendor | Third Party (Supplier)1:1 | Fully supported | |
| Inventory Item (Stock/Non-Stock) | Product1:1 | Fully supported | |
| Chart of Accounts (GL Account) | Account (Accounting plan)1:1 | Fully supported | |
| Project | Project1:1 | Fully supported | |
| Sales Order | Customer Order1:1 | Fully supported | |
| Purchase Order | Supplier Order1:1 | Fully supported | |
| AR Invoice | Customer Invoice1:1 | Fully supported | |
| AP Invoice | Supplier Invoice1:1 | Fully supported | |
| Employee | User / Third Party (Contact)1:1 | Fully supported | |
| Warehouse / Location | Warehouse1:1 | Fully supported | |
| Note | Note / Attached Document1:1 | Fully supported | |
| Tax Category / Zone | Tax / VATlossy | Fully supported |
Gotchas + challenges
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 gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Acumatica
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Acumatica and Dolibarr ERP.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
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
Acumatica doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Acumatica to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Acumatica
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.