ERP migration
Field-level mapping, validation, and rollback between Accolent ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Accolent ERP
Source
Dolibarr ERP
Destination
Compatibility
12 of 14
objects map 1:1 between Accolent ERP and Dolibarr ERP.
Complexity
CModerate
Timeline
3-5 weeks
Overview
Migrating from Accolent ERP to Dolibarr addresses the absence of a public API in Accolent by routing all data extraction through direct SQL access or vendor-assisted export, then loading the resulting flat files into Dolibarr's MySQL/MariaDB backend via its native import tools or Dolibarr's REST API. Accolent's multi-warehouse inventory, BOM hierarchy, and open AP/AR balances each require explicit transformation: warehouse bin locations map to Dolibarr's stock location structure, multi-level BOMs are flattened into Dolibarr's product BOM module, and live payables/receivables land as beginning-balance or outstanding-invoice records rather than new transactions. Dolibarr's modular activation model means we configure the accounting, stock, and project modules before importing master and transactional data, and we flag Documents and Attachments as not migratable because Accolent does not expose a file-retrieval API. We do not migrate Accolent's report definitions, workflow configurations, or user access-control rules as code; we deliver a written inventory of these 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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Accolent ERP 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.
Accolent ERP
Customer
Dolibarr ERP
ThirdParty (Customer type)
1:1Accolent Customer records with billing address, shipping address, contact details, and account type flags map to Dolibarr ThirdParty records where the Tiers type field is set to Customer. We extract the customer_code, name, address fields, phone, email, and payment terms from Accolent's customer master and map them to Dolibarr's ref (customer code), name, address fields, phone, email, and conditions_reglement fields. Customer price level and credit limit from Accolent map to Dolibarr's price level and limite_credit fields. We set the ThirdParty status to Active and preserve the original Accolent customer ID in a custom reference field for reconciliation.
Accolent ERP
Vendor
Dolibarr ERP
ThirdParty (Supplier type)
1:1Accolent Vendor records with address, payment terms, and PO defaults map to Dolibarr ThirdParty where the Tiers type is set to Supplier. We extract vendor_code, name, address, phone, email, and payment terms from Accolent's vendor master and map them to Dolibarr's ref (supplier code), name, address fields, phone, email, and conditions_reglement fields. Default PO lead time and freight terms from Accolent map to Dolibarr's delivery delay and shipping_methode fields.
Accolent ERP
Item (Product/Inventory)
Dolibarr ERP
Product
1:1Accolent Item records including SKU, description, unit of measure, cost layers, pricing tiers, reorder points, and warehouse assignments map to Dolibarr Product records. The Accolent item_type (Stocked vs Non-Stocked vs Service) maps to Dolibarr's fk_product_type (0=standard, 1=service). Barcode and lot/serial number settings migrate to Dolibarr's barcode and lot_num fields. Accolent's price tiers map to Dolibarr's multi-price levels. For items with BOM links, we flag the product for BOM configuration after the base product is imported.
Accolent ERP
Sales Order
Dolibarr ERP
CommandeClient (Customer Order)
1:1Accolent Sales Order headers and line items map to Dolibarr CommandeClient and its associated OrderLine records. We extract order number, order date, customer reference, ship-to address, and line items (product, quantity, unit price, discount) from Accolent. Dolibarr's CommandeClient uses a status workflow (Draft, Validated, Shipped, Closed) that we map from Accolent's order status field. Fulfilled lines retain their fulfilled quantity in Dolibarr's qty_shipped field. Open orders import as Draft or Validated status; historical orders import as Closed with shipped quantities preserved.
Accolent ERP
Purchase Order
Dolibarr ERP
CommandeFournisseur (Supplier Order)
1:1Accolent Purchase Order records including vendor reference, PO date, line items, receipt status, and expected delivery date map to Dolibarr CommandeFournisseur and OrderLine records. The vendor reference maps to Dolibarr's fk_soc (ThirdParty supplier). Receipt status from Accolent (Not Received, Partially Received, Fully Received) maps to Dolibarr's status field. Line items include product reference, ordered quantity, unit cost, and any landed cost allocations.
Accolent ERP
Chart of Accounts
Dolibarr ERP
Accounting Account (plan comptable)
1:1Accolent GL Chart of Accounts with account numbers, names, types (Asset, Liability, Expense, Revenue), and optional cost-center assignments maps to Dolibarr AccountingAccount records. The five-digit account code from Accolent maps to Dolibarr's account_number field. Account type (classe 1 through 7 in French GAAP-style numbering) maps to Dolibarr's pcm_type field. We activate Dolibarr's accounting module during pre-migration configuration and import the chart before any transactional data to ensure account references are valid on insert.
Accolent ERP
Open AP/AR Balances
Dolibarr ERP
FactureFournisseur (Supplier Invoice) and Facture (Customer Invoice) with outstanding amounts
lossyOutstanding Accolent AP invoices and AR invoices must land as open balance records in Dolibarr rather than new transactions. We extract invoice header records with original invoice date, vendor/customer reference, total amount, and outstanding amount, then create Dolibarr supplier invoices (FactureFournisseur) with status = unpaid and a payment term entry set to the original due date. For AR, we create Facture records with status = unpaid. Invoices older than 90 days are flagged for customer review before commit because Dolibarr's aging report does not auto-truncate old opening balances.
Accolent ERP
Bills of Materials (BOM)
Dolibarr ERP
Bom (product BOM)
1:manyAccolent multi-level BOM headers with component lines, quantities-per, routing steps, work-center assignments, and phantom BOM flags require flattening for Dolibarr's BOM module. Dolibarr supports a two-level BOM structure (parent product with sub-product components). We extract the full Accolent BOM tree, resolve phantom BOM flags to sub-product references, and create a flat Bom record per Accolent BOM header. Components with quantity-per relationships map to BomLine entries. BOMs with more than three levels are flagged for manual review before load because Dolibarr does not natively support routing steps or work-center assignments; these must be managed as notes or via a production module extension.
Accolent ERP
Warehouse Location
Dolibarr ERP
Entrepot (Warehouse)
1:1Accolent warehouse definitions with site name, address, and bin/shelf location codes map to Dolibarr Entrepot records. The warehouse_code, name, and address fields transfer directly. Bin and shelf location codes from Accolent are stored in Dolibarr's address field or as a custom location reference field. We create one Dolibarr Entrepot per Accolent warehouse site before any stock data imports to satisfy the warehouse lookup on product-stock records.
Accolent ERP
Financial Transactions (Journal Entries)
Dolibarr ERP
AccountantDocument (Journal Entry)
1:1Accolent posted journal entries including date, account number, debit/credit amounts, and source reference map to Dolibarr AccountingDocument records in the configured journal. Each journal entry line is an AccountingDocumentLine with the account reference, debit amount (or 0), credit amount (or 0), and the general_account lookup. We preserve the original posting date and journal code from Accolent. Note that Dolibarr's accounting module must be activated and the journal (ACHAT, VENTE, BANQUE, or GENERAU) must be pre-created before this import runs.
Accolent ERP
Tax Codes
Dolibarr ERP
Tax (TaxRate)
1:1Accolent tax codes with rate percentages and applicability rules (sales vs purchasing) map to Dolibarr TaxRange records. The tax_code, rate percentage, and applicable transaction type transfer to Dolibarr's ref, rate (percentage), and fk_type (VAT-deductible, VAT-collected, or other). We configure Dolibarr's tax module before importing sales or purchasing records to ensure tax codes are valid on transaction lines.
Accolent ERP
Fixed Assets
Dolibarr ERP
Asset
1:1Accolent fixed asset records including asset number, description, acquisition cost, acquisition date, depreciation method, useful life, accumulated depreciation, and asset class map to Dolibarr Asset records. The asset number maps to Dolibarr's ref, acquisition cost to purchase_value, acquisition date to date_acquisition, accumulated depreciation to cumulative_depreciation, and depreciation method to depreciation_type. We create the asset before importing the associated GL transactions to maintain the asset-account linkage.
Accolent ERP
Users and Permissions
Dolibarr ERP
User
1:1Accolent user accounts with login name, email, role name, and permission flags map to Dolibarr User records. The primary email becomes the user login, and the role name maps to a Dolibarr permission group. Note that Dolibarr's permission model is module-based (each activated module grants specific rights), so we deliver a permission matrix mapping Accolent role names to Dolibarr module-level permission sets for the customer's admin to configure post-migration.
Accolent ERP
Documents and Attachments
Dolibarr ERP
N/A
1:1Accolent stores documents and file attachments associated with orders, items, and customers. The platform does not expose a documented file-retrieval API or export mechanism for attachments. We do not migrate document attachments. We deliver a written inventory of all document attachment paths and metadata (file name, associated record type, record ID, file size, last modified date) extracted from the Accolent database so the customer's admin can manually retrieve and re-upload files to Dolibarr's document management module post-migration.
| Accolent ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Customer type)1:1 | Fully supported | |
| Vendor | ThirdParty (Supplier type)1:1 | Fully supported | |
| Item (Product/Inventory) | Product1:1 | Fully supported | |
| Sales Order | CommandeClient (Customer Order)1:1 | Fully supported | |
| Purchase Order | CommandeFournisseur (Supplier Order)1:1 | Fully supported | |
| Chart of Accounts | Accounting Account (plan comptable)1:1 | Mapping required | |
| Open AP/AR Balances | FactureFournisseur (Supplier Invoice) and Facture (Customer Invoice) with outstanding amountslossy | Mapping required | |
| Bills of Materials (BOM) | Bom (product BOM)1:many | Mapping required | |
| Warehouse Location | Entrepot (Warehouse)1:1 | Fully supported | |
| Financial Transactions (Journal Entries) | AccountantDocument (Journal Entry)1:1 | Mapping required | |
| Tax Codes | Tax (TaxRate)1:1 | Mapping required | |
| Fixed Assets | Asset1:1 | Mapping required | |
| Users and Permissions | User1:1 | Mapping required | |
| Documents and Attachments | N/A1:1 | Not 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.
Accolent ERP gotchas
No public API means all migration runs through database access or vendor-assisted export
No bulk or batch API — file exports are the only high-volume path
BOM and manufacturing data requires manual schema mapping
Open AP/AR balances must be imported as live balance-forward records
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
Access confirmation and extraction method agreement
We confirm the Accolent deployment type (on-premise SQL Server or cloud-hosted by ADS Solutions) and agree on the extraction method during the scoping call. For on-premise, we establish a secure VPN or jump-host connection and test read access to the primary database. For cloud-hosted, we coordinate with the ADS Solutions account representative to arrange a structured CSV export or read-only database access. We run a discovery query against all core tables (customer, vendor, item, so_header, po_header, gl_account, ap_header, ar_header, bom_header, warehouse, user) to confirm schema visibility and record counts before formal scoping closes.
Dolibarr module activation and schema pre-configuration
We activate the required Dolibarr modules (ThirdParty, Product, CommandeClient, CommandeFournisseur, Facture, Stock, Accounting, BOM, Project) in the target Dolibarr instance before any data import begins. We configure the accounting module with the appropriate chart of accounts template, create the required journals, and set the multi-currency and tax configurations. For manufacturing customers, we configure the BOM module and prepare the product BOM structure. We validate all lookups (warehouse, price level, payment term, tax code) exist in Dolibarr before loading transactional data.
Data extraction and staging in Accolent schema
We execute structured SQL queries against the Accolent database to extract master data (customers, vendors, items, chart of accounts, tax codes, fixed assets, warehouses) and transactional data (sales orders, purchase orders, AP/AR open balances, BOMs, journal entries). For each object we generate a deduplicated, schema-aligned CSV file. We run data quality checks: duplicate detection on customer/vendor/item codes, date-range validation on transaction dates, and null-check on required fields. Records failing validation are written to a separate exceptions file for customer review. We also extract BOM tree depth for each BOM header to flag multi-level structures for flattening.
BOM flattening, balance-forward creation, and object transformation
We flatten Accolent's multi-level BOM tree into a single-level parent-component structure for Dolibarr. Phantom BOM flags are resolved to sub-product references. Open AP/AR invoices are transformed into Dolibarr unpaid invoice records with original invoice references and due dates preserved. Journal entries are split into Dolibarr AccountingDocument and AccountingDocumentLine records. All transformation rules are documented in a written mapping spec that the customer reviews before the import phase begins.
Staged import into Dolibarr with dependency ordering
We run imports into Dolibarr in strict dependency order: accounting chart (prerequisite for all GL references), warehouses (prerequisite for stock), tax codes (prerequisite for invoice lines), ThirdParties (customers and vendors), Products (with BOM links flagged for later BOM import), BOMs (after products), then transactional records (orders, invoices, journal entries). Each phase emits a row-count reconciliation report. We use Dolibarr's native CSV import tool for standard objects and direct MySQL INSERT with API fallback for bulk operations. Owner reconciliation (user accounts) runs before transactional imports to resolve all user_id references.
Cutover, validation, and inventory handoff
We freeze Accolent writes during cutover and run a final delta migration of any records modified during the migration window. We validate 25-50 spot-check records per object against the Accolent source and reconcile total record counts. We deliver the migration inventory document: a written map of all imported objects with record counts, a list of documents and attachments requiring manual re-upload, and a permissions matrix mapping Accolent role names to Dolibarr module-level permission sets for the admin to configure post-migration. We support a one-week hypercare window for reconciliation issues. We do not rebuild Accolent workflows or report definitions in Dolibarr as standard scope.
Platform deep dives
Accolent ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Moderate ERP migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Accolent ERP and Dolibarr ERP.
Object compatibility
4 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
Accolent ERP: Not applicable.
Data volume sensitivity
Accolent ERP 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 Accolent ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Accolent ERP 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 Accolent ERP
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.