ERP migration

Migrate from INNERGY ERP to Dolibarr ERP

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

INNERGY ERP logo

INNERGY ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

objects map 1:1 between INNERGY ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from INNERGY ERP to Dolibarr is a structural migration from a vertical millwork-specific platform to a modular open-source ERP built for small and medium businesses. INNERGY organizes data around Estimates, Jobs, BOMs, Work Orders, and Change Orders tied to a woodworking division structure; Dolibarr uses Projects, Products, Inventory, and Orders with a simpler taxonomy. We sequence the migration starting with Customers and Vendors as parent records, then Jobs with their linked BOM and Work Order chains, preserving the full change order log as a structured table rather than collapsing it into the Job record. Dolibarr's module activation model means we configure the relevant Dolibarr modules (Products, Stock, Projects, Invoices, Suppliers) before importing, and we flag any INNERGY custom fields discovered during API discovery against Dolibarr's extrafield system. Workflows, CAD integration, and the Bottleneck Report do not migrate; we deliver a written inventory of INNERGY automations requiring rebuild in Dolibarr's workflow module or as community scripts.

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

INNERGY ERP logo

INNERGY ERP

What's pushing teams away

  • Custom pricing with no public tiers makes budget planning difficult and creates anxiety during renewal negotiations, as noted in estimator forums discussing total cost of ownership.
  • The implementation complexity and steep learning curve require significant internal resources, with Reddit users estimating months of setup before realizing full value.
  • Integration challenges with third-party business systems, including accounting software and shop-floor equipment, create data silos that negate the unified-platform promise.
  • Insufficient native reporting features force users to supplement with external BI tools or spreadsheet exports for detailed analytical needs.

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

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

INNERGY ERP

Customer

maps to

Dolibarr ERP

ThirdParty (Customer/Supplier)

1:1
Fully supported

INNERGY Customer records map to Dolibarr ThirdParty objects with the IsCustomer flag enabled. We preserve billing and shipping addresses, contact details, and the Jobs list relationship. The ThirdParty object in Dolibarr serves both customer and supplier roles, so we set the appropriate classification flag during import. Customer records must be imported before any Job or Estimate records to satisfy the parent lookup.

INNERGY ERP

Vendor

maps to

Dolibarr ERP

ThirdParty (Supplier)

1:1
Fully supported

INNERGY Vendor records map to Dolibarr ThirdParty objects with the IsSupplier flag enabled. We preserve supplier lead times, preferred items, and any associated purchase history exposed through INNERGY's API. Dolibarr's supplier module links directly to the Products module for material sourcing.

INNERGY ERP

Estimate

maps to

Dolibarr ERP

Proposal/Commercial Proposal

1:1
Fully supported

INNERGY Estimates (covering material takeoffs, labor assumptions, and margin calculation for custom millwork) map to Dolibarr Proposal objects. Line items from the estimate map to ProposalLine rows with product references where applicable. We preserve the estimate status (Draft, Sent, Accepted, Lost) as Dolibarr Proposal status values.

INNERGY ERP

Job

maps to

Dolibarr ERP

Project

1:1
Fully supported

INNERGY Jobs represent the core project record from award through installation and map to Dolibarr Projects. Job metadata (status, assigned staff, client reference) migrates to Project fields. The original Job number becomes the Project reference code. Jobs must be imported after Customers to satisfy the socid (ThirdParty) lookup.

INNERGY ERP

Bill of Materials (BOM)

maps to

Dolibarr ERP

Product (with BOM structure via module)

lossy
Fully supported

INNERGY BOMs auto-generated from CAD geometry or built manually include material specs, quantities, operations routing, and subassembly relationships. Dolibarr's BOM module (an optional extension) handles multi-level product structures. We map top-level BOM items to Dolibarr Products with a bill of materials definition, and subassemblies to child Product BOM entries. Multi-level BOM decomposition is preserved as a parent-child structure.

INNERGY ERP

Work Order

maps to

Dolibarr ERP

Project Task

1:many
Fully supported

INNERGY Work Orders drive shop-floor execution and link to Jobs and BOMs. Each Work Order maps to a Dolibarr Task within the corresponding Project. We preserve Work Order status (Scheduled, In Progress, Completed), assigned operations, and sequencing. If INNERGY exposes multiple Work Orders per Job, we split them into individual Tasks under the same Project.

INNERGY ERP

Change Order

maps to

Dolibarr ERP

Project Note (linked table)

1:1
Fully supported

INNERGY Change Orders modify Job scope and track lineage with approval dates and revised quantities. Dolibarr has no native change order object, so we preserve the full change order log as a structured linked table: a Dolibarr Note attached to the Project with a structured format (CO number, date, description, approved amount, revised quantities) that maintains sequence fidelity for auditors and project managers. The Note includes a reference back to the original Job number.

INNERGY ERP

Inventory Item

maps to

Dolibarr ERP

Product + Stock

1:1
Fully supported

INNERGY Inventory Items with units of measure, reorder points, warehouse locations, and average costs map to Dolibarr Product records with stock levels in the Stock module. We preserve the average cost as the Product purchase or standard cost price and set initial stock quantities from INNERGY's current balances. Warehouse locations map to Dolibarr warehouse records.

INNERGY ERP

Chart of Accounts

maps to

Dolibarr ERP

Account (Accounting module)

1:1
Mapping required

INNERGY's Chart of Accounts configured per-customer during implementation maps to Dolibarr's accounting chart. We export the full account list and map account codes and names to Dolibarr's Plan Comptable (for French localization) or a generic chart. Division-specific cost pools require manual account type classification during scoping.

INNERGY ERP

Open AP/AR

maps to

Dolibarr ERP

Invoice (Supplier Invoice / Customer Invoice)

1:1
Mapping required

Outstanding INNERGY invoices and credit memos represent live financial data that must be reconciled before migration. We extract open payable and receivable records via INNERGY's API and map them to Dolibarr SupplierInvoice and Facture (Customer Invoice) objects in Open status. Open amounts and due dates are preserved so that the customer's accounting team can reconcile and close them in Dolibarr post-migration.

INNERGY ERP

Attachments

maps to

Dolibarr ERP

Document (linked to Project/Product)

1:1
Mapping required

INNERGY stores documents and drawings associated with Jobs, Work Orders, and Estimates—PDFs, images, and CAD files. We export attachments in their native format and link them to the corresponding Dolibarr Project or Product record via the Document module. CAD files are preserved as-is; the customer must have appropriate software to open them post-migration.

INNERGY ERP

Custom Fields

maps to

Dolibarr ERP

Extrafields

lossy
Mapping required

INNERGY's custom fields (including those added through Feature Release 115 for Shipments) map to Dolibarr extrafields on the corresponding objects. We query INNERGY's field definitions via API during discovery and cross-reference against Dolibarr's extrafield system to identify target object, field type, and validation rules. Any orphaned or undocumented custom fields are flagged for the customer's review before schema deployment.

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.

INNERGY ERP logo

INNERGY ERP gotchas

High

INNERGY has no public pricing page

High

Industry-specific data structures resist generic mappings

Medium

Change order history can span multiple Jobs

Medium

Custom fields introduced post-implementation may lack schema documentation

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

  • Change order lineage spans multiple Jobs

    INNERGY Change Orders may reference original Job numbers, client approval dates, and revised quantities across a project lifecycle. If a project accumulates several change orders, the historical sequence matters for accurate job costing. Dolibarr has no native change order object, so we preserve the full change order log as structured Notes attached to the Project, formatted with CO number, date, description, approved amount, and revised quantities. This maintains sequence fidelity for auditors and project managers but requires the customer's team to adopt the Note-based convention.

  • INNERGY custom fields lack schema documentation

    Feature Release 115 confirms INNERGY ships new custom field capabilities over time. Customers who added custom fields during implementation may not have a formal schema export. We query INNERGY's field definitions via the API during discovery and cross-reference against the customer's current export to catch any orphaned or mislabeled custom properties. Custom fields discovered late in migration require schema updates in Dolibarr and re-validation of any records already loaded.

  • CAD-generated BOMs require manual decomposition

    INNERGY BOMs auto-generated from CAD design data may contain geometry-derived material quantities and operations routing that Dolibarr's BOM module cannot interpret natively. We extract the full BOM structure including subassembly relationships and decompose multi-level BOMs into Dolibarr Product BOM entries. The customer should review the decomposed BOM structure in Dolibarr's BOM module before production use, as operations routing from CAD does not automatically map to Dolibarr production task scheduling.

  • Dolibarr production module is basic

    INNERGY's Bottleneck Report and Throughput Widget with MES for shop-floor execution have no equivalent in Dolibarr's core modules. Dolibarr offers a basic production module via extension, but throughput analysis, bottleneck identification, and real-time production visibility require third-party modules or supplemental BI tools. We do not rebuild these features as part of the migration scope.

  • No workflow or automation migration

    INNERGY Workflows, Sequences, and automations do not migrate to Dolibarr's workflow module because the automation models differ structurally. We deliver a written inventory of every active INNERGY automation with its trigger, conditions, and actions, and a recommended Dolibarr equivalent (community module or scripted workflow) for the customer's admin to rebuild post-migration.

Migration approach

Six steps for a successful INNERGY ERP to Dolibarr ERP data migration

  1. Discovery and INNERGY API audit

    We audit INNERGY's live schema via API to identify all active modules, custom fields, division structures, and data volumes. We extract sample records from Estimates, Jobs, BOMs, Work Orders, Change Orders, Inventory, Customers, Vendors, and open AP/AR to validate field coverage and identify any undocumented custom properties. We request a current INNERGY invoice to establish the customer's active module count and user count for pricing context.

  2. Dolibarr module selection and schema design

    We configure Dolibarr by enabling only the modules relevant to the customer's operations: ThirdParty (Customers and Suppliers), Commercial Proposal, Product and Stock, Project and Task, BOM (if production module is active), Invoice (Customer and Supplier), and Accounting. We create extrafields on each module to match INNERGY custom fields discovered during the API audit. Division-specific cost pools and account structures require manual classification during scoping.

  3. Data cleansing and deduplication

    We run INNERGY data through a cleansing pass: duplicate customer records are merged using name and address fuzzy matching; orphaned inventory items with zero balances are flagged for archiving; change orders with invalid Job references are reconciled against the Job list; and custom field values are validated against any enumerated lists discovered in the schema. Data quality issues are documented in a cleansing report for the customer's review before import.

  4. Sandbox migration and reconciliation

    We run a full migration into a Dolibarr staging environment (a separate instance or database clone) using production-like data volume. The customer's operations lead reconciles record counts (Customers in, Vendors in, Estimates in, Jobs in, BOMs in, Work Orders in, Change Orders in, Inventory in), spot-checks 25-50 random records against the INNERGY source, and signs off the schema and mapping before production migration begins. Any mapping corrections happen here.

  5. Production migration in dependency order

    We run production migration in record-dependency order: ThirdParties (Customers and Vendors) first to establish parent lookups; Inventory Items and Products; Chart of Accounts; Estimates (Proposals); Jobs (Projects) with Change Order Notes attached; BOM structures; Work Orders as Project Tasks; Open AP/AR as invoices in Open status; Attachments linked to the corresponding records. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and automation handoff

    We freeze INNERGY writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dolibarr as the system of record. We deliver the automation inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild INNERGY Workflows or CAD integrations as Dolibarr automations or modules inside the migration scope.

Platform deep dives

Context on both ends of the pair

INNERGY ERP logo

INNERGY ERP

Source

Strengths

  • Purpose-built for ETO woodworking, millwork, and cabinet shops with native support for custom architectural scenarios.
  • Tightly integrated CAD-to-ERP workflow that auto-populates BOMs and estimates from design data.
  • Real-time production visibility through the Bottleneck Report and Throughput Widget features.
  • Cloud-based delivery with a mobile app supporting field and shop-floor access.
  • Dedicated implementation team and structured certification program for onboarding.

Weaknesses

  • No public pricing — sales-led custom quoting creates budget uncertainty and extends evaluation cycles.
  • Significant implementation complexity requiring weeks to months of internal resource commitment before operational value is realized.
  • Reported integration challenges with third-party accounting, scheduling, and equipment systems.
  • Native reporting is described by users as insufficient for detailed analytical requirements, requiring supplemental BI tooling.
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 INNERGY ERP 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

    INNERGY ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your INNERGY 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 shops with fewer than 5,000 Jobs, straightforward BOM structures, and no post-implementation custom fields. Migrations with multi-level BOMs, large change order histories spanning multiple Jobs, or extensive custom field frameworks move to eight to twelve weeks because of schema discovery, BOM decomposition, and linked-table preservation work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from INNERGY 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