ERP migration

Migrate from Rootstock Cloud ERP to Dolibarr ERP

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

Rootstock Cloud ERP logo

Rootstock Cloud ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

objects map 1:1 between Rootstock Cloud ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Rootstock Cloud ERP to Dolibarr is a structural migration from a Salesforce-native manufacturing suite to an open-source ERP and CRM platform. Rootstock inherits the Salesforce object model for CRM records and layers ERP objects including Items, Sales Orders, Purchase Orders, Work Orders, BOMs, and Inventory Locations on top. Dolibarr's core modules cover Third-Party (Accounts/Contacts), Products, Orders, Invoices, Stock, and Projects, but Dolibarr has no native manufacturing module, no BOM versioning, no Work Order execution tracking, and no native ECO management. We migrate the data that fits Dolibarr's schema directly and flag Work Orders, BOMs, ECOs, and Fixed Assets as records requiring manual rebuild or third-party module installation post-migration. We sequence the migration by establishing the chart of accounts and Item master first, then flowing in open sales and purchase orders, location hierarchies, and on-hand inventory. Custom Salesforce fields on ERP objects are explicitly enumerated during scoping and carried forward as Dolibarr extrafields or stored in a migration audit field.

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

Rootstock Cloud ERP logo

Rootstock Cloud ERP

What's pushing teams away

  • Implementation complexity and resource requirements are significant—the platform's flexibility is a double-edged sword that demands extensive planning and coordination.
  • Financial reporting capabilities are a known gap; customers report limited financial reporting compared to purpose-built finance ERPs.
  • Performance issues and sporadic lags have been noted by users, particularly under heavy transaction volumes or complex BOM structures.
  • The user interface is described as dated and needing improvement compared to more modern ERP alternatives.
  • Customization depth creates long-term maintenance burden—each customization requires ongoing coordination with internal or external Salesforce resources.

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

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

Rootstock Cloud ERP

Customers (Accounts)

maps to

Dolibarr ERP

Third-Party (Dolibarr)

1:1
Fully supported

Rootstock Accounts (CRM layer, Salesforce object) map to Dolibarr Third-Party records. Customer type (Customer / Prospect / Supplier / Both) is set via the s.rowid type field. Address data, payment terms, and credit limits migrate to corresponding Dolibarr fields. We use the Account Name as the dedupe key. Multi-site customer locations in Rootstock (Shipping Addresses, Billing Addresses on Account) map to Dolibarr Addresses linked via the contact_address table.

Rootstock Cloud ERP

Vendors

maps to

Dolibarr ERP

Third-Party (Dolibarr)

1:1
Fully supported

Rootstock Vendors are Account records with the Vendor checkbox enabled. These map to Dolibarr Third-Party records with type = Supplier. W-9/1099 settings and EDI identifiers on the Rootstock Vendor record migrate to Dolibarr extrafields. Multiple vendor sites in Rootstock map to Dolibarr contact addresses on the Supplier Third-Party record.

Rootstock Cloud ERP

Items (Products)

maps to

Dolibarr ERP

Product (Dolibarr)

1:1
Fully supported

Rootstock Item master records map to Dolibarr Products. We transfer Item ID, description, unit of measure, costing method (standard or average from Rootstock maps to Dolibarr PMD), and the stock management flag. Lot and serial control settings from Rootstock Item migrate to the Dolibarr lot tracking configuration on the Product record. Custom fields on the Rootstock Item object (identified during pre-migration schema review) migrate as Dolibarr extrafields.

Rootstock Cloud ERP

Sales Orders

maps to

Dolibarr ERP

Customer Order (Dolibarr)

1:1
Fully supported

Rootstock Sales Orders map to Dolibarr Customer Orders. Header fields (Customer reference, ship-to address, payment terms) and all line items (Item reference, quantity, unit price, discount) transfer directly. Order status in Rootstock (Draft, Pending, Submitted, Shipped, Invoiced) maps to Dolibarr status (Draft, Validated, Shipped, Closed). Partially fulfilled lines are preserved as open line quantities in the Dolibarr order.

Rootstock Cloud ERP

Purchase Orders

maps to

Dolibarr ERP

Supplier Order (Dolibarr)

1:1
Fully supported

Rootstock Purchase Orders map to Dolibarr Supplier Orders. PO header and line structure transfers with vendor reference, terms, and line items. Approval status in Rootstock maps to Dolibarr status. Vendor records must exist in Dolibarr (from the Vendor mapping above) before Purchase Order import to satisfy the fk_soc foreign key. Receipt linkages and partial receipt flags are preserved as order line quantities.

Rootstock Cloud ERP

Bills of Materials (BOMs)

maps to

Dolibarr ERP

Product description or Project (Dolibarr)

lossy
Fully supported

Rootstock BOMs define multi-level component structures with quantities and operations. Dolibarr has no native BOM object. We store the active BOM as structured text in the Product description field (or as a Dolibarr Project attached to the finished product) and flag BOM version history as a Product note field. The customer selects BOM strategy during scoping: plain-text description for simple assemblies, or Project-based structure for complex multi-level BOMs that require reconstruction in a third-party manufacturing module post-migration.

Rootstock Cloud ERP

Work Orders

maps to

Dolibarr ERP

Project (Dolibarr)

1:1
Fully supported

Rootstock Work Orders represent manufacturing operations tied to a Sales Order or standalone job. Dolibarr has no native Work Order or Shop Floor execution object. We migrate Work Order headers as Dolibarr Projects with routing steps and material allocations stored as Project tasks and Project task time entries. Manufacturing status and completion percentages map from Rootstock WO status to Project status. Work Order BOM references are stored as Project notes linking to the BOM mapping above.

Rootstock Cloud ERP

Inventory Locations

maps to

Dolibarr ERP

Warehouse (Dolibarr)

1:1
Fully supported

Rootstock Inventory Locations (warehouses, plants, stock points) map to Dolibarr Warehouses. We transfer location name, address, location type, and ABC analysis codes. Complex multi-level hierarchies in Rootstock (region > plant > warehouse > bin) are flattened into Dolibarr warehouse records with parent-child relationships represented via Dolibarr's warehouse address or custom extrafield rather than a native hierarchy. Circular or orphaned location assignments identified during pre-migration review are flagged for resolution before migration.

Rootstock Cloud ERP

Inventory Balances

maps to

Dolibarr ERP

Stock (Dolibarr)

1:1
Fully supported

Rootstock on-hand inventory quantities per location map to Dolibarr Stock movements linked to Products and Warehouses. The current stock snapshot migrates as a Stock Replenishment or Stock Correction record with transaction date set to the migration date. We preserve the per-location quantity breakdown so that the customer can verify aggregate on-hand matches between systems.

Rootstock Cloud ERP

Purchase Receipts

maps to

Dolibarr ERP

Supplier Reception (Dolibarr)

1:1
Mapping required

Rootstock Purchase Receipts link to POs and update inventory. We migrate receipt records with PO line references and quantity received. Receipt dates and partial receipt flags are reconciled against the destination Supplier Order lines, and any discrepancies are flagged in the reconciliation report for the customer's admin to resolve post-migration.

Rootstock Cloud ERP

Lot and Serial Numbers

maps to

Dolibarr ERP

Lot (Dolibarr)

1:1
Fully supported

Rootstock Lot and Serial Number master records map to Dolibarr Lot records linked to Products. Lot number, expiration date, and supplier reference transfer directly. Serial number assignments with transaction history map to Dolibarr Lot entries with traceability note fields. Full backward lot traceability from Rootstock (receipt to shipment links) is stored in the Lot description field since Dolibarr's lot traceability is batch-level.

Rootstock Cloud ERP

Chart of Accounts

maps to

Dolibarr ERP

Accounting Account (Dolibarr

1:1
Fully supported

Rootstock GL accounts map to Dolibarr Accounting Account records. We transfer account number, name, account type (Asset, Liability, Equity, Revenue, Expense), and segment definitions. Multi-company and intercompany settings from Rootstock are documented separately since Dolibarr's core accounting module does not support multi-company natively; the customer's admin configures intercompany relationships via separate instances or a third-party module post-migration.

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.

Rootstock Cloud ERP logo

Rootstock Cloud ERP gotchas

High

Salesforce edition gating affects available ERP objects

Medium

BOM versioning requires explicit mapping to destination structure

Medium

Multi-site inventory requires location hierarchy pre-mapping

Medium

Salesforce custom fields on ERP objects require explicit field-level mapping

Low

CI/CD and sandbox limitations complicate staging migrations

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 has no native Work Order or BOM module

    Rootstock provides native Work Order management with routing steps, labor estimates, material allocations, and status tracking tied to the shop floor. Dolibarr's core ERP/CRM has no Work Order object and no native BOM management. Work Order headers migrate as Dolibarr Projects, but execution tracking, material kitting, and labor posting require either a third-party manufacturing module (available on the Dolibarr Marketplace) or a manual rebuild. BOMs are stored as product description text or project-linked notes. We disclose this gap during scoping and include the BOM and Work Order data in the migration export so the customer's admin can use it as a reference when rebuilding in the chosen module.

  • BOM versioning collapses to a single active revision

    Rootstock supports BOM versioning with effective dates, alternate BOMs for manufacturing constraints, and ECO-linked revision history. Dolibarr has no BOM versioning model. We extract the BOM version history, identify the current effective BOM by date, and store it as the active revision. All obsolete BOM versions are preserved in a migration audit field (mf_bom_history__c equivalent) on the Dolibarr Product record so the customer's engineering team can reference prior revisions without a native versioning system.

  • Multi-site inventory hierarchy requires pre-mapping

    Rootstock supports complex multi-site hierarchies with regions, plants, warehouses, and bins in a parent-child relationship. Dolibarr's warehouse model is flat with optional address linkage. Organizations with more than one warehouse level must have their location structure reviewed and flattened before migration. We map each Rootstock location to a Dolibarr Warehouse and flag any locations that lose hierarchical context. Circular or orphaned location assignments are raised during scoping for the customer's admin to resolve before migration begins.

  • Salesforce custom fields on ERP objects need explicit field-level mapping

    Rootstock extends the Salesforce data model with custom fields on ERP objects including Sales Order lines, Work Order headers, and Item records. Those fields are not automatically detected by standard export connectors. We perform a pre-migration schema review of the source org to enumerate all custom fields on ERP objects and explicitly include them in the field mapping. Custom fields migrate as Dolibarr extrafields or, for fields with picklist or multi-select values, as structured text if the Dolibarr extrafield type does not support the source field's data type.

  • Salesforce API rate limits affect export throughput

    Rootstock's data lives behind the Salesforce REST and Bulk APIs. We export using the Bulk API 2.0 with batch chunking, exponential backoff on rate limit responses (standard Salesforce limits: 150 API calls per minute for concurrent requests, 10,000 records per Bulk API batch), and parallel polling to maximize throughput. Large BOM structures and historical Work Orders with many line items require additional API calls and extend the export timeline. We size the export plan during discovery based on record counts and complexity.

Migration approach

Six steps for a successful Rootstock Cloud ERP to Dolibarr ERP data migration

  1. Discovery and source schema audit

    We audit the source Rootstock org across Salesforce edition tier, activated ERP modules, and object support level (Growth vs Advanced vs Enterprise determines which ERP objects are available). We enumerate all custom fields on ERP objects, inventory the BOM version history per Item, map the multi-site location hierarchy, and extract record counts for Items, Sales Orders, Purchase Orders, Work Orders, BOMs, inventory locations, and lot/serial numbers. We also identify any Salesforce custom fields on ERP objects that carry business logic and must be preserved. The discovery output is a written migration scope document that flags the manufacturing gap and any gated features.

  2. Dolibarr target schema setup and BOM strategy selection

    We assist the customer's admin with Dolibarr target schema setup: creating Warehouses (mapped from Rootstock locations), configuring the accounting chart (mapped from Rootstock GL accounts), loading Products (mapped from Rootstock Items), and enabling the Stock and Third-Party modules. During this step the customer selects the BOM strategy: plain-text product description, Project-based structure, or a third-party manufacturing module from the Dolibarr Marketplace. We document which approach the customer chooses and structure the migration export accordingly.

  3. Sandbox migration and reconciliation

    We run a full migration into a Dolibarr staging instance (can be a local install or cloud-hosted trial) using production-like data volume. The customer's operations lead reconciles record counts (Third-Parties, Products, Orders, Stock, Projects), spot-checks 25-50 records against the Rootstock source, and reviews the BOM and Work Order representations in Dolibarr. Any schema corrections, field mapping adjustments, or BOM strategy changes happen in this phase. Sign-off on the staging migration is required before production migration begins.

  4. Dependency-ordered data migration

    We run production migration in record dependency order: Third-Parties (Customers and Vendors), Products (with lot/serial settings), Warehouses (location pre-mapping validated), Products in Stock (on-hand balances per warehouse), Customer Orders, Supplier Orders, Projects (Work Orders as Projects), and BOM notes (as Product description or Project notes). Each phase emits a row-count reconciliation report. Any records rejected due to missing parent records (e.g., an Order line referencing a non-existent Product) are held in a retry queue.

  5. Cutover, delta sync, and manufacturing-gap disclosure

    We freeze writes to Rootstock during cutover, run a final delta migration of any records modified during the migration window, and complete the reconciliation pass. We deliver the manufacturing-gap document: a structured export of BOM version history, Work Order header and line data, and ECO references that the customer's admin uses to rebuild manufacturing logic in Dolibarr or the selected third-party module. We do not rebuild Work Orders, BOMs, or ECOs in Dolibarr as part of standard scope.

  6. Hypercare and post-migration support

    We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. Common post-migration questions include how to handle partial Purchase Order receipts, how to post Work Order material issues in the new Project structure, and how to configure lot traceability in Dolibarr's Stock module. We do not provide ongoing admin support, training, or workflow rebuild as standard scope; these are separate engagements.

Platform deep dives

Context on both ends of the pair

Rootstock Cloud ERP logo

Rootstock Cloud ERP

Source

Strengths

  • Built natively on Salesforce—manufacturers get CRM and ERP on a single platform with shared data model and unified reporting.
  • Supports all major discrete manufacturing modes: make-to-stock, make-to-order, configure-to-order, and engineer-to-order.
  • Comprehensive BOM management with multi-level structures, ECO approval workflows, and version control for complex assemblies.
  • Real-time supply chain visibility from procurement through manufacturing to shipment with shop floor tracking.
  • Multi-site and multi-country capabilities with multi-currency support for global manufacturing operations.

Weaknesses

  • Financial reporting module is a documented weakness—customers cite limited financial statement depth compared to purpose-built finance ERPs.
  • User interface is described as dated relative to newer ERP competitors, with occasional performance slowdowns under load.
  • Implementation complexity is high—flexibility creates a configuration burden that requires skilled Salesforce administrators and ERP functional consultants.
  • Customization depth creates technical debt over time as each modification requires ongoing maintenance through Salesforce release cycles.
  • Limited out-of-box functionality for certain vertical-specific needs outside manufacturing and distribution.
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 Rootstock Cloud ERP and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

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

    Rootstock Cloud ERP: Salesforce API rate limits apply—typically 100,000 API calls per 24-hour period for standard Enterprise Edition orgs, with higher limits for Unlimited and Performance editions.

  • Data volume sensitivity

    A

    Rootstock Cloud ERP exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for organizations with fewer than 5,000 Items, 2,000 open orders, and straightforward single-level BOMs. Migrations with complex multi-level BOM structures, large Work Order histories, multi-site inventory hierarchies, or extensive custom Salesforce fields on ERP objects extend to eight to fourteen weeks because of BOM version collapsing, location pre-mapping, and custom field carry-forward scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Rootstock Cloud 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