ERP migration
Field-level mapping, validation, and rollback between Plex Smart Manufacturing Platform and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Plex Smart Manufacturing Platform
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between Plex Smart Manufacturing Platform and Dolibarr ERP.
Complexity
BStandard
Timeline
4-8 weeks
Overview
Moving from Plex Smart Manufacturing Platform to Dolibarr is a platform-scale migration driven by cost reduction and fit-for-purpose narrowing. Plex charges a $3,500-per-month floor plus volume-based fees aimed at mid-to-large manufacturers, which for smaller discrete manufacturers creates a cost structure that no longer justifies the platform's full MES/ERP/IIoT depth. Dolibarr's open-source core handles ERP and CRM with optional manufacturing modules (BOM, Work Orders, Stock) and a Quality module, but it does not include native MES shop-floor control or native IIoT integration. We extract Plex's transactional history (Production Orders, Work Orders, Quality Non-Conformances, Lot Genealogy) in dependency order and load Dolibarr's corresponding modules through Dolibarr's REST API with batch processing and parent-record resolution. We do not migrate Plex's Rockwell Automation hardware integrations, its MES operator dashboards, or its IIoT sensor ingestion pipelines; these require separate evaluation against Dolibarr's capabilities or a complementary MES layer. Workflows, Plex Alerts, and automations are documented and handed off for Dolibarr rebuild by the customer's admin team.
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 Plex Smart Manufacturing Platform 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.
Plex Smart Manufacturing Platform
Items / Products
Dolibarr ERP
Product (Dolibarr Catalogue produits)
1:1Plex Items (manufactured, purchased, and phantom subtypes) map to Dolibarr Products. The Plex item code becomes Dolibarr's ref field, item description becomes label, and unit of measure maps from Plex's UOM to Dolibarr's Units dictionary. Multi-site inventory positions in Plex map to Dolibarr Warehouses (Stock module), one warehouse per Plex site. Phantom items used as BOM components in Plex migrate as Dolibarr Products with type=2 (assembly) but with no stock tracking.
Plex Smart Manufacturing Platform
Production Orders
Dolibarr ERP
Manufacturing Order (Dolibarr OF / orders of manufacture)
1:1Plex Production Orders map to Dolibarr Manufacturing Orders. The Plex production order number becomes Dolibarr's ref_ext, the linked Item becomes the Dolibarr product_to_build, and the requested quantity maps to qty. Status mapping: Plex Released maps to Dolibarr Draft or InProgress depending on whether materials are allocated; Plex Complete maps to Done. Open production orders are migrated first so that downstream Work Orders can reference them. Closed Production Orders migrate as historical records.
Plex Smart Manufacturing Platform
Work Orders
Dolibarr ERP
Workstation Timesheet or Third-party Work Order (Dolibarr fiche projet / work stations)
1:1Plex Work Orders derive from Production Orders and carry their own scheduling, labor, and material allocations. Dolibarr handles work orders through its Project module or its Workstation module (if the Manufacturing (MoM) module is active). We map Plex Work Order status to Dolibarr project status, the assigned employee to a Dolibarr User contact on the project, and linked material allocations to Dolibarr stock movements. Open work orders are migrated before closed ones to maintain sequencing against the parent Production Order.
Plex Smart Manufacturing Platform
Bill of Materials
Dolibarr ERP
Bill of Materials (Dolibarr Nomenclature / BOM)
1:1Plex BOMs are versioned and tied to Items. Multi-level BOMs with component yields, scrap factors, and alternate components require careful sequencing. Dolibarr BOM supports single-level explosion only in its core module; multi-level BOMs require flattening or using Dolibarr's sub-assembly handling. We document the full Plex BOM hierarchy and create either flat BOMs in Dolibarr (one BOM per top-level item with all sub-components exploded) or separate sub-assembly BOMs depending on the customer's Dolibarr configuration preference. Scrap percentages and component yields map to损耗率 and rendements fields.
Plex Smart Manufacturing Platform
Inventory Locations and Bins
Dolibarr ERP
Warehouses and Stock Locations (Dolibarr Entrepôts etlocalisations de stock)
1:1Plex tracks inventory at site, warehouse, and bin level. We extract location assignments and current on-hand quantities per location, preserving multi-plant setups. Dolibarr's Stock module supports Warehouses and sub-locations within warehouses. If Plex uses bin-level tracking within warehouses, we map bins to Dolibarr warehouse sub-locations or create a custom location field on the stock record. On-hand quantities migrate as Dolibarr Stock MOVED (quantity movements) rather than static balances so that the inventory ledger reflects the starting position.
Plex Smart Manufacturing Platform
Quality Non-Conformances
Dolibarr ERP
Quality NCR / Interventions (Dolibarr module Quality or fiche Intervention)
1:1Quality records in Plex are tightly linked to the production transaction that triggered them (lot, work order, item). Dolibarr's Quality module (if enabled) provides NCR tracking with disposition codes. We extract non-conformance dispositions, corrective actions, and associated inspection data, then map them to Dolibarr Interventions or Quality NCR records linked to the corresponding Product and Work Order. If the customer's Dolibarr instance does not include the Quality module, we migrate NCR data as Dolibarr Notes attached to the relevant Product or Work Order records and flag it for the admin to evaluate the Quality module purchase.
Plex Smart Manufacturing Platform
Suppliers and Accounts
Dolibarr ERP
Third Parties (Dolibarr Sociétés - suppliers and customers)
1:manyPlex consolidates supplier and customer data under Accounts with a type field distinguishing them. We split Plex Accounts by type into Dolibarr Third Parties: suppliers become Dolibarr Third Parties with type=1 (supplier), and customers become type=0 (customer). Contact details, payment terms, and approved supplier status migrate. If Plex uses a single Account record for both a supplier and customer relationship, we create two Dolibarr Third Parties linked by the same external ID to preserve the dual relationship.
Plex Smart Manufacturing Platform
Purchase Orders
Dolibarr ERP
Supplier Orders (Dolibarr Commandes fournisseurs)
1:1Plex Purchase Orders link to Accounts and Items, carrying expected dates, quantities, and pricing. We extract open and historical PO records, preserving line-level detail (item, quantity ordered, unit price, expected date). Closed POs migrate as historical records with status=Closed. Dolibarr Commandes fournisseurs line items reference the mapped Product record and the mapped Supplier Third Party. If Plex PO approval workflows are in use, we document the approval chain as part of the automation inventory handoff.
Plex Smart Manufacturing Platform
Lot and Serial Genealogy
Dolibarr ERP
Lot / Serial Number tracking (Dolibarr Batch / Lot numbers)
1:1Lot traceability is a core Plex strength; each lot carries parent-child genealogy across production and inventory transactions. Dolibarr's Stock module supports batch and lot tracking with Eat-by / Sell-by dates but has basic genealogy (lot-to-lot parent-child at time of production). We extract the full Plex traceability tree and create Dolibarr Lot records with batch numbers matching Plex lot codes, and we document the parent-child relationships as Lot genealogy notes in the Dolibarr lot record description or as linked Note records. Destinations that lack the full genealogy depth are flagged during scoping.
Plex Smart Manufacturing Platform
Custom Fields
Dolibarr ERP
Extra Fields (Dolibarr ExtraFields)
1:1Plex supports Custom Fields on most objects, but the set of custom fields and their data types differ per customer implementation. Dolibarr's ExtraFields system provides an equivalent extensible field mechanism per object. We perform a discovery pass using Plex's API to enumerate every custom field across every object before building the migration mapping, then pre-create each Dolibarr ExtraField with the correct type (string, int, float, date, select, checkbox) before importing any record data. This discovery step adds time to the project timeline but is required to prevent data loss.
Plex Smart Manufacturing Platform
Documents and Attachments
Dolibarr ERP
Documents (Dolibarr Documents attached to objects)
1:1Documents attached to Items, Work Orders, or Quality records in Plex's document management system are exported as binary content with file references. Dolibarr attaches documents to Third Parties, Products, Projects, and Intervention records. We export file references and binary content where API access permits and attach them to the corresponding Dolibarr record. Large binary attachments (drawings, CAD files, quality certificates) may exceed Dolibarr's default upload size limits and require server configuration changes. We document all document attachment migration constraints during scoping.
Plex Smart Manufacturing Platform
Financial Transactions
Dolibarr ERP
Accounting Entries and Invoices (Dolibarr Comptabilité and Facturation)
1:1Plex ERP includes core financials (GL, AP, AR). Transactional history, journal entries, and account balances require mapping to Dolibarr's chart of accounts structure. Open AP and AR items migrate as Dolibarr Supplier Invoices (Factures fournisseurs) and Customer Invoices (Factures clients). Historical GL entries migrate to Dolibarr Accounting module as general ledger lines if the customer needs full financial history; otherwise we migrate only the open items and close the historical ledger migration as a separate scope. Chart of accounts mapping is complex and requires a finance-team sign-off on the account mapping matrix.
| Plex Smart Manufacturing Platform | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Items / Products | Product (Dolibarr Catalogue produits)1:1 | Fully supported | |
| Production Orders | Manufacturing Order (Dolibarr OF / orders of manufacture)1:1 | Fully supported | |
| Work Orders | Workstation Timesheet or Third-party Work Order (Dolibarr fiche projet / work stations)1:1 | Fully supported | |
| Bill of Materials | Bill of Materials (Dolibarr Nomenclature / BOM)1:1 | Mapping required | |
| Inventory Locations and Bins | Warehouses and Stock Locations (Dolibarr Entrepôts etlocalisations de stock)1:1 | Fully supported | |
| Quality Non-Conformances | Quality NCR / Interventions (Dolibarr module Quality or fiche Intervention)1:1 | Mapping required | |
| Suppliers and Accounts | Third Parties (Dolibarr Sociétés - suppliers and customers)1:many | Mapping required | |
| Purchase Orders | Supplier Orders (Dolibarr Commandes fournisseurs)1:1 | Fully supported | |
| Lot and Serial Genealogy | Lot / Serial Number tracking (Dolibarr Batch / Lot numbers)1:1 | Mapping required | |
| Custom Fields | Extra Fields (Dolibarr ExtraFields)1:1 | Mapping required | |
| Documents and Attachments | Documents (Dolibarr Documents attached to objects)1:1 | Mapping required | |
| Financial Transactions | Accounting Entries and Invoices (Dolibarr Comptabilité and Facturation)1:1 | Mapping required |
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.
Plex Smart Manufacturing Platform gotchas
Plex Classic vs. new UX split creates data residency ambiguity
Tightly coupled transactional schema causes dependency cascades
Pricing is volume- and module-gated without public tiers
Legacy system integration is a known friction point
Custom Fields vary per customer and require pre-migration discovery
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 module footprint mapping
We audit the source Plex environment across installed modules, active objects (Production Orders, Work Orders, BOMs, Quality records, Lot genealogy depth), custom field definitions (via a discovery pass across every object), and record volumes per object type. We pair this with a Dolibarr module readiness assessment: which manufacturing and quality modules are active or need to be purchased, which Dolibarr version is targeted (LTS stable recommended), and what server infrastructure is available or needs to be provisioned. The discovery output is a written migration scope, a BOM complexity assessment, a genealogy depth review, and a server requirements document.
BOM and genealogy architecture decision
We assess the customer's Plex BOM depth (single-level vs multi-level, yield/scrap factors, versioned revisions) and lot genealogy complexity (single-level lot traceability vs full parent-child genealogy tree). Based on this assessment, we design the Dolibarr BOM strategy: flat BOM migration, sub-assembly decomposition, or a hybrid. We also decide whether full lot genealogy trees migrate as Dolibarr lot records with linked note documentation or whether genealogy history is summarized and archived separately. This decision gates the data model design for all downstream phases.
Schema design and ExtraField provisioning
We design the destination Dolibarr schema: Products (with types and units), Warehouses (per Plex site/location), BOMs (per the chosen BOM strategy), Third Parties (split from Plex Accounts by type), and any custom ExtraFields. We pre-create every ExtraField in Dolibarr with the correct type before any data import so that record inserts land with all custom data intact. Schema is deployed into the target Dolibarr instance and validated before migration data moves. We also configure Dolibarr numbering templates to match or reference Plex's original record numbers where feasible.
Master data migration
We run master data migration in dependency order: Products and Units first, then Warehouses, then Third Parties (suppliers and customers split by Plex Account type), then BOMs (per the BOM strategy), then Lot records (with Plex lot codes as Dolibarr batch numbers). Each phase emits a row-count reconciliation report and a spot-check comparison of 25-50 records against the Plex source. Master data must be fully validated and signed off before transactional data begins loading because Work Orders, Production Orders, and Quality records all reference master data keys.
Transactional history migration
We load Production Orders, Work Orders, Quality Non-Conformances, Purchase Orders, and inventory movements in strict dependency order. Open orders load first (in draft or validated status per Dolibarr's state machine), then closed historical records. Inventory movements load last so that on-hand quantities reflect the correct starting position after all transactional history is applied. We use Dolibarr's REST API with batch chunking and rate-limit handling. Plex custom fields discovered during scoping are included on every record type that carries them.
Lot genealogy and attachment migration
We traverse Plex's lot genealogy trees and create corresponding Dolibarr lot records with batch numbers and, where Dolibarr supports it, parent-child lot references or linked Note records documenting the genealogy. Document attachments exported from Plex are attached to the corresponding Dolibarr records (Product drawings on Products, certificates of conformance on Lots, work instructions on Work Orders). We validate attachment counts against Plex's document registry and flag any that exceeded Dolibarr's upload limits.
Cutover, validation, and automation handoff
We freeze Plex writes during cutover, run a final delta migration of any records modified during the migration window, then switch the system of record to Dolibarr. We deliver a reconciliation report comparing Plex record counts against Dolibarr record counts per object, plus a spot-check sign-off by the customer's operations team. We deliver a written inventory of Plex Alerts, automated actions, and approval workflows that require rebuild in Dolibarr (via Dolibarr's Workflow module, Cron tasks, or custom PHP development). We support a one-week hypercare window for reconciliation issues. Ongoing server administration, Dolibarr module configuration, and workflow rebuild are outside the migration scope and are separate engagements or internal admin tasks.
Platform deep dives
Plex Smart Manufacturing Platform
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Plex Smart Manufacturing Platform and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Plex Smart Manufacturing Platform and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Plex Smart Manufacturing Platform 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
Plex Smart Manufacturing Platform: Not publicly documented; Plex advises contacting their support for API rate limit specifics per customer tier.
Data volume sensitivity
Plex Smart Manufacturing Platform 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 Plex Smart Manufacturing Platform to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Plex Smart Manufacturing Platform 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 Plex Smart Manufacturing Platform
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.