ERP migration

Migrate from Plex Smart Manufacturing Platform to Dolibarr ERP

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 logo

Plex Smart Manufacturing Platform

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

objects map 1:1 between Plex Smart Manufacturing Platform and Dolibarr ERP.

Complexity

BStandard

Timeline

4-8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Plex Smart Manufacturing Platform logo

Plex Smart Manufacturing Platform

What's pushing teams away

  • Pricing structure including $3,500/month floor plus per-user or volume-based fees creates significant total cost of ownership that strains smaller and mid-sized manufacturers.
  • Reporting and business intelligence are widely described as difficult to configure, with many customers resorting to external BI tools or manual spreadsheet work to get the insights they need.
  • Workflow customization is constrained; specialized platform knowledge or professional services engagements are required for even minor customizations, limiting agility.
  • Legacy system integration presents challenges, particularly for manufacturers with older ERP or custom systems that do not have pre-built Plex connectors.
  • Some features remain in Plex Classic and have not fully migrated to the newer UX, creating a split experience that can feel inconsistent and lead to usability issues.

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 Plex Smart Manufacturing Platform objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

Product (Dolibarr Catalogue produits)

1:1
Fully supported

Plex 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

maps to

Dolibarr ERP

Manufacturing Order (Dolibarr OF / orders of manufacture)

1:1
Fully supported

Plex 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

maps to

Dolibarr ERP

Workstation Timesheet or Third-party Work Order (Dolibarr fiche projet / work stations)

1:1
Fully supported

Plex 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

maps to

Dolibarr ERP

Bill of Materials (Dolibarr Nomenclature / BOM)

1:1
Mapping required

Plex 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

maps to

Dolibarr ERP

Warehouses and Stock Locations (Dolibarr Entrepôts etlocalisations de stock)

1:1
Fully supported

Plex 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

maps to

Dolibarr ERP

Quality NCR / Interventions (Dolibarr module Quality or fiche Intervention)

1:1
Mapping required

Quality 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

maps to

Dolibarr ERP

Third Parties (Dolibarr Sociétés - suppliers and customers)

1:many
Mapping required

Plex 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

maps to

Dolibarr ERP

Supplier Orders (Dolibarr Commandes fournisseurs)

1:1
Fully supported

Plex 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

maps to

Dolibarr ERP

Lot / Serial Number tracking (Dolibarr Batch / Lot numbers)

1:1
Mapping required

Lot 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

maps to

Dolibarr ERP

Extra Fields (Dolibarr ExtraFields)

1:1
Mapping required

Plex 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

maps to

Dolibarr ERP

Documents (Dolibarr Documents attached to objects)

1:1
Mapping required

Documents 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

maps to

Dolibarr ERP

Accounting Entries and Invoices (Dolibarr Comptabilité and Facturation)

1:1
Mapping required

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

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.

Plex Smart Manufacturing Platform logo

Plex Smart Manufacturing Platform gotchas

High

Plex Classic vs. new UX split creates data residency ambiguity

High

Tightly coupled transactional schema causes dependency cascades

Medium

Pricing is volume- and module-gated without public tiers

Medium

Legacy system integration is a known friction point

Low

Custom Fields vary per customer and require pre-migration discovery

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

  • Plex MES and IIoT data has no Dolibarr destination

    Plex's MES shop-floor features (real-time production tracking, operator dashboards, guided work instructions, paperless operations) and IIoT sensor ingestion from Rockwell Automation hardware have no equivalent in Dolibarr. We do not migrate MES operator data, machine cycle counts, PLC-sourced sensor data, or production monitoring logs. Manufacturers relying on Plex's real-time shop floor visibility need to evaluate whether Dolibarr's production tracking capabilities meet their operational needs or whether a separate MES layer is required post-migration. We document the MES and IIoT data scope during discovery so the customer makes an informed decision before cutover.

  • Plex's tightly coupled transactional schema causes dependency cascades

    Plex enforces referential integrity across its data model: a Quality Non-Conformance references a Work Order, which references a Production Order, which references an Item and a Bill of Materials. Migrating in the wrong sequence causes foreign-key failures or orphaned records in Dolibarr. We build a dependency graph upfront and load records in the correct order: master data first (Products, Third Parties, Warehouses), then BOMs, then Production Orders, then Work Orders, then Quality records, then inventory movements, then open POs last. We flag any orphaned Plex records (e.g., a Work Order referencing a deleted Item) before migration so the customer can clean or document them.

  • Plex Classic vs new UX split creates data residency ambiguity

    Plex operates two interface environments: Plex Classic and the newer Plex UX. Certain features and data are locked to one environment or the other, and some records may have originated in Classic but display in the new UX. During migration scoping, we identify which objects and custom fields live in each environment and extract from the correct underlying API endpoint. If we pull only from one endpoint, records created in the alternate environment may be missed entirely, leading to incomplete data migration. This risk is elevated for customers who have been on Plex for several years and may have mixed-environment records.

  • Dolibarr's BOM depth may not match Plex's multi-level structure

    Plex BOMs support multi-level nesting with per-level yield and scrap factors, alternate components, and versioned revisions. Dolibarr's BOM module (Nomenclature) supports single-level BOMs natively; multi-level assembly exploded BOMs require either flattening (creating one BOM per top-level item with all sub-components at one level) or using Dolibarr's sub-product handling with manual explosion. We assess the customer's BOM complexity during discovery and recommend either a flat BOM migration strategy or a phased approach where sub-assemblies become separate Products with their own BOMs. The chosen strategy affects BOM migration time and the accuracy of material cost rollup post-migration.

  • Dolibarr is self-hosted, requiring infrastructure and maintenance responsibility

    Dolibarr runs on a customer-provided or hosted server (Linux, Apache/Nginx, PHP, MySQL/MariaDB) rather than a managed SaaS platform. Manufacturers moving from Plex's fully managed cloud experience take on server provisioning, PHP version maintenance, security patching, and backup management. We provide a Dolibarr server requirements specification and can assist with initial server setup as a separate engagement, but ongoing server administration and hosting costs fall outside the migration scope. This is a material operational difference from Plex and should be factored into the total cost of ownership comparison.

Migration approach

Six steps for a successful Plex Smart Manufacturing Platform to Dolibarr ERP data migration

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

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

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

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

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

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

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

Context on both ends of the pair

Plex Smart Manufacturing Platform logo

Plex Smart Manufacturing Platform

Source

Strengths

  • Cloud-native single-instance multi-tenant SaaS with 99.5% SLA and always-current versioning, eliminating patching overhead for manufacturers.
  • Unifies MES, ERP, QMS, and IIoT in one platform, removing data silos between shop floor and back-office that plague general-purpose ERPs.
  • Strong lot genealogy and traceability for regulated industries like automotive, aerospace, and food & beverage with strict quality audit requirements.
  • Native integration with Rockwell Automation hardware (Allen-Bradley PLCs) for real-time IIoT data ingestion from the plant floor.
  • Unlimited user licensing model with named or concurrent user options, providing predictability for growing manufacturing organizations.

Weaknesses

  • Pricing starts at $3,500/month plus per-user or volume-based fees, creating significant cost burden for small and mid-sized manufacturers.
  • Steep learning curve with extensive training required; the manufacturing-specific concepts take time for new users to internalize.
  • Business intelligence and reporting tools are difficult to configure, driving many customers to external BI tools for analytical needs.
  • Customization flexibility is constrained; even minor workflow changes often require specialized platform knowledge or paid professional services.
  • Some functionality remains in Plex Classic interface and has not migrated to the newer UX, creating an inconsistent user experience.
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 Plex Smart Manufacturing Platform and Dolibarr ERP.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Plex Smart Manufacturing Platform and Dolibarr ERP.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Plex Smart Manufacturing Platform 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

    Plex Smart Manufacturing Platform: Not publicly documented; Plex advises contacting their support for API rate limit specifics per customer tier.

  • Data volume sensitivity

    B

    Plex Smart Manufacturing Platform doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Plex Smart Manufacturing Platform 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 Plex Smart Manufacturing Platform to Dolibarr ERP data migrations

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

Can't find your answer?

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 consultation

Most migrations land between four and eight weeks for accounts with master data (Items, Suppliers, Customers), BOMs, open Work Orders, and transactional history under 50,000 records with single-level BOMs and basic lot tracking. Migrations including multi-level Bills of Materials with yield and scrap factors, full lot genealogy trees, Quality Non-Conformance records, documents and attachments, and Plex Custom Fields across all objects move to twelve to twenty weeks because of the discovery pass, BOM strategy work, genealogy traversal, and server infrastructure preparation for Dolibarr.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Plex Smart Manufacturing Platform.
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