ERP migration

Migrate from ERPAG to Dolibarr ERP

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

ERPAG logo

ERPAG

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between ERPAG and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from ERPAG to Dolibarr is a transition from a cloud-hosted, tier-gated MRP platform to a self-hosted, modular open-source ERP. ERPAG's plan model gates Customization, Customer Portal, and Automation behind the Advanced tier ($199/month), while Dolibarr ships these capabilities in its Community download with server hosting costs that start under $10/month on basic VPS. We extract ERPAG's transaction-heavy data model through the Smart API and map Items to Dolibarr Products, Customers and Suppliers to Third Parties, Sales Orders to Orders, Purchase Orders to Supplier Orders, Work Orders to Manufacturing Orders (when the BOM module is activated), and BOMs to their Dolibarr equivalents. ERPAG's double-SKU layer on supplier records is preserved so the supplier's own SKU remains linked to ERPAG's internal SKU. We do not migrate ERPAG's Automation scripts, B2B Portal configurations, or Blockly-based customizations as code; we deliver a written inventory of these for the customer's admin to rebuild in Dolibarr or a Dolistore module.

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

ERPAG logo

ERPAG

What's pushing teams away

  • No human resources module — businesses needing employee tracking, payroll, or HR workflows must bolt on a separate system or migrate entirely.
  • Limited third-party app integrations beyond the advertised eCommerce and QuickBooks connectors; some users report difficulty finding or enabling integrations.
  • Manufacturing cost estimation gaps cause frustration when input prices fluctuate due to inflation, exchange rates, or supply disruptions.
  • Advanced features like Automation and Customer Portal are gated behind the Advanced plan, pushing growing companies toward unexpected upgrade costs.
  • The platform lacks negative inventory handling, and concurrent-user write conflicts can create phantom negative quantities that require manual repair.

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

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

ERPAG

Items

maps to

Dolibarr ERP

Product

1:1
Fully supported

ERPAG Items map to Dolibarr Products with SKU, description, cost, price, stock levels (serial, lot, batch), and barcode data preserved. ERPAG composite products (kits, variable items) map to Dolibarr Products with BOM links where the BOM module is activated. Multi-UOM items from ERPAG require a Dolistore unit-conversion module or manual tracking since Dolibarr's standard product does not natively enforce UOM conversion rates.

ERPAG

Customer

maps to

Dolibarr ERP

Third Party (Customer mode)

1:1
Fully supported

ERPAG Customer records map to Dolibarr Third Parties with mode set to Customer. Contact info, billing address, shipping address, and financial overview fields transfer directly. ERPAG's B2B portal assignment does not migrate as a configuration; the customer's portal access rules must be rebuilt in Dolibarr via a self-hosted webroot or Dolistore portal module after migration.

ERPAG

Supplier

maps to

Dolibarr ERP

Third Party (Supplier mode)

1:1
Fully supported

ERPAG Supplier records map to Dolibarr Third Parties with mode set to Supplier. The double-SKU layer (supplier's own SKU alongside ERPAG's internal SKU) is preserved as two separate SKU fields in Dolibarr's supplier product reference so that purchase order matching against the supplier's catalog remains accurate post-migration.

ERPAG

Sales Order

maps to

Dolibarr ERP

Order

1:1
Fully supported

ERPAG Sales Orders map to Dolibarr Orders with line items, pricing, payment status, and packing list associations preserved. The payment_status column exported from ERPAG maps to Dolibarr's Facture (invoice) status and Order status combination. Linked packing lists transfer as delivery notes if Dolibarr's Expedition module is activated.

ERPAG

Invoice

maps to

Dolibarr ERP

Invoice (Facture)

1:1
Fully supported

ERPAG Invoices map to Dolibarr Factures. Credit notes from ERPAG map to Dolibarr credit notes (negative Factures). Invoice status, amount, tax, and payment information transfer directly. Historical invoices with original tax jurisdiction values (see localization gotcha) are preserved as-is to maintain audit trail consistency.

ERPAG

Purchase Order

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

ERPAG Purchase Orders map to Dolibarr Supplier Orders with supplier reference, line items, double-SKU entry, goods-received state, and fulfillment logic preserved. Goods received notes transfer as Dolibarr receptions if the Expedition/Reception module is activated. Purchase order approval workflows from ERPAG do not migrate as automation; we document the workflow steps for admin rebuild in Dolibarr.

ERPAG

Quotation

maps to

Dolibarr ERP

Proposal

1:1
Fully supported

ERPAG Quotations (estimates) map to Dolibarr Commercial Proposals. Validity dates, custom fields, and full pricing transfer directly. Quotations convertible to Sales Orders migrate as Proposal records; the conversion action must be re-established in Dolibarr by the admin post-migration.

ERPAG

Work Order

maps to

Dolibarr ERP

Manufacturing Order

1:1
Fully supported

