ERP migration
Field-level mapping, validation, and rollback between MRPeasy and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
MRPeasy
Source
Dolibarr ERP
Destination
Compatibility
12 of 14
objects map 1:1 between MRPeasy and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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)
Dolibarr ERP
Product
1:1MRPeasy 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)
Dolibarr ERP
Third-Party (type = Supplier)
1:1MRPeasy 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
Dolibarr ERP
Product BOM (Bill of Materials module)
1:1MRPeasy 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
Dolibarr ERP
Project / Task (manufacturing operations)
lossyMRPeasy 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
Dolibarr ERP
MO (Manufacturing Orders module) or Project
1:1MRPeasy 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
Dolibarr ERP
Third-Party (type = Customer)
1:1MRPeasy 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
Dolibarr ERP
Stock Warehouse + Product Stock
1:1MRPeasy 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
Dolibarr ERP
Lot/Serial Number
1:1MRPeasy 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
Dolibarr ERP
Product Price (customer-specific pricing)
1:1MRPeasy 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
Dolibarr ERP
Extra Fields
1:1MRPeasy 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
Dolibarr ERP
User
1:1MRPeasy 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
Dolibarr ERP
Accounting Account
1:1MRPeasy'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
Dolibarr ERP
Workstation (manufacturing module)
lossyMRPeasy 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
Dolibarr ERP
Stock Transfer
1:1MRPeasy 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.
| MRPeasy | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Item (Article/SKU) | Product1:1 | Fully supported | |
| Vendor (Supplier) | Third-Party (type = Supplier)1:1 | Fully supported | |
| Bill of Materials | Product BOM (Bill of Materials module)1:1 | Fully supported | |
| Routing | Project / Task (manufacturing operations)lossy | Fully supported | |
| Manufacturing Order | MO (Manufacturing Orders module) or Project1:1 | Fully supported | |
| Customer | Third-Party (type = Customer)1:1 | Fully supported | |
| Inventory Level | Stock Warehouse + Product Stock1:1 | Fully supported | |
| Stock Lot | Lot/Serial Number1:1 | Fully supported | |
| Price List | Product Price (customer-specific pricing)1:1 | Fully supported | |
| Custom Fields | Extra Fields1:1 | Mapping required | |
| User | User1:1 | Fully supported | |
| Chart of Accounts | Accounting Account1:1 | Mapping required | |
| Workstation Group / Workstation | Workstation (manufacturing module)lossy | Fully supported | |
| Transfer Order | Stock Transfer1: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.
MRPeasy gotchas
API access locked behind Unlimited plan
3000-line CSV import cap per upload
Workstations and Storage Locations must be manually configured
Active Manufacturing Orders trigger dynamic rescheduling on import
Transfer Order 'Received' status is manual
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 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.
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.
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.
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.
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.
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
MRPeasy
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across MRPeasy and Dolibarr ERP.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
MRPeasy: Not publicly documented.
Data volume sensitivity
MRPeasy 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 MRPeasy to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave MRPeasy
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.