ERP migration

Migrate from MRPeasy to Dolibarr ERP

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

MRPeasy logo

MRPeasy

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

86%

12 of 14

objects map 1:1 between MRPeasy and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from MRPeasy to Dolibarr is a transition from a purpose-built manufacturing SaaS to a modular open-source ERP/CRM platform. MRPeasy's cloud-only, per-user model offers tight production scheduling but gates API access behind the Unlimited tier and imposes a 3000-line cap on CSV imports. Dolibarr is self-hostable with a free community edition and paid cloud tiers starting at €9 per user per month, but its manufacturing modules (BOM, Workstation, MRP) must be explicitly activated and configured before any production data can land. We handle the export sequencing from MRPeasy (Vendors first, then Storage Locations manually, then Items, BOMs, Routings, and Manufacturing Orders), map multi-level BOMs to Dolibarr's nested product/component structure, and preserve serial and lot tracking metadata through the transfer. Workflows, automations, and the Dynamic Rescheduling engine do not migrate; we deliver a written inventory of any MRPeasy automations requiring rebuild in Dolibarr.

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

MRPeasy logo

MRPeasy

What's pushing teams away

  • API access — required for custom integrations and automated data pipelines — is gated behind the Unlimited plan at $149/user/month, pushing smaller teams toward competitors with API on lower tiers.
  • Per-user pricing compounds quickly: 10 users on Professional costs $690/month versus unlimited-user alternatives at flat rates, making growth expensive to budget for.
  • Integration ecosystem is limited to approximately 14 native integrations versus competitors offering native plus Zapier/Make connectors, making MRPeasy harder to fit into heterogeneous tool stacks.
  • Self-service-only implementation means smaller manufacturers without internal IT competence can struggle with initial data setup and process configuration despite the software's reputation for ease of use.

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

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

MRPeasy

Item (Article/SKU)

maps to

Dolibarr ERP

Product

1:1
Fully supported

MRPeasy Items map to Dolibarr Products. The part number becomes ref (reference code) and description becomes label. Cost from MRPeasy maps to Cost Price in Dolibarr's Price tab. We handle the MRPeasy type split (Stocked vs Non-Stocked vs Service) into Dolibarr's product type field. Inventory quantities are imported separately after the Product record exists. MRPeasy's 3000-line CSV cap applies to Items; we chunk large catalogs before import.

MRPeasy

Vendor (Supplier)

maps to

Dolibarr ERP

Third-Party (type = Supplier)

1:1
Fully supported

MRPeasy Vendors map to Dolibarr Third-Party contacts with Type = Supplier. Vendor code, name, address, and payment terms migrate directly. MRPeasy's documented import sequence puts Vendors before Items because Items reference vendor purchase terms; we follow that dependency order in Dolibarr by creating Third-Parties with supplier role first.

MRPeasy

Bill of Materials

maps to

Dolibarr ERP

Product BOM (Bill of Materials module)

1:1
Fully supported

MRPeasy BOMs map to Dolibarr's BOM module (enabled in Setup -> Modules -> BOM). Multi-level BOMs are preserved by creating the top-level manufactured product first, then linking sub-assemblies as child BOMs. Co-product BOMs from MRPeasy Professional map to Dolibarr BOM lines with quantity ratios. We flag any MRPeasy BOM revision or version data for manual reconciliation in Dolibarr's BOM Revisions tab.

MRPeasy

Routing

maps to

Dolibarr ERP

Project / Task (manufacturing operations)

lossy
Fully supported

MRPeasy Routings define production operation sequences, workstations, and labor times. Dolibarr does not have a native routing object equivalent to MRPeasy's. We map Routings to Dolibarr Projects with Task records representing individual operations, with workstation reference stored in the Task description field. Workstation Groups from MRPeasy must be manually configured in Dolibarr (Dolibarr has a Workstation module that requires activation) before Task records can reference them.

MRPeasy

Manufacturing Order

maps to

Dolibarr ERP

MO (Manufacturing Orders module) or Project

1:1
Fully supported

