ERP migration

Migrate from Base ERP to Dolibarr ERP

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 logo

Base ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

67%

8 of 12

objects map 1:1 between Base ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Base ERP logo

Base ERP

What's pushing teams away

  • Per-order fee can become expensive at scale — at $0.19/order, a seller doing 50,000 orders/month pays ~$9,500/month, pushing them toward Enterprise negotiation or a different platform.
  • Reviewer feedback on Capterra/Gartner notes limited advanced inventory features (e.g., purchase orders, detailed sales statistics) compared to dedicated WMS or full ERP platforms.
  • Onboarding complexity — users report the feature breadth can feel overwhelming for first-time users, requiring meaningful setup time across modules.
  • Limited fit for businesses needing deep ERP financials (multi-entity GL, manufacturing BOM, fixed assets) — base.com is order/inventory-centric, not a financial ERP.
  • Freemium tier caps data retention at 6 months — sellers needing longer historical data must upgrade to Business or Enterprise.

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

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

maps to

Dolibarr ERP

Product (physical goods) and Service (non-physical)

1:many
Fully supported

Base 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

maps to

Dolibarr ERP

Warehouse (Stock Location)

1:1
Fully supported

Base 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

maps to

Dolibarr ERP

Product Stock (Stock Movement log)

1:1
Fully supported

Real-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

maps to

Dolibarr ERP

Product Price (Multi-price)

lossy
Fully supported

Base 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

maps to

Dolibarr ERP

Order (Customer Order) and Proposal

1:1
Fully supported

Base 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)

maps to

Dolibarr ERP

Third Party (client type)

1:1
Fully supported

Base 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)

maps to

Dolibarr ERP

Third Party (supplier type)

1:1
Fully supported

Base 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

maps to

Dolibarr ERP

Channel Configuration (documentation only)

1:1
Fully supported

Base 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

maps to

Dolibarr ERP

User

1:1
Fully supported

Base 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

maps to

Dolibarr ERP

Extrafields (Products/Services)

lossy
Fully supported

Base 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)

maps to

Dolibarr ERP

Product Stock (versioned snapshot)

lossy
Fully supported

The 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

maps to

Dolibarr ERP

Invoice (Customer Invoice)

1:1
Fully supported

Base 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.

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.

Base ERP logo

Base ERP gotchas

High

Inventory Control module is in public beta

Medium

Duplicate SKUs accumulate in long-running accounts

High

Marketplace connector credentials are non-exportable

Medium

Order export excludes records from paused connectors

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

  • Dolibarr's date format validation rejects non-strict imports

    Dolibarr's CSV import enforces a strict regex for date fields: ^[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9](-[0-9][0-9]?)?$ matching YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. A documented GitHub issue (Dolibarr #24700) shows imports failing with ambiguous date formats from external systems. We normalize all dates from Base ERP to strict ISO 8601 format before import and validate against this regex before loading. Source systems that use DD/MM/YYYY or MM/DD/YYYY will fail without pre-transformation.

  • Marketplace connector credentials cannot migrate

    BaseLinker connector profiles store channel API keys, OAuth tokens, and marketplace account credentials that are not accessible via export. We export the connector configuration (channel type, listing IDs, sync rules) as a written map, but customers must manually re-enter all credentials at the destination. Channels on eBay, Amazon, Allegro, and other marketplaces need fresh OAuth flows and re-authorization. We recommend scheduling the credential re-entry before the Base ERP read-only freeze so there is no channel downtime at cutover.

  • Beta Inventory Control records require schema versioning

    Base ERP's Inventory Control module is marked beta in official documentation, meaning field names, data types, and behavior can change without notice. We flag any records in this module, extract them under a versioned schema snapshot (including module version number at extraction time), and load them as flagged Stock Movement entries in Dolibarr. Customers using Inventory Control should validate the migrated records manually and treat them as provisional until the module reaches general availability.

  • Dolibarr separates Products and Services—Offer taxonomy must split

    Base ERP's Offer object does not distinguish physical goods from services. Dolibarr requires a deliberate choice between Product (physical, tracked in stock) and Service (non-physical, not tracked in stock) when creating catalog records. We compute the split using product weight, dimensions, and naming patterns, but customers should validate the classification post-migration. Services imported as Products will consume unnecessary warehouse space; Products imported as Services will not appear in stock reports.

  • Third Party object covers both customers and suppliers

    Dolibarr uses a single Third Party object for all external entities and distinguishes them with a type flag (Customer, Supplier, Prospect, or a combination). Base ERP may treat customers and suppliers as distinct or loosely typed entities. We map each entity to the appropriate Third Party type and flag any ambiguous records for customer validation. Entities that are both customers and suppliers require both flags set on the same Third Party record, which Dolibarr supports but requires explicit configuration.

Migration approach

Six steps for a successful Base ERP to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Base ERP logo

Base ERP

Source

Strengths

  • Deep marketplace integrations across European and global sales channels
  • Inventory and order management designed specifically for multi-channel e-commerce
  • Centralized stock synchronization across warehouses and platforms
  • Two-tier ERP support via BaseLinker bridge to external ERP systems
  • Affordable pricing for small to mid-sized online sellers

Weaknesses

  • Limited ERP depth—core financials, manufacturing, and HR modules are absent or minimal
  • Beta features like Inventory Control introduce schema instability during migration windows
  • Offer synchronization requires manual setup for external Shopify or WooCommerce catalogs
  • Limited API documentation makes programmatic export scoping challenging without a partner account
  • Customer support responsiveness varies based on plan tier and ticket volume
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 Base ERP and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between Base ERP 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

    Base ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Migrations under 5,000 product offers, 3 warehouses, and 10,000 historical orders typically land between three and five weeks. Migrations with large product catalogs (over 20,000 SKUs), complex multi-warehouse stock matrices, Beta Inventory Control records requiring schema versioning, or extensive order history with line-item attachments move to eight to twelve weeks. Timeline depends on data volume, deduplication scope, and customer validation speed.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Base 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