ERPAG Work Orders map to Dolibarr Manufacturing Orders when the MRP/Manufacturing module is activated. BOM references, production status, estimated vs. actual cost, and work order timestamps transfer directly. Multi-level BOM nesting requires BOM explosion during export so that sub-assemblies are correctly resolved at migration time rather than relying on Dolibarr's BOM routing during order launch.

ERPAG

Bill of Materials (BOM)

maps to

Dolibarr ERP

BOM

1:1
Fully supported

ERPAG BOMs map to Dolibarr BOMs with multi-level product structures preserved. We export BOM records as part of the Items export where BOMs are associated, or as standalone work order source data. Multi-level BOM nesting is resolved into flat BOM line imports during the transform phase so that Dolibarr's BOM explosion does not introduce missing-component errors on import.

ERPAG

Warehouse

maps to

Dolibarr ERP

Stock Deposit

lossy
Fully supported

ERPAG Warehouses map to Dolibarr Stock Deposits. Each ERPAG warehouse's independent tax, currency, and price list settings transfer to the corresponding Dolibarr Stock Deposit. We configure the Stock Deposit before item migration so that stock quantities land in the correct warehouse context. Geographic location data from ERPAG warehouses transfers to Dolibarr's location address fields.

ERPAG

Custom Fields

maps to

Dolibarr ERP

Extra Fields

lossy
Mapping required

ERPAG custom fields (up to 15 per document) on Items, Customers, Suppliers, Sales Orders, and Invoices map to Dolibarr Extra Fields. Linked document references (pointing to external files) do not migrate as live links; we export the file URIs as text fields and provide a file migration checklist for the customer's admin to relocate documents to Dolibarr's document folder structure. Custom fields are only exportable from Advanced-plan accounts; we verify plan tier during scoping.

ERPAG

User and User Role

maps to

Dolibarr ERP

User and Group

1:1
Fully supported

ERPAG Users map to Dolibarr Users with role-based permissions. Active vs. inactive status transfers directly. ERPAG permission sets that gate access to documents and modules do not migrate as configuration; Dolibarr's permission model (module-level activation per user or group) must be rebuilt by the admin post-migration. We export the role assignments as a reference document during scoping.

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.

ERPAG logo

ERPAG gotchas

High

API rate limit of 2 requests per second throttles bulk migration speed

High

Localization settings do not retroactively rewrite existing documents

Medium

Plan tier gates Customization, Portal, and Automation features

Medium

No native negative inventory support; phantom negatives require repair step

Low

Delete-all-transactions preserves inventory and contacts, requiring separate scoping

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

  • ERPAG API rate limit caps bulk export throughput

    ERPAG's Smart API enforces a strict 2 req/sec rate limit across all authenticated requests on all plan tiers. For migrations involving thousands of Items, Orders, or Work Orders, this ceiling significantly extends the export window. We handle this by implementing request pacing on our end, chunking historical data by date ranges and object type, and running export phases during off-peak hours to avoid blocking live operations. Large BOM and work order datasets may require an XLS export fallback for the historical cube data in addition to the API pass.

  • Custom Fields and B2B Portal are Advanced-plan gated exports

    Custom document fields, linked document references, B2B portal configuration, and Automation scripts are only accessible on ERPAG's Advanced plan ($199/month). Migrations scoped from a Basic or Professional account cannot export these objects until the customer upgrades. We include a plan-check step in our scoping questionnaire and flag any Advanced-gated objects that appear in the data inventory. If the customer cannot upgrade before migration, we document the missing custom fields as Extra Field definitions for manual entry in Dolibarr.

  • Localization settings do not retroactively rewrite existing documents

    ERPAG's language, currency, date format, and tax code settings are initialized at company creation and do not retroactively apply to existing documents. If a customer changes their base currency or tax jurisdiction after data has been created, all historical documents retain the original values. We flag this during scoping and recommend separating historical document migration from live go-live configuration. For multi-warehouse setups with per-warehouse currency and tax settings, we map each warehouse's independent settings to the corresponding Dolibarr Stock Deposit configuration before item migration begins.

  • No native negative inventory support in ERPAG requires pre-migration repair

    ERPAG does not support negative inventory quantities. Under concurrent write load, a known glitch can create phantom negative balances on Items. The platform provides a 'Repairs and maintenance' button in database settings to correct this. We detect negative quantities during the export phase and apply the repair step before migration begins to prevent bad stock data from landing in Dolibarr. Dolibarr supports negative stock natively, so resolved quantities land cleanly in the destination.

  • Automation scripts and Blockly customizations do not migrate as code

    ERPAG's Automation module and Blockly script-based customizations (including plugin exports, function scripts, and report designer templates) are Advanced-plan features that do not have direct Dolibarr equivalents in the Community edition. We enumerate every active Automation script and Blockly customization during scoping and deliver a written inventory with each script's trigger, conditions, and actions. The customer's admin or a Dolibarr integrator rebuilds these using Dolibarr's built-in workflow engine or a Dolistore automation module. This is a manual handoff step outside standard migration scope.

Migration approach