MRPeasy Manufacturing Orders map to Dolibarr MO records if the MO module is activated (Setup -> Modules -> Manufacturing). Open or active MOs trigger Dolibarr's own scheduling recalculation after import; we flag any MRPeasy Dynamic Rescheduling shifts as a post-import reconciliation delta. Closed MOs migrate as read-only Project records with a closed status flag. We do not migrate the Dynamic Rescheduling engine itself as that is an MRPeasy-specific automation.

MRPeasy

Customer

maps to

Dolibarr ERP

Third-Party (type = Customer)

1:1
Fully supported

MRPeasy Customers map to Dolibarr Third-Party contacts with Type = Customer. Name, contact details, address, and tax ID migrate directly. Customer code becomes ref in Dolibarr. We deduplicate by code match before insert. Price lists attached to customers map to Dolibarr's customer-specific price rules in the Product pricing tab.

MRPeasy

Inventory Level

maps to

Dolibarr ERP

Stock Warehouse + Product Stock

1:1
Fully supported

MRPeasy inventory levels per storage location map to Dolibarr Warehouses (Stock -> Warehouses) with Product Stock records holding current quantities. MRPeasy's 3000-line CSV cap applies to inventory import; a warehouse with 10,000 item-location pairs requires at least four import passes. We pre-create Warehouses in Dolibarr matching MRPeasy Storage Locations before inventory is assigned. Note: MRPeasy Storage Locations cannot be imported via CSV and must be created manually in MRPeasy before export; we replicate that manual setup as Dolibarr Warehouse creation.

MRPeasy

Stock Lot

maps to

Dolibarr ERP

Lot/Serial Number

1:1
Fully supported

MRPeasy Stock Lots with batch number, expiry date, and quantity map to Dolibarr's Lot/Serial module (enabled in Stock -> Lots). The part number links the lot to the correct Product in Dolibarr. We preserve the received status, batch identifier, and expiry date from MRPeasy's lot import fields. Lot traceability reports generated in Dolibarr will reflect the imported lot history.

MRPeasy

Price List

maps to

Dolibarr ERP

Product Price (customer-specific pricing)

1:1
Fully supported

MRPeasy Price Lists define product-specific and customer-specific pricing. We map these to Dolibarr Product Price records with the customer-specific flag set. Currency from MRPeasy's multi-currency pricing becomes Dolibarr's price currency per rule. If MRPeasy tiered pricing (volume breaks) is used, we map to Dolibarr's quantity price breaks per product.

MRPeasy

Custom Fields

maps to

Dolibarr ERP

Extra Fields

1:1
Mapping required

MRPeasy Custom Fields (Professional and above) map to Dolibarr Extra Fields on the corresponding object. MRPeasy field types (free text, number, date, choice) map to Dolibarr types (varchar, int, datetime, select). We pre-create the Extra Field definition in Dolibarr before importing any records with custom field data. Any custom field logic (calculated fields, conditional visibility) does not migrate as configuration.

MRPeasy

User

maps to

Dolibarr ERP

User

1:1
Fully supported

MRPeasy Users map to Dolibarr Users by email match. Role assignments from MRPeasy's permission groups map to Dolibarr's permission set per module (Stock, Manufacturing, Third-Party, etc.). We export MRPeasy user records via table export and create matching Dolibarr users manually or via Dolibarr's user import. Active vs inactive status migrates directly.

MRPeasy

Chart of Accounts

maps to

Dolibarr ERP

Accounting Account

1:1
Mapping required

MRPeasy's accounting module Chart of Accounts maps to Dolibarr's Accounting -> Chart of Accounts. We flag any non-standard account codes or custom account types for manual reconciliation during Dolibarr's accounting setup. Account type mapping (asset, liability, equity, income, expense) preserves the MRPeasy classification. Opening balances migrate as journal entries in Dolibarr's accounting module.

MRPeasy

Workstation Group / Workstation

maps to

Dolibarr ERP

Workstation (manufacturing module)

lossy
Fully supported

MRPeasy Workstation Groups and Workstations cannot be set up via CSV import in MRPeasy and are flagged as a manual configuration requirement on both sides of the migration. We document the full Workstation and Workstation Group structure from MRPeasy (including capacity and hourly cost) and recreate it manually in Dolibarr's Workstation module (Setup -> Modules -> Workstation) before Manufacturing Order import. This is a pre-migration manual step, not an automated data migration.

MRPeasy

Transfer Order

maps to

Dolibarr ERP

Stock Transfer

1:1
Fully supported

MRPeasy Transfer Orders (inter-site stock moves) map to Dolibarr Stock Transfer records. The New, Ready, Shipped, Received, Canceled lifecycle in MRPeasy maps to Dolibarr's transfer status field. In-transit orders at migration time land in Shipped status; the Received completion step in MRPeasy is manual and we document this in the cutover checklist so that pending receipts are completed before go-live.

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.

MRPeasy logo

MRPeasy gotchas

High

API access locked behind Unlimited plan

High

3000-line CSV import cap per upload

High

Workstations and Storage Locations must be manually configured

Medium

Active Manufacturing Orders trigger dynamic rescheduling on import

Low

Transfer Order 'Received' status is manual

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

  • MRPeasy API access is locked behind the Unlimited plan

    MRPeasy exposes its API only on the Unlimited tier at $149 per user per month. On Starter and Professional, there is no programmatic access to Items, BOMs, Manufacturing Orders, or any other object. If a customer wants to migrate data from MRPeasy on a lower tier, we cannot pull via API and must fall back to table-by-table CSV exports, which we then transform and load into Dolibarr. We confirm the customer's plan tier during scoping and adjust the export strategy accordingly. This is a structural constraint of MRPeasy's pricing model, not a migration-specific issue.

  • MRPeasy's 3000-line CSV import cap applies to every object

    MRPeasy enforces a 3000-line limit on any single CSV import (Items, Inventory, Stock Lots, Customers, etc.). Large manufacturers with thousands of SKUs or multi-site inventory must chunk their imports into multiple files. We segment large datasets before import and track partial completion to avoid duplicating already-migrated records. On the Dolibarr side, the Import module also recommends CSV over Excel for performance and can handle multi-pass loads. We coordinate the chunking strategy on both sides.

  • MRPeasy Workstations and Storage Locations cannot be imported

    MRPeasy explicitly states that Workstation Groups and Workstations cannot be set up via CSV import — they must be created manually in Settings. Storage Locations also require manual setup, which impacts how we sequence inventory imports because inventory must be assigned to an existing Storage Location. We create these records manually in MRPeasy's UI before exporting, and recreate the equivalent structure in Dolibarr's Warehouse and Workstation modules before inventory and MO migration. This manual work adds a pre-migration step that is not present in most ERP-to-ERP migrations.

  • Dolibarr's modular activation requires pre-configuration before data lands

    Dolibarr ships with a base CRM module and requires explicit activation of manufacturing-specific modules (BOM, Manufacturing Orders, Workstation, Stock, and Accounting) in Setup -> Modules before any production data can be stored in them. We activate the required modules, configure warehouse structure, and set up the BOM module before importing any Items or Manufacturing Orders. If these modules are not activated, imports will appear to succeed but manufacturing data will not be visible in the expected menus.

  • Active Manufacturing Orders trigger rescheduling on import into Dolibarr

    MRPeasy's Dynamic Rescheduling engine recalculates Manufacturing Order start and end dates based on current capacity and BOM structure after any relevant data change. When we import open Manufacturing Orders into Dolibarr's MO module, Dolibarr's own scheduling engine recalculates dates based on its routing and workstation data. Any mismatch between MRPeasy's capacity assumptions and Dolibarr's configured capacity will shift scheduled dates. We flag open and active MOs during scoping, advise customers to close or freeze orders before import where possible, and document the post-import reschedule delta for the customer's review.

Migration approach

Six steps for a successful MRPeasy to Dolibarr ERP data migration

  1. Discovery and export strategy

    We audit the source MRPeasy instance across plan tier (Starter/Professional/Unlimited), object volume (Items, BOMs, Manufacturing Orders, Inventory lines, Stock Lots), and custom field count. If the customer is on Starter or Professional, API access is unavailable and we plan a CSV export strategy. We identify any Workstations, Workstation Groups, and Storage Locations that require manual creation before export. The discovery output is a written migration scope with object counts, a pre-migration manual checklist, and the export sequencing plan.

  2. Dolibarr module activation and warehouse design

    We activate the required Dolibarr modules (Third-Party, Product, Stock, BOM, Manufacturing Orders, Workstation, Accounting) on the target instance. We design the warehouse structure to match MRPeasy's Storage Locations, create Workstation records to match MRPeasy's Workstation Groups, and configure the BOM module with the appropriate product type settings. This step runs in parallel with MRPeasy manual setup and must be completed before any data import begins.

  3. CSV export from MRPeasy in dependency order

    We export MRPeasy data in the documented dependency sequence: Vendors (Third-Party contacts with supplier role) first, then Customers (Third-Party contacts with customer role), then Items (Products), then Price Lists (Product Prices), then BOMs (BOM module), then Stock Lots (Lots), then Inventory Levels (Product Stock per Warehouse), then Manufacturing Orders (MOs or Projects), then Users, then Chart of Accounts. Each export is chunked to respect MRPeasy's 3000-line cap where applicable. We cross-reference the export counts against the discovery audit to confirm nothing was missed.

  4. Data transformation and Dolibarr import

    We transform the exported CSV files to match Dolibarr's import field names, types, and constraints. This includes splitting MRPeasy Items into Dolibarr Product records, mapping BOM parent-component relationships to Dolibarr's BOM lines, resolving storage location IDs to Dolibarr Warehouse IDs, splitting multi-level BOMs into nested structure, and mapping owner email addresses to Dolibarr User IDs. Any records that fail Dolibarr's validation rules are logged to a reconciliation sheet for the customer's admin to resolve before re-import.

  5. Sandbox import and reconciliation

    If a Dolibarr staging or sandbox environment is available, we run a full import there to validate mapping correctness, BOM integrity, and inventory assignment before touching production. The customer's team spot-checks 25-50 records against the MRPeasy source and signs off the mapping before production migration begins. Corrections to field mapping, BOM structure, or warehouse assignment happen here, not in production.

  6. Production migration and cutover

    We run the production migration in the same dependency order used in staging. Each phase (Vendors, Customers, Products, BOMs, Stock, MOs) emits a row-count reconciliation report before the next phase begins. We freeze MRPeasy write access during the cutover window, run a final delta import of any records modified during migration, and hand off to the customer's team. We do not migrate MRPeasy automations or the Dynamic Rescheduling engine; those are documented in the handoff inventory for the customer's admin to rebuild in Dolibarr's workflow tools.

Platform deep dives

Context on both ends of the pair

MRPeasy logo

MRPeasy

Source

Strengths

  • Generous free trial (15+15 days with demo video and LinkedIn engagement) lowers evaluation risk for small manufacturers.
  • Built-in internet-kiosk and barcode scanning enable shop floor reporting without additional hardware purchases.
  • Production scheduling supports make-to-stock and make-to-order modes with drag-and-drop rescheduling and dynamic auto-rescheduling.
  • Multi-site, multi-stock, and multi-currency support on higher tiers accommodates growing manufacturers with distributed operations.
  • Lot traceability and serial number tracking satisfy basic quality and compliance requirements in regulated manufacturing sectors.

Weaknesses

  • Per-user pricing on every tier inflates costs as teams grow; competitors offer unlimited-user plans at comparable or lower total cost.
  • API access requires Unlimited tier ($149/user), making programmatic migration and custom integrations prohibitively expensive for smaller teams.
  • Limited integrations ecosystem (~14 native) versus competitors with Zapier/Make connectors forces manual data handling in hybrid tool stacks.
  • Self-service-only implementation with no vendor-provided consulting means smaller manufacturers without ERP experience may struggle during initial deployment.
  • Workstations, Workstation Groups, and Storage Locations cannot be imported via CSV — they must be created manually, adding friction to data migration.
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. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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

    MRPeasy: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your MRPeasy 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 5,000 items, 500 BOMs, and 2,000 Manufacturing Orders typically complete in three to five weeks. Migrations with multi-level BOMs, serial number histories, large open-MO queues, or multi-site inventory requiring chunked CSV passes extend to seven to twelve weeks. The pre-migration manual step (creating Workstations and Storage Locations in both platforms) adds one to two weeks of setup time before automated migration begins.

Adjacent paths

Related migrations to explore

Ready when you are

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