ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between INNERGY ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty (Customer/Supplier)
1:1INNERGY 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
Dolibarr ERP
ThirdParty (Supplier)
1:1INNERGY 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
Dolibarr ERP
Proposal/Commercial Proposal
1:1INNERGY 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
Dolibarr ERP
Project
1:1INNERGY 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)
Dolibarr ERP
Product (with BOM structure via module)
lossyINNERGY 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
Dolibarr ERP
Project Task
1:manyINNERGY 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
Dolibarr ERP
Project Note (linked table)
1:1INNERGY 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
Dolibarr ERP
Product + Stock
1:1INNERGY 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
Dolibarr ERP
Account (Accounting module)
1:1INNERGY'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
Dolibarr ERP
Invoice (Supplier Invoice / Customer Invoice)
1:1Outstanding 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
Dolibarr ERP
Document (linked to Project/Product)
1:1INNERGY 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
Dolibarr ERP
Extrafields
lossyINNERGY'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.
| INNERGY ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Customer/Supplier)1:1 | Fully supported | |
| Vendor | ThirdParty (Supplier)1:1 | Fully supported | |
| Estimate | Proposal/Commercial Proposal1:1 | Fully supported | |
| Job | Project1:1 | Fully supported | |
| Bill of Materials (BOM) | Product (with BOM structure via module)lossy | Fully supported | |
| Work Order | Project Task1:many | Fully supported | |
| Change Order | Project Note (linked table)1:1 | Fully supported | |
| Inventory Item | Product + Stock1:1 | Fully supported | |
| Chart of Accounts | Account (Accounting module)1:1 | Mapping required | |
| Open AP/AR | Invoice (Supplier Invoice / Customer Invoice)1:1 | Mapping required | |
| Attachments | Document (linked to Project/Product)1:1 | Mapping required | |
| Custom Fields | Extrafieldslossy | 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.
INNERGY ERP gotchas
INNERGY has no public pricing page
Industry-specific data structures resist generic mappings
Change order history can span multiple Jobs
Custom fields introduced post-implementation may lack schema documentation
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 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.
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.
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.
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.
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.
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
INNERGY ERP
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 INNERGY ERP 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
INNERGY ERP: Not publicly documented.
Data volume sensitivity
INNERGY ERP 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 INNERGY ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave INNERGY ERP
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.