ERP migration

Migrate from R4 ENTERPRISE to Dolibarr ERP

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 logo

R4 ENTERPRISE

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

79%

11 of 14

objects map 1:1 between R4 ENTERPRISE and Dolibarr ERP.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

R4 ENTERPRISE logo

R4 ENTERPRISE

What's pushing teams away

  • Annual maintenance contracts and hardware refresh cycles become expensive as the business grows past 100 users.
  • The user interface feels dated compared to modern cloud ERPs, leading to longer onboarding times for new employees.
  • Customization outside the standard modules requires vendor professional services, creating bottlenecks on configuration changes.
  • No native API documentation means third-party integrations and automated data pipelines require custom development each time.
  • Reporting and business intelligence tools are functional but lag behind dedicated BI platforms on visualization and self-service analytics.

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 R4 ENTERPRISE objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

ThirdParty

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

ThirdParty

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

Product

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

Product (as kit or BOM)

lossy
Mapping required

R4 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

maps to

Dolibarr ERP

Project or BillOfMaterials

lossy
Mapping required

R4 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

maps to

Dolibarr ERP

Account (accounting module)

1:1
Fully supported

R4 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)

maps to

Dolibarr ERP

SupplierInvoice

1:1
Fully supported

R4 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)

maps to

Dolibarr ERP

Invoice (customer)

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

Asset

1:1
Fully supported

R4 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)

maps to

Dolibarr ERP

Commande client (customer order)

1:1
Fully supported

R4 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)

maps to

Dolibarr ERP

Commande fournisseur (supplier order)

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

Stock

1:1
Fully supported

R4 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

maps to

Dolibarr ERP

Extra fields

lossy
Mapping required

R4 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

maps to

Dolibarr ERP

User

1:1
Mapping required

R4 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.

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.

R4 ENTERPRISE logo

R4 ENTERPRISE gotchas

High

No public API for programmatic data extraction

Medium

Lot number and cost layer histories require careful sequencing

Medium

Multi-currency AP and AR balances need currency revaluation

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

  • R4 ENTERPRISE has no public API for data extraction

    R4 ENTERPRISE does not publish a REST or SOAP API for external access. All data export must be performed through the built-in report writer, ODBC direct database queries, or vendor-provided export utilities. We engage the vendor's professional services team to obtain data extracts in CSV or XML format. We always request the export package 2-3 weeks before the migration window to allow time for reformatting, re-mapping, and validation in our staging environment. Any delays in vendor export delivery push the migration timeline; we cannot begin transformation work until the source data is in hand.

  • Layered cost histories must be flattened before import

    R4 ENTERPRISE maintains per-lot and per-receipt layered cost records as separate child tables. Dolibarr's product cost model is average or standard cost per product with no native support for layered cost history. We flatten the layered cost history into a single effective cost per item using either the most recent receipt cost or a weighted average calculated at cutover. The flattening method is documented in a custom field on each product record so the customer's finance team can verify and adjust. Lot-level cost detail is not preserved in the destination.

  • Manufacturing module depth is shallower in Dolibarr

    R4 ENTERPRISE provides deep BOM versioning, work-order routing with labor standards, and material allocation tied to specific BOM revisions. Dolibarr's production capabilities in the core installation are limited to basic BOM management and project-based production tracking. A third-party manufacturing module (DoliBoutique or community) is required for routing, labor standards, and shop-floor scheduling. We flag which R4 ENTERPRISE production features have no direct Dolibarr equivalent and deliver a written inventory of required third-party modules or manual process changes.

  • Multi-currency AP and AR require revaluation at cutover

    R4 ENTERPRISE stores open AP and AR in both transaction currency and functional currency with the original exchange rate. Migrating open invoices to Dolibarr requires either revaluation at cutover using the current exchange rate or preservation of the original rate and functional-currency amount. We preserve both the original rate and the original functional-currency amount so the customer's accountant can elect to re-price or keep historical rates. Dolibarr's accounting module must be activated and configured with appropriate currency settings before multi-currency invoices are imported.

  • Dolibarr third-party contact model differs from R4 ENTERPRISE split

    R4 ENTERPRISE maintains separate Customer and Vendor master files. Dolibarr uses a single ThirdParty object where each record can be flagged as Customer, Supplier, or both. During migration we split the R4 ENTERPRISE sources into separate ThirdParty records if the same entity appears as both a customer and vendor in R4 ENTERPRISE, and we consolidate duplicate entities that appear under both roles into a single ThirdParty with both checkboxes enabled. The customer's admin confirms the deduplication rules during scoping.

Migration approach

Six steps for a successful R4 ENTERPRISE to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

R4 ENTERPRISE logo

R4 ENTERPRISE

Source

Strengths

  • Integrated ERP, CRM, and financial modules eliminate data silos between sales, production, and accounting teams.
  • Robust lot tracking and serial number genealogy support regulated industries and first-in-first-out inventory requirements.
  • Multi-currency and multi-language ledger handles international subsidiaries and intercompany transactions natively.
  • Hardware-agnostic deployment model avoids cloud per-seat pricing for high-volume transaction environments.
  • Deep BOM and routing support handles complex discrete manufacturing workflows including kitting and co-products.

Weaknesses

  • No publicly documented API means programmatic data extraction requires custom integration development.
  • Dated desktop-client interface generates higher training costs and slower user adoption compared to modern SaaS ERPs.
  • Customization requires vendor professional services, creating long lead times for configuration changes.
  • Limited self-service reporting and BI compared to standalone analytics platforms.
  • Maintenance contracts and on-premise hardware refresh cycles add significant total cost of ownership over time.
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 R4 ENTERPRISE 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

    R4 ENTERPRISE: Not applicable..

  • Data volume sensitivity

    B

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

Estimator

Estimate your R4 ENTERPRISE 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 R4 ENTERPRISE to Dolibarr ERP data migrations

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

Can't find your answer?

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 consultation

Most migrations land between four and six weeks for accounts under 10,000 items, 2,000 customers, and 500 vendors with straightforward cost structures and no complex multi-level BOMs. Migrations with complex BOM structures, layered cost histories across hundreds of lots, multi-currency AP and AR revaluation requirements, or work-order histories exceeding 1,000 records move to eight to twelve weeks. The primary variable is vendor export delivery from R4 ENTERPRISE; we cannot begin transformation work until the source data is in hand.

Adjacent paths

Related migrations to explore

Ready when you are

Move from R4 ENTERPRISE.
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