ERP migration
Field-level mapping, validation, and rollback between ERPAG and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
ERPAG
Source
Dolibarr ERP
Destination
Compatibility
10 of 12
objects map 1:1 between ERPAG and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
Product
1:1ERPAG 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
Dolibarr ERP
Third Party (Customer mode)
1:1ERPAG 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
Dolibarr ERP
Third Party (Supplier mode)
1:1ERPAG 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
Dolibarr ERP
Order
1:1ERPAG 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
Dolibarr ERP
Invoice (Facture)
1:1ERPAG 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
Dolibarr ERP
Supplier Order
1:1ERPAG 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
Dolibarr ERP
Proposal
1:1ERPAG 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
Dolibarr ERP
Manufacturing Order
1:1ERPAG 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)
Dolibarr ERP
BOM
1:1ERPAG 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
Dolibarr ERP
Stock Deposit
lossyERPAG 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
Dolibarr ERP
Extra Fields
lossyERPAG 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
Dolibarr ERP
User and Group
1:1ERPAG 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.
| ERPAG | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Items | Product1:1 | Fully supported | |
| Customer | Third Party (Customer mode)1:1 | Fully supported | |
| Supplier | Third Party (Supplier mode)1:1 | Fully supported | |
| Sales Order | Order1:1 | Fully supported | |
| Invoice | Invoice (Facture)1:1 | Fully supported | |
| Purchase Order | Supplier Order1:1 | Fully supported | |
| Quotation | Proposal1:1 | Fully supported | |
| Work Order | Manufacturing Order1:1 | Fully supported | |
| Bill of Materials (BOM) | BOM1:1 | Fully supported | |
| Warehouse | Stock Depositlossy | Fully supported | |
| Custom Fields | Extra Fieldslossy | Mapping required | |
| User and User Role | User and Group1:1 | 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.
ERPAG gotchas
API rate limit of 2 requests per second throttles bulk migration speed
Localization settings do not retroactively rewrite existing documents
Plan tier gates Customization, Portal, and Automation features
No native negative inventory support; phantom negatives require repair step
Delete-all-transactions preserves inventory and contacts, requiring separate scoping
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 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).
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.
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.
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.
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.
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
ERPAG
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between ERPAG and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ERPAG and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between ERPAG and Dolibarr ERP.
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
ERPAG: 2 requests per second.
Data volume sensitivity
ERPAG 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 ERPAG to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave ERPAG
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.