Six steps for a successful ERPAG to Dolibarr ERP data migration

  1. Discovery and plan-tier verification

    We audit the source ERPAG account across plan tier (Basic/Professional/Advanced), active modules, API usage patterns, custom field count, BOM nesting depth, warehouse count, supplier double-SKU records, and transaction volume by object type. We specifically verify whether the Advanced plan is active since Custom Fields, Automation, and B2B Portal exports require it. The discovery output is a written migration scope document listing all migratable objects, Advanced-gated objects, and a BOM complexity classification (single-level, multi-level, or kit with variable items).

  2. Schema design and module activation plan

    We design the destination Dolibarr configuration before any data moves. This includes activating the relevant Dolibarr modules (Products/Services, Third Parties, Commercial, Stock, BOM/MRP, Projects, HR if applicable), creating Stock Deposits mapped one-to-one to ERPAG Warehouses with matching tax and currency settings, defining Extra Fields corresponding to ERPAG custom fields, and configuring the BOM structure to receive multi-level nests. If Dolibarr is self-hosted, we coordinate with the customer's server environment to verify PHP version, MySQL/MariaDB capacity, and Dolibarr version compatibility before the migration pass.

  3. Sandbox migration and reconciliation

    We run a full migration into a Dolibarr staging environment using production-like data volume. The customer's operations lead reconciles record counts (Products in, Third Parties in, Orders in, Stock levels in) and spot-checks 25-50 records against the ERPAG source. We specifically verify BOM explosion output for multi-level Items, double-SKU mapping on supplier records, and per-warehouse stock quantities. Any mapping corrections, BOM resolution adjustments, or SKU cross-reference fixes are applied here before production migration begins.

  4. Supplier SKU cross-reference and ERPAG API rate-limit pacing

    We extract all supplier records with their dual SKU fields (ERPAG's internal SKU and the supplier's own catalog SKU) and build a cross-reference table during the export phase. The ERPAG Smart API's 2 req/sec rate limit is managed through request pacing and chunked date-range exports. For large purchase order histories, we supplement the API export with ERPAG's XLS export endpoint for the historical cube data. The supplier SKU cross-reference is loaded into Dolibarr as supplier product reference fields on the Third Party records before any purchase order import begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Stock Deposits (warehouse configuration with tax and currency settings), Products (from ERPAG Items with BOM associations), Third Parties (Customers and Suppliers with double-SKU mapping), BOMs (flat line imports for multi-level nests), Sales Orders, Purchase Orders, Invoices and Credit Notes, Work Orders (Manufacturing Orders), Quotation history, and User accounts. Custom field values load after their parent records are in place. Negative quantity detection runs before item stock migration to trigger the ERPAG repair step if needed.

  6. Cutover, delta pass, and automation handoff

    We freeze ERPAG writes during the cutover window, run a final delta migration of any records modified during the migration pass, then enable Dolibarr as the system of record. We deliver the Automation and Blockly script inventory document to the customer's admin team with each script's trigger conditions and recommended Dolibarr workflow equivalent. We support a one-week post-cutover window where we resolve reconciliation issues. We do not rebuild ERPAG Automation scripts as Dolibarr workflows inside standard migration scope; that work is handled by the customer's admin or a Dolibarr integrator as a follow-on engagement.

Platform deep dives

Context on both ends of the pair

ERPAG logo

ERPAG

Source

Strengths

  • Transparent per-seat pricing with a 15-day free trial and no long-term contract required.
  • Built-in MRP (Material Requirements Planning) for manufacturing businesses with BOM management and work order tracking.
  • Multi-warehouse support with per-warehouse tax, currency, and price list settings.
  • B2B customer portal with Stripe payment integration for wholesale and field-agent self-service ordering.
  • Customization via JSON/XML designer and Blockly scripting allows building custom document types and API endpoints.

Weaknesses

  • No native HR or payroll module, requiring a separate system for employee management.
  • Automation and customer portal features are Advanced-plan exclusives, limiting functionality at lower tiers.
  • API is rate-limited to 2 requests per second, making large historical data migrations time-intensive.
  • No support for negative inventory quantities; concurrent writes can create phantom negative balances requiring manual cleanup.
  • Limited third-party ecosystem compared to larger ERPs, with fewer pre-built connectors beyond eCommerce platforms.
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. All 8 core objects map 1:1 between ERPAG and Dolibarr ERP.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across ERPAG and Dolibarr ERP.

  • Object compatibility

    A

    All 8 core objects map 1:1 between ERPAG and Dolibarr ERP.

  • 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

    ERPAG: 2 requests per second.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your ERPAG to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Straightforward migrations under 10,000 Items and 3,000 Customers with single-level BOMs and one or two warehouses land between three and five weeks. Migrations with multi-level nested BOMs, five or more warehouses with independent tax and currency settings, large purchase order histories (over 2,000 POs), or dual SKU supplier records move to eight to twelve weeks because of BOM explosion resolution, per-warehouse tax jurisdiction reconciliation, and the ERPAG API rate-limit pacing on bulk exports.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ERPAG.
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