ERP migration

Migrate from Aptean Compiere ERP to Dolibarr ERP

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

Aptean Compiere ERP logo

Aptean Compiere ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

objects map 1:1 between Aptean Compiere ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Aptean Compiere ERP to Dolibarr is a platform migration across fundamentally different technology stacks: Compiere runs on Java with Oracle or PostgreSQL, while Dolibarr is PHP-based with MySQL or PostgreSQL. Compiere's three-tier security model (System, Client, Organization) has no direct Dolibarr equivalent, so we collapse subsidiary Organizations into Dolibarr third-party entities and preserve the parent-Client relationship as a Dolibarr category or project. We migrate Business Partners as third-party records with separate contact records, Products with multi-level BOMs preserved, and open Accounts Payable and Receivable as Dolibarr invoices with payment status. Workflows, automations, and the Visual Dictionary Editor customizations do not migrate; we deliver a written inventory of any customizations requiring Dolibarr module equivalents 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

Aptean Compiere ERP logo

Aptean Compiere ERP

What's pushing teams away

  • Steep learning curve for developers, particularly those unfamiliar with Java JDK 1.6 or the cross-platform client architecture, leading to long onboarding times before teams become productive.
  • Frequent performance issues and slow loading reported by users, particularly in older Compiere deployments where connectivity and software bugs disrupt workflow.
  • Limited API documentation and unclear rate-limit information make integrations brittle, pushing teams toward platforms with more transparent developer ecosystems.
  • Only Enterprise Edition customers receive Service Packs, bug fixes, and access to Aptean Connect; Community Edition users manage their own upgrade path with less professional support.
  • Vendors and customers on G2 and Capterra report that occasional technical glitches and software bugs persist across minor releases, dampening confidence in long-term stability.

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 Aptean Compiere ERP objects map to Dolibarr ERP

Each row shows how a Aptean Compiere 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.

Aptean Compiere ERP

Business Partner

maps to

Dolibarr ERP

ThirdParty + Contact

1:many
Fully supported

Compiere's unified Business Partner entity splits into Dolibarr's ThirdParty (the organization-level record) and Contact records (the individual people). We extract BP type flags (customer, vendor, both) to set Dolibarr's Tiers and Customer/Supplier flags. Addresses and locations from Compiere BP location records migrate to Dolibarr Address records linked to ThirdParty. We preserve the original BP name and search keys as Dolibarr ref_int and ref_ext for audit.

Aptean Compiere ERP

Organization

maps to

Dolibarr ERP

ThirdParty entity or Project

1:1
Fully supported

Compiere's three-tier System-Client-Org hierarchy has no direct Dolibarr equivalent. We map each Compiere Client to a top-level Dolibarr ThirdParty (marked as internal or parent) and each Organization within that Client to either a child ThirdParty or a Dolibarr Project with the parent ThirdParty linked. The customer chooses the mapping during scoping based on whether subsidiary entities need separate invoicing. We flag any BP records that span multiple Organizations and require disambiguation.

Aptean Compiere ERP

Product

maps to

Dolibarr ERP

Product

1:1
Fully supported

Compiere Products migrate to Dolibarr Product records. We map ProductType (Item vs Service), the sales and purchase flags, and the default unit of measure. Compiere's product stock warehouse location migrates to Dolibarr's warehouse assignment. Product categories map to Dolibarr's Categories.

Aptean Compiere ERP

Bill of Materials

maps to

Dolibarr ERP

Bill of Materials (manufacturing module)

1:1
Fully supported

Compiere multi-level BOMs migrate to Dolibarr's BOM/BoM object under the manufacturing module. We preserve the full component hierarchy with quantities and scrap percentages, and we resolve each component reference back to its migrated Product record. If the destination Dolibarr instance does not have the manufacturing module activated, we flag BOMs as a module activation requirement during scoping.

Aptean Compiere ERP

Warehouse and Locator

maps to

Dolibarr ERP

Warehouse

1:1
Fully supported

Compiere warehouses with up to five locator dimensions (aisle, bin, rack, level, bay) map to Dolibarr Warehouses. Multi-dimension locator data beyond Dolibarr's flat location model is collapsed into the warehouse Location field as a hyphenated string. If the customer requires locator-level inventory tracking, we document it as a Dolibarr module or custom field requirement.

Aptean Compiere ERP

Price List

maps to

Dolibarr ERP

Product Price (multi-price)

lossy
Fully supported

Compiere purchase and sales price lists map to Dolibarr multi-price entries on each Product record. We create separate Dolibarr Price Types for each source price list name and associate price entries by effective-from date. Customer-specific pricing migrates as a dedicated price list linked to the relevant ThirdParty.

Aptean Compiere ERP

Chart of Accounts

maps to

Dolibarr ERP

Account (Accounting module)

1:1
Mapping required

Compiere's country-specific AccountingXX.csv chart of accounts maps to Dolibarr's accounting chart. We import the natural account hierarchy (Account_Value, Name, Account_Type, Account_Default) and reconstruct the account tree under Dolibarr's categories (Assets, Liabilities, Equity, Income, Expenses). If the destination Dolibarr uses an external accounting module (bookkeeping export), we format the chart for the export format.

Aptean Compiere ERP

Open Accounts Payable

maps to

Dolibarr ERP

Supplier Invoice

1:1
Fully supported

Open AP invoices from Compiere migrate as Dolibarr Supplier Invoice records with status Draft or Unvalidated. We preserve vendor reference, invoice number, invoice date, due date, total amount, and line items with account distribution. Payment status carries as unpaid. Historical closed AP is scoped separately and archived rather than migrated to reduce migration volume.

Aptean Compiere ERP

Open Accounts Receivable

maps to

Dolibarr ERP

Customer Invoice

1:1
Fully supported

Open AR invoices from Compiere migrate as Dolibarr Customer Invoice records. We preserve customer reference (linked to migrated ThirdParty), invoice number, date, due date, total, and line items. Invoice status migrates as Dolibarr's validated or draft status. Payment reconciliation data migrates as partial payment records where applicable.

Aptean Compiere ERP

Product Category

maps to

Dolibarr ERP

Category

1:1
Fully supported

Compiere Product Categories with pricing structures, accounting rules, and discount controls map to Dolibarr Categories. We set the Category type to Product and preserve the parent-child hierarchy. Discount structures are carried as Dolibarr extrafields if the module supports them, or documented for admin configuration post-migration.

Aptean Compiere ERP

User and Role

maps to

Dolibarr ERP

User

1:1
Fully supported

Compiere users with System, Client, and Organization-level roles map to Dolibarr User accounts. We resolve by email match and map role names to Dolibarr permission groups. Any Compiere user without a matching email in the destination is held in a reconciliation queue. Multi-org access scopes that Compiere handled at the Organization level are not natively replicated in Dolibarr's flat user model.

Aptean Compiere ERP

Accounting Schema

maps to

Dolibarr ERP

Accounting Configuration

lossy
Fully supported

Compiere's Accounting Schema (combination of Chart of Accounts and accounting rules) maps to Dolibarr's accounting configuration. We set the functional currency from the source accounting schema, map posting rules to Dolibarr's account assignment configuration, and preserve the accounting schema name as a reference field for audit.

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.

Aptean Compiere ERP logo

Aptean Compiere ERP gotchas

High

Service Packs gated behind Enterprise Edition

High

Multi-organization hierarchy affects data scoping

Medium

Oracle and PostgreSQL database edition differences

Medium

Historical transaction carry-over without cleansing

Low

Unclear API rate limits and bulk endpoint availability

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

  • Multi-org hierarchy collapses into Dolibarr's flat entity model

    Compiere's three-tier System-Client-Organization security model lets holding companies manage subsidiaries independently while retaining consolidated views. Dolibarr has no equivalent multi-org hierarchy. We map each Compiere Organization to either a separate Dolibarr ThirdParty (if the subsidiary needs its own invoicing) or a Dolibarr Project (if it is an internal cost center). Any Business Partner records that span multiple Organizations require disambiguation before migration. We confirm the desired entity mapping during scoping because retroactive changes to third-party relationships after migration are disruptive.

  • BOM hierarchy requires Dolibarr manufacturing module activation

    Compiere's multi-level BOM support (with scrap percentages, phantom BOMs, and routing-linked assemblies) is a core manufacturing feature. Dolibarr's BOM capability is available only with the manufacturing module (extension module in Dolibarr's addons ecosystem). If the destination Dolibarr instance does not have this module activated, BOM component hierarchies cannot be preserved at migration time. We confirm module availability during scoping and install the manufacturing module before BOM migration begins. BOMs without the module are documented as a deferred scope.

  • Five-dimension locator data cannot map directly to Dolibarr warehouse structure

    Compiere supports up to five user-defined locator dimensions (e.g., Aisle-Bin-Rack-Level-Bay) per warehouse. Dolibarr's warehouse model uses a single location field per stock entry. We collapse multi-dimension locator strings into a hyphenated location identifier stored in the Dolibarr warehouse location field. Inventory quantities, total stock values, and re-order thresholds migrate correctly, but spatial locator granularity beyond the warehouse level is lost unless the customer implements a custom field or locator extension module.

  • Compiere API surface area is undocumented for migration scoping

    Compiere's public documentation does not specify API rate limits or confirm bulk/batch endpoint availability. Aptean Connect serves as the primary integration hub for Enterprise Edition customers, but Community Edition users often rely on direct database exports. We handle this by assuming conservative per-record API calls for Enterprise Edition customers, requesting a pre-migration API access review with the customer's Aptean account team, and falling back to direct database export for Community Edition instances where API access is restricted. We confirm the data access method during discovery.

  • Historical closed transactions require disciplined scoping

    Aptean's own ERP implementation guidance warns against carrying over all historical records without cleansing because duplicate, incomplete, or obsolete data slows cutover and undermines user confidence. We apply a data scope definition phase that agrees with the customer which transaction history to migrate (open AP/AR, current fiscal year, last two fiscal years) versus archive in a separate export file. Records that do not meet minimum completeness thresholds (missing key dates, amounts, or counterparty references) are flagged and excluded unless the customer explicitly overrides.

Migration approach

Six steps for a successful Aptean Compiere ERP to Dolibarr ERP data migration

  1. Discovery and edition assessment

    We audit the source Compiere deployment across edition tier (Community, Professional, Enterprise), database backend (Oracle XE, Oracle Standard/Enterprise, PostgreSQL), Business Partner count and type distribution, Product count with BOM depth analysis, number of Organizations within the Client hierarchy, open AP/AR aging, and chart of accounts structure. We confirm the data access method: Enterprise Edition customers with Aptean Connect API access versus Community Edition customers requiring direct database export. The discovery output is a written migration scope document with record counts per object and a recommendation on which historical transactions to migrate versus archive.

  2. Dolibarr environment provisioning and module activation

    We provision the destination Dolibarr instance with the required modules activated: CRM, Products, Invoicing, Purchases, Stock/Warehouse, Accounting (or Bookkeeping export), and the Manufacturing module if BOM migration is in scope. We configure the multi-price structure to match the number of source price lists, set the base currency from the source accounting schema, and create the initial category hierarchy from the source Product Category tree. Any missing Dolibarr modules are installed from Dolistore before data migration begins.

  3. Schema mapping and entity hierarchy design

    We design the destination schema in Dolibarr. This includes mapping each Compiere Client to a top-level Dolibarr ThirdParty, mapping each Organization within that Client to either a child ThirdParty or a Dolibarr Project, and resolving the parent-child relationship for reporting. We design the Business Partner split (ThirdParty + Contact records) and confirm the mapping with the customer before any data moves. We also define the Chart of Accounts import mapping from the source AccountingXX.csv file to the Dolibarr account structure.

  4. Test migration and reconciliation

    We run a test migration into a non-production Dolibarr environment using production-like data volumes. The customer's finance and operations leads reconcile record counts, spot-check 25-50 records against the Compiere source, and validate that BOM hierarchies, price list structures, and AP/AR aging are preserved correctly. Any mapping corrections (field names, data type mismatches, missing required fields) are documented and fixed before the production migration plan is finalized.

  5. Owner and user reconciliation

    We extract every distinct Compiere user referenced on Business Partner, Product, and transaction records and match them against the destination Dolibarr user table by email. Any Compiere user without a matching Dolibarr user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Multi-org access scopes that Compiere handled at the Organization level are documented as a post-migration permission review item.

  6. Production migration in dependency order

    We run production migration in record-dependency order: Categories (first, as Products and ThirdParties reference them), ThirdParties (from Business Partners), Contacts (split from Business Partners), Products (with category lookups resolved), Warehouses, BOMs (with component Product references resolved), Price List entries, Accounts (from Chart of Accounts), Supplier Invoices (AP), Customer Invoices (AR), and Users. Each phase emits a row-count reconciliation report. We apply a data cleanse pass that excludes records failing minimum completeness thresholds and documents them in an archive export.

  7. Cutover, validation, and handoff

    We freeze Compiere writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dolibarr as the system of record. We deliver a written inventory of any Compiere customizations (Visual Dictionary Editor extensions, custom fields, workflow rules) requiring Dolibarr module equivalents or custom PHP work, along with a recommendation for a Dolibarr implementation partner if extended customization is needed. We support a one-week hypercare window for reconciliation issues. We do not rebuild Compiere workflows or automations as Dolibarr tasks; that is a separate engagement.

Platform deep dives

Context on both ends of the pair

Aptean Compiere ERP logo

Aptean Compiere ERP

Source

Strengths

  • Open-source licensing model with GPL Community Edition and commercial Enterprise Edition options.
  • Multi-organization architecture supporting subsidiaries with independent processes and consolidated executive views.
  • Multi-currency, multi-location, and multilingual support for global discrete manufacturers.
  • Integrated CRM alongside ERP, providing a 360-degree view of customer interactions.
  • Flexible customization without requiring functional upgrades, per Compiere's 'change anything at any time' design principle.

Weaknesses

  • Java JDK 1.6-based client architecture creates a steep developer onboarding curve for teams without Java experience.
  • Service Packs and migration tooling are gated behind Enterprise Edition subscriptions.
  • Limited publicly documented API capabilities and unclear rate-limit specifications.
  • Historical transaction data often carries over unclean, a known risk Aptean itself warns against in migration guidance.
  • Small review corpus (11 reviews on G2, 1 on Capterra) makes independent evaluation difficult for prospective buyers.
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 Aptean Compiere ERP 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

    Aptean Compiere ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Aptean Compiere ERP 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 Aptean Compiere ERP to Dolibarr ERP data migrations

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

Can't find your answer?

Walk through your Aptean Compiere ERP 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 three and five weeks for deployments under 10,000 Business Partners and 2,000 Products with no multi-level BOMs and a single Organization. Migrations with complex multi-level BOMs, more than three subsidiary Organizations, large open AP/AR batches, or historical transaction carry-over (more than two fiscal years of data) move to eight to twelve weeks because of BOM hierarchy preservation, entity reconciliation, and data cleansing scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Aptean Compiere ERP.
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