ERP migration
Field-level mapping, validation, and rollback between Base ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Base ERP
Source
Dolibarr ERP
Destination
Compatibility
8 of 12
objects map 1:1 between Base ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Base ERP to Dolibarr is a structural migration that exits a Polish e-commerce-centric platform built around BaseLinker marketplace connectors and enters an open-source ERP/CRM with modular billing, project management, and stock control. Base ERP organizes products as Offers with marketplace-linked pricing and inventory; Dolibarr separates Products (physical goods) from Services and uses a Third Party object for both customers and suppliers. We resolve the Offer taxonomy split (physical goods vs services), map each source Warehouse to a Dolibarr Stock Location, transfer stock quantities as physical stock entries, and document every marketplace connector configuration so the customer can re-enter credentials in Dolibarr's channel setup. Beta-flagged Inventory Control records in Base ERP require a versioned schema snapshot because their structure may change. We do not migrate workflows, automations, or BaseLinker channel credentials as these are non-exportable.
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 Base 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.
Base ERP
Offer
Dolibarr ERP
Product (physical goods) and Service (non-physical)
1:manyBase ERP Offers span physical products and service listings without a consistent type flag. We split at migration time using product dimensions, weight fields, and naming conventions to classify physical goods as Dolibarr Product records and non-physical items as Dolibarr Service records. SKU maps to ref (product reference), name maps to label, description maps to description. Custom product fields from Base ERP migrate as extrafields on the corresponding Dolibarr object.
Base ERP
Warehouse
Dolibarr ERP
Warehouse (Stock Location)
1:1Base ERP Warehouses map directly to Dolibarr Stock Locations under the Stock module. We activate the Stock module in Dolibarr during configuration if not already enabled. Each source Warehouse becomes a Dolibarr entrepot with its name and address preserved. Multi-warehouse accounts require Warehouse type to be set (customer warehouse, supplier warehouse, inventory warehouse) per Dolibarr's entrepot type classification.
Base ERP
Stock Level
Dolibarr ERP
Product Stock (Stock Movement log)
1:1Real-time stock quantities per Warehouse per Product migrate as Dolibarr Stock Movement entries with movement type set to manual correction (TypeMovement = 3) so the quantities land as the opening balance without triggering reorder logic. We take a point-in-time stock snapshot at migration start to ensure a consistent baseline before live sync resumes in Base ERP or at the new destination.
Base ERP
Pricing Rule
Dolibarr ERP
Product Price (Multi-price)
lossyBase ERP per-channel and per-quantity-tier pricing rules require expansion into Dolibarr's Multi-price module. We create a Price Multi customer-level price per source pricing rule, then map channel-specific pricing to Dolibarr customer category price lists. Quantity-tier pricing becomes Dolibarr quantity-based price breaks on the Product Price card.
Base ERP
Order
Dolibarr ERP
Order (Customer Order) and Proposal
1:1Base ERP Orders map to Dolibarr Customer Order records for confirmed sales and Proposal (quotation) records for pre-confirmed orders. We classify by order status: confirmed and in-progress orders become Dolibarr customer orders; draft or pending orders become proposals. Order line items map to order lines with Product reference, quantity, unit price, and VAT rate. Shipping address becomes the delivery address on the order.
Base ERP
Third Party (customer)
Dolibarr ERP
Third Party (client type)
1:1Base ERP customers map to Dolibarr Third Party records with Type = Customer (client type flag). Customer name, address, phone, email, VAT number, and SIRET/SIREN map to their Dolibarr equivalents. Customer-specific pricing rules from Base ERP become Dolibarr customer price agreements (prix spécifiques) on the Third Party record.
Base ERP
Third Party (supplier)
Dolibarr ERP
Third Party (supplier type)
1:1Base ERP suppliers map to Dolibarr Third Party records with Type = Supplier (fournisseur flag). Supplier code, contact name, email, and address map directly. We flag the Third Party as supplier and link any migrated purchase orders to it. Suppliers without any order history still migrate as Third Party records for future procurement use.
Base ERP
Marketplace Connector
Dolibarr ERP
Channel Configuration (documentation only)
1:1Base ERP BaseLinker connector profiles store channel type, listing IDs, sync rules, and non-exportable credentials. We export the connector mapping table (channel, offer ID, sync status) as a written configuration document. Customers must manually re-enter API credentials at the destination. We document every channel-to-product mapping so nothing is lost during reconnection. This is a configuration handoff, not a data migration.
Base ERP
User / Owner
Dolibarr ERP
User
1:1Base ERP users with roles (Admin, Operator, Warehouse Manager) map to Dolibarr User records. We match by email and preserve role assignments as Dolibarr permission profiles. Base ERP warehouse-level operator assignments map to Dolibarr warehouse-specific user permissions if the Stock module's advanced permissions are enabled. Inactive users from Base ERP migrate as inactive Dolibarr users for audit continuity.
Base ERP
Custom Product Field
Dolibarr ERP
Extrafields (Products/Services)
lossyBase ERP custom product fields (certifications, seasonal flags, custom dimensions) export as extra columns in the product CSV. We create matching extrafield definitions in Dolibarr's Products and Services tables using the ExtraFields module, type-cast values (date, integer, select, text), and attach them to the migrated records. Custom field metadata is preserved in a migration reference document.
Base ERP
Beta Inventory Control (if present)
Dolibarr ERP
Product Stock (versioned snapshot)
lossyThe Base ERP Inventory Control module is explicitly beta. We extract its current schema version and data snapshot before migration, store it as a versioned JSON export, and load it into Dolibarr as a separate Stock Movement log with a migration_note flag. Customers should validate this data manually after migration because the beta schema may change between now and general availability.
Base ERP
Invoice
Dolibarr ERP
Invoice (Customer Invoice)
1:1Base ERP does not natively generate invoices—these are typically handled by external accounting integrated via BaseLinker. If any invoice records exist in Base ERP (e.g., from a connected module or legacy data), we map them to Dolibarr Customer Invoice records. For most accounts, invoice data is not present in Base ERP and customers export from their external accounting tool separately. We flag this explicitly in the pre-migration audit.
| Base ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Offer | Product (physical goods) and Service (non-physical)1:many | Fully supported | |
| Warehouse | Warehouse (Stock Location)1:1 | Fully supported | |
| Stock Level | Product Stock (Stock Movement log)1:1 | Fully supported | |
| Pricing Rule | Product Price (Multi-price)lossy | Fully supported | |
| Order | Order (Customer Order) and Proposal1:1 | Fully supported | |
| Third Party (customer) | Third Party (client type)1:1 | Fully supported | |
| Third Party (supplier) | Third Party (supplier type)1:1 | Fully supported | |
| Marketplace Connector | Channel Configuration (documentation only)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Product Field | Extrafields (Products/Services)lossy | Fully supported | |
| Beta Inventory Control (if present) | Product Stock (versioned snapshot)lossy | Fully supported | |
| Invoice | Invoice (Customer Invoice)1: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.
Base ERP gotchas
Inventory Control module is in public beta
Duplicate SKUs accumulate in long-running accounts
Marketplace connector credentials are non-exportable
Order export excludes records from paused connectors
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
Pre-migration audit and scope definition
We audit the Base ERP account across offers catalog, warehouse count, stock snapshot, order history, user list, active marketplace connectors, and any Beta Inventory Control records. We run a similarity analysis on product names and SKUs to surface duplicates accumulated over years of use. We extract the connector configuration table (channel, offer ID, sync rules) and document it separately for manual reconnection. The audit output is a written migration scope with record counts, a deduplication recommendation, and a connector reconnection checklist.
Dolibarr environment setup and module activation
We provision or validate the target Dolibarr environment (self-hosted or DoliCloud). We activate required modules: Third Parties (for customers and suppliers), Products and Services (for the catalog), Stock (for warehouses and stock movements), Orders and Proposals (for sales records), and ExtraFields (for custom product fields). We configure multi-currency if the source uses multiple currencies, and enable the Multi-price module if source pricing rules require per-customer price lists. Dolibarr version compatibility is validated against the latest LTS release before schema deployment.
Offer taxonomy split and deduplication
We split Base ERP Offers into Dolibarr Products (physical goods) and Services (non-physical) using weight, dimensions, and naming patterns. We apply the deduplication results from the pre-migration audit—merging or archiving duplicate SKUs and test listings per customer approval. Each remaining Offer maps to a Dolibarr record with SKU as ref, name as label, and description preserved. Custom product fields become Dolibarr extrafields on the Product or Service record.
Warehouse mapping and stock migration
We map each Base ERP Warehouse to a Dolibarr Stock Location (entrepot). We take a point-in-time stock snapshot at migration start, then create Dolibarr Stock Movement entries (type 3, manual correction) for each product per warehouse to set the opening balance. Beta Inventory Control records are extracted under a versioned schema snapshot and loaded as flagged Stock Movement entries with a migration_note indicating they are provisional. Stock movements are validated by comparing total unit count in Dolibarr against the source snapshot before proceeding.
Order and Third Party migration in dependency order
We migrate Third Parties first (customers and suppliers as separate type-flagged records), then Orders and Proposals in status order (draft proposals, then confirmed orders). Order line items resolve Product/Service references from the catalog migrated in step 3. Pricing rules from Base ERP are mapped to Dolibarr customer price agreements or multi-price entries. Each phase emits a row-count reconciliation report showing records imported, skipped, and rejected, with reasons for any rejections.
Connector documentation and cutover
We deliver the written connector configuration map documenting every marketplace channel, listing ID, and sync rule from BaseLinker. Customers re-enter API credentials for each marketplace in Dolibarr or their chosen replacement connector tool. We freeze Base ERP writes, run a final delta migration of any records modified during the migration window, then enable Dolibarr as the system of record. We support a one-week post-cutover window for reconciliation issues. Workflows, automations, and BaseLinker-specific sync rules do not migrate; we document them as rebuild tasks for the customer's admin.
Platform deep dives
Base ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Base ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Base ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Base ERP 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
Base ERP: Not publicly documented.
Data volume sensitivity
Base 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 Base ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Base 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 Base 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.