ERP migration
Field-level mapping, validation, and rollback between R4 ENTERPRISE and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
R4 ENTERPRISE
Source
Dolibarr ERP
Destination
Compatibility
11 of 14
objects map 1:1 between R4 ENTERPRISE and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
R4 ENTERPRISE is a discrete manufacturing ERP that organizes data around Customers, Vendors, Items, Work Orders, Bills of Material, and GL Accounts with deep lot tracking and layered cost accounting. Dolibarr is an open-source modular ERP and CRM for small and medium enterprises that uses a single ThirdParty contact object for both customers and vendors, a Product object for items, and separate modules for projects, accounting, and stock. The structural gap between R4 ENTERPRISE's manufacturing depth and Dolibarr's SME scope is the central challenge in this migration: BOM structures and work-order histories require transformation into Dolibarr's simpler product and project equivalents, and layered cost records must be flattened to a single effective cost per item. We extract via vendor-provided CSV exports (R4 ENTERPRISE has no public API), transform and re-map in a staging environment, then load into Dolibarr through its native import utilities and REST API where available. Dolibarr's community-supported nature means production module capabilities are shallower than R4 ENTERPRISE's shop-floor depth; we flag this gap explicitly and deliver a written inventory of any production workflows requiring manual rebuild or third-party module installation post-migration.
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 R4 ENTERPRISE 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.
R4 ENTERPRISE
Customer
Dolibarr ERP
ThirdParty
1:1R4 ENTERPRISE Customer records map to Dolibarr ThirdParty records with Type=Customer. We preserve customer ID, company name, billing and shipping addresses, credit limit, payment terms, and currency preference. Multi-currency assignments on Customer records transfer as read-only reference values in Dolibarr's currency settings. The customer code from R4 ENTERPRISE becomes the ref (reference) field in Dolibarr, serving as the dedupe key during import.
R4 ENTERPRISE
Vendor
Dolibarr ERP
ThirdParty
1:1R4 ENTERPRISE Vendor records map to Dolibarr ThirdParty records with Type=Supplier. We preserve vendor ID, company name, address, 1099 flags, W-9 status, and multi-currency settings. Vendor tax ID fields map to Dolibarr's idprof fields (IDprof1 through IDprof4). Vendors and Customers share the same Dolibarr object but are distinguished by the Client and Fournisseur (supplier) checkboxes on the ThirdParty record.
R4 ENTERPRISE
Item
Dolibarr ERP
Product
1:1R4 ENTERPRISE Item records map to Dolibarr Product records. Unit of measure conversions, stocking locations, and item type (stockable, service, assembly) transfer directly. Lot and serial number controls map to Dolibarr's lot tracking module. The critical transformation is cost layers: R4 ENTERPRISE maintains layered cost records as separate child tables; we flatten these into a single effective cost per item using the most recent receipt cost or the average cost calculated at cutover, storing the method used in a custom field for audit.
R4 ENTERPRISE
Bills of Material
Dolibarr ERP
Product (as kit or BOM)
lossyR4 ENTERPRISE BOMs are versioned with effective dates and item revisions. We extract the active BOM revision and map it to Dolibarr's BOM module (available as a community module or in the manufacturing add-on). Multi-level BOMs require flattening or recursive expansion depending on Dolibarr's installed BOM module version. Each BOM component maps to a BOM line referencing the child Product record. We flag superseded BOM revisions so the destination receives only the current production-approved structure.
R4 ENTERPRISE
Work Orders
Dolibarr ERP
Project or BillOfMaterials
lossyR4 ENTERPRISE Work Orders carry routings, labor standards, and material allocations tied to specific BOM revisions. Dolibarr does not have a native work-order module in the core installation; production workflows typically map to Dolibarr's Project module with task-level tracking of materials and labor, or to a third-party manufacturing module. We extract open and historical work orders, flag any routing steps tied to deprecated BOM versions, and map the structure to either Project tasks or the customer's installed production module.
R4 ENTERPRISE
General Ledger Accounts
Dolibarr ERP
Account (accounting module)
1:1R4 ENTERPRISE Chart of Accounts records map to Dolibarr's accounting module (if activated). Account type, cost-center assignments, and intercompany flags transfer directly. Dolibarr's accounting module supports chart of accounts import via CSV; we preserve the account hierarchy and segment structures where the destination chart matches R4 ENTERPRISE's account structure. Customers activating Dolibarr's accounting module must configure their fiscal year and posting date rules before GL migration begins.
R4 ENTERPRISE
Accounts Payable (open invoices)
Dolibarr ERP
SupplierInvoice
1:1R4 ENTERPRISE open AP vouchers map to Dolibarr SupplierInvoice records. We preserve vendor reference, invoice number, due date, and amount in both transaction and functional currency. Multi-currency AP invoices require exchange-rate revaluation at cutover; we preserve the original functional-currency amount and the exchange rate used at invoice entry so the customer can re-price or maintain historical rates. Closed AP invoices migrate as reference history unless Dolibarr's accounting module supports historical invoice archival.
R4 ENTERPRISE
Accounts Receivable (open invoices)
Dolibarr ERP
Invoice (customer)
1:1R4 ENTERPRISE open AR invoices map to Dolibarr Facture (customer invoice) records. We preserve customer reference, invoice number, due date, and amount in both transaction and functional currency, maintaining the original aging buckets for cash-flow reporting. Open invoice aging buckets transfer as line-item status so the destination supports accurate dunning from day one. Closed AR invoices migrate as reference history.
R4 ENTERPRISE
Fixed Assets
Dolibarr ERP
Asset
1:1R4 ENTERPRISE Fixed Asset records map to Dolibarr Asset records. Acquisition cost, depreciation method, useful life, and location transfer directly. We migrate the asset register and accumulated depreciation balance as of the migration cutover date. Dolibarr's asset module supports basic depreciation tracking; customers with complex depreciation schedules (accelerated, units-of-production) may need to document these for manual entry or custom field extension.
R4 ENTERPRISE
Sales Orders (open)
Dolibarr ERP
Commande client (customer order)
1:1R4 ENTERPRISE open Sales Orders map to Dolibarr Commande customer order records. Customer reference, line items, quantities, pricing, and promised dates transfer directly. We flag any order lines that reference discontinued items or inactive price lists in the destination item catalog so the customer's admin can resolve these before production use. Order status (pending, confirmed, partially shipped) maps to Dolibarr's order status field.
R4 ENTERPRISE
Purchase Orders (open)
Dolibarr ERP
Commande fournisseur (supplier order)
1:1R4 ENTERPRISE open Purchase Orders map to Dolibarr Commande fournisseur records. Vendor reference, line items, quantities, and expected receipt dates transfer directly. We flag any PO lines that reference item numbers not present in the destination product catalog for admin resolution before production use.
R4 ENTERPRISE
Inventory Balances
Dolibarr ERP
Stock
1:1R4 ENTERPRISE on-hand quantities extract per location and per lot or serial number. We preserve lot numbers and bin locations so the destination stock snapshot matches physical reality at cutover. Each stock record maps to a Dolibarr Stock product record with warehouse assignment. Lot numbers require Dolibarr's stock lot module to be activated; serial numbers similarly require the serial number tracking module. We flag any expired-lot items tied to discontinued SKUs so they do not create active inventory records in the destination.
R4 ENTERPRISE
Custom Fields
Dolibarr ERP
Extra fields
lossyR4 ENTERPRISE user-defined fields on master records extract as name-value pairs. We map these to Dolibarr's Extra fields (extrafields) system, which stores custom field data in a separate table linked by element_id. Customers approve the mapping table during scoping; any fields with no Dolibarr equivalent are documented for post-migration review and potential community module installation.
R4 ENTERPRISE
Users and Roles
Dolibarr ERP
User
1:1R4 ENTERPRISE user accounts with login name, role assignment, and menu preferences map to Dolibarr User records. Role assignments map to Dolibarr's permission set system (global rights and per-module rights). We export user records and map them to the nearest equivalent Dolibarr security group; the customer's admin confirms access levels and deactivates any accounts not carried forward.
| R4 ENTERPRISE | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty1:1 | Fully supported | |
| Vendor | ThirdParty1:1 | Fully supported | |
| Item | Product1:1 | Fully supported | |
| Bills of Material | Product (as kit or BOM)lossy | Mapping required | |
| Work Orders | Project or BillOfMaterialslossy | Mapping required | |
| General Ledger Accounts | Account (accounting module)1:1 | Fully supported | |
| Accounts Payable (open invoices) | SupplierInvoice1:1 | Fully supported | |
| Accounts Receivable (open invoices) | Invoice (customer)1:1 | Fully supported | |
| Fixed Assets | Asset1:1 | Fully supported | |
| Sales Orders (open) | Commande client (customer order)1:1 | Fully supported | |
| Purchase Orders (open) | Commande fournisseur (supplier order)1:1 | Fully supported | |
| Inventory Balances | Stock1:1 | Fully supported | |
| Custom Fields | Extra fieldslossy | Mapping required | |
| Users and Roles | User1:1 | Mapping required |
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.
R4 ENTERPRISE gotchas
No public API for programmatic data extraction
Lot number and cost layer histories require careful sequencing
Multi-currency AP and AR balances need currency revaluation
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
Discovery and vendor export coordination
We audit the source R4 ENTERPRISE environment across all modules in scope: customer count, vendor count, item count with BOM complexity, work-order volume (open and historical), GL account count, open AP and AR balances, fixed asset register, and inventory snapshot (per location and per lot). Because R4 ENTERPRISE has no public API, we coordinate directly with the vendor's professional services team to obtain CSV or XML exports of each data set. We request the export package 3-4 weeks before the planned migration window to allow reformatting and staging time. We simultaneously assess the target Dolibarr installation: edition (community vs business), activated modules, hosting environment, and any third-party modules already installed.
Schema design and transformation mapping
We design the destination schema in Dolibarr based on activated modules. This includes configuring ThirdParty types (customer, supplier, or both), Product types (stockable, service, assembly), warehouse assignments, and accounting chart of accounts structure. For customers activating the accounting module, we map the R4 ENTERPRISE GL account hierarchy to the Dolibarr chart. We design the BOM and work-order mapping strategy based on installed Dolibarr modules: basic BOM for simple assemblies, third-party manufacturing module for routing and labor. We document the cost-flattening method and apply it during the staging migration. All schema design is reviewed with the customer's admin before any data moves.
Staging migration and reconciliation
We run a full migration into a staging copy of the target Dolibarr instance using production-like data volume. The customer's team reconciles record counts across all object types, spot-checks 25-50 records per object against the R4 ENTERPRISE source for field accuracy, and validates that cost values, lot numbers, and multi-currency amounts are correct. Any mapping corrections are documented and applied before the production migration. This staging step also serves as the team's training and validation opportunity, reducing surprises at cutover.
Cost layer flattening and BOM normalization
We run the cost-flattening transformation on all R4 ENTERPRISE layered cost records, producing a single effective cost per item with the calculation method documented. For multi-level BOMs, we extract the active revision and normalize component quantities to the top-level item. We flag any BOM structures that cannot be represented in the target Dolibarr BOM module (recursive structures, phantom bills, co-products) and present alternatives to the customer's admin. Work-order histories are mapped to project tasks or the installed production module, with routing steps attached as task notes where no native routing exists.
Production migration in dependency order
We run production migration in record-dependency order: ThirdParties (customers and vendors), Products (items with flattened costs), BOMs (if applicable), GL accounts (if accounting module activated), Fixed Assets, open AP and AR (with currency metadata preserved), open Sales Orders, open Purchase Orders, Inventory balances (per warehouse with lot numbers), and Work Orders (mapped to projects). Each phase emits a row-count reconciliation report before the next phase begins. We use Dolibarr's native import utilities for CSV loads and the REST API for API-supported record types.
Cutover, validation, and production workflow handoff
We freeze R4 ENTERPRISE writes during cutover, run a final delta migration of any records modified during the migration window, then mark Dolibarr as the system of record. We deliver a written inventory of any R4 ENTERPRISE production workflows, custom reports, and forms that do not have a Dolibarr equivalent, with recommended rebuild paths. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild R4 ENTERPRISE production workflows, custom reports, or scheduling rules inside the migration scope; those are documented for the customer's admin or a Dolibarr implementation partner to address separately.
Platform deep dives
R4 ENTERPRISE
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 R4 ENTERPRISE 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
R4 ENTERPRISE: Not applicable..
Data volume sensitivity
R4 ENTERPRISE 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 R4 ENTERPRISE to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your R4 ENTERPRISE 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 R4 ENTERPRISE
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.