ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between Aptean Compiere ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty + Contact
1:manyCompiere'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
Dolibarr ERP
ThirdParty entity or Project
1:1Compiere'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
Dolibarr ERP
Product
1:1Compiere 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
Dolibarr ERP
Bill of Materials (manufacturing module)
1:1Compiere 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
Dolibarr ERP
Warehouse
1:1Compiere 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
Dolibarr ERP
Product Price (multi-price)
lossyCompiere 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
Dolibarr ERP
Account (Accounting module)
1:1Compiere'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
Dolibarr ERP
Supplier Invoice
1:1Open 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
Dolibarr ERP
Customer Invoice
1:1Open 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
Dolibarr ERP
Category
1:1Compiere 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
Dolibarr ERP
User
1:1Compiere 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
Dolibarr ERP
Accounting Configuration
lossyCompiere'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.
| Aptean Compiere ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Business Partner | ThirdParty + Contact1:many | Fully supported | |
| Organization | ThirdParty entity or Project1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Bill of Materials | Bill of Materials (manufacturing module)1:1 | Fully supported | |
| Warehouse and Locator | Warehouse1:1 | Fully supported | |
| Price List | Product Price (multi-price)lossy | Fully supported | |
| Chart of Accounts | Account (Accounting module)1:1 | Mapping required | |
| Open Accounts Payable | Supplier Invoice1:1 | Fully supported | |
| Open Accounts Receivable | Customer Invoice1:1 | Fully supported | |
| Product Category | Category1:1 | Fully supported | |
| User and Role | User1:1 | Fully supported | |
| Accounting Schema | Accounting Configurationlossy | 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.
Aptean Compiere ERP gotchas
Service Packs gated behind Enterprise Edition
Multi-organization hierarchy affects data scoping
Oracle and PostgreSQL database edition differences
Historical transaction carry-over without cleansing
Unclear API rate limits and bulk endpoint availability
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 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.
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.
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.
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.
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.
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.
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
Aptean Compiere ERP
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 Aptean Compiere ERP 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
Aptean Compiere ERP: Not publicly documented.
Data volume sensitivity
Aptean Compiere 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 Aptean Compiere ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Aptean Compiere 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.