ERP migration
Field-level mapping, validation, and rollback between Total ETO and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Total ETO
Source
Dolibarr ERP
Destination
Compatibility
12 of 13
objects map 1:1 between Total ETO and Dolibarr ERP.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from Total ETO to Dolibarr is a data-extraction challenge before it is a data-loading challenge. Total ETO publishes no public API, so every migration begins with a SQL Server database export or structured CSV extracts from the Windows desktop application. On the destination side, Dolibarr is a modular open-source ERP with a web interface that covers third-parties, products, projects, purchasing, and stock — but its manufacturing module lacks the versioned BOM hierarchy that Total ETO engineers rely on during the ETO build phase. We preserve each BOM revision as a separate Dolibarr product with a version tag, import Parts as Dolibarr products with multi-level BOM lines, and map Work Orders to Dolibarr Project tasks with routing data. Open POs migrate as supplier Purchase Orders only after the Part master is established to satisfy foreign-key constraints. Quality records (NCRs, Inspections) and CAD-linked documents have no native Dolibarr equivalent — we deliver these as structured inventory for manual reconstruction. Workflows, automations, and CAD integrations do not migrate; we document them for the customer's admin to address separately.
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 Total ETO 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.
Total ETO
Project
Dolibarr ERP
Project
1:1Total ETO Projects (covering the ETO lifecycle from quote through delivery) map directly to Dolibarr Projects. Each project carries status stages, owner assignment, and dates that transfer as Project fields. We preserve the project-level job costing data as Project task-level cost entries at the destination. If Total ETO uses custom project stages beyond the standard pipeline, we configure Dolibarr Project status values during initial setup.
Total ETO
Bill of Materials (versioned)
Dolibarr ERP
Product (with BOM) + Product lot/batch
1:manyTotal ETO BOMs are multi-level and versioned — each engineering revision creates a new BOM version rather than overwriting the prior one. Dolibarr does not have native BOM versioning, so we import each BOM revision as a separate Dolibarr Product with the version identifier embedded in the product reference (for example, BOM-ASSY-001-REV-C). Multi-level sub-assemblies map to Dolibarr BOM lines under the parent product. This preserves the revision history but requires the customer's admin to select the correct BOM version when creating production orders.
Total ETO
Part
Dolibarr ERP
Product
1:1Total ETO Part master records (description, unit of measure, cost, supplier link, and usage history) map to Dolibarr Products. The part number becomes the product reference; description and unit of measure transfer directly. Supplier link migrates as a Dolibarr Supplier Pre-Qualified List entry tied to the product. Usage history across projects transfers as a product warehouse movement log rather than a standalone history object.
Total ETO
Customer
Dolibarr ERP
Third-Party (Customer)
1:1Total ETO Customer master records (contact details, address, account balance as of migration date) map to Dolibarr Third-Party records with the Customer category flag. Open Accounts Receivable balances transfer as Dolibarr customer account entries for reconciliation. If Total ETO maintains credit limits, these map to Dolibarr's third-party credit limit fields.
Total ETO
Vendor
Dolibarr ERP
Third-Party (Supplier)
1:1Total ETO Vendor master records map to Dolibarr Third-Party records with the Supplier category flag. Purchasing terms (payment conditions, lead times) transfer to Dolibarr's supplier data fields. Active RFQs and POs migrate separately after the vendor and part masters are established at the destination.
Total ETO
Purchase Order (open)
Dolibarr ERP
Supplier Order
1:1Open Purchase Orders in Total ETO reference live part numbers and vendor commitments. We sequence PO migration after Part master and Vendor records are established at Dolibarr to satisfy foreign-key requirements. Each PO line item maps to a Dolibarr Supplier Order line referencing the mapped Product. POs with partial receipt status carry remaining quantity as the open line item value. Any orphaned PO lines (references to parts not yet migrated) are flagged and held for manual resolution before the next migration phase.
Total ETO
Work Order
Dolibarr ERP
Project Task
1:1Total ETO Work Orders link to Projects and BOMs, tracking manufacturing operations by shop-floor routing. We map each work order to a Dolibarr Project Task with the routing operation sequence preserved as task descriptions and planned durations. Operation-level labor assignments link to the mapped Employee record. Work order status (released, in-progress, completed) maps to Dolibarr task status values.
Total ETO
Non-Conformance Record
Dolibarr ERP
No native equivalent
1:1Total ETO NCRs reference specific parts, inspections, and quality issues logged from the shop floor, engineering, or procurement. Dolibarr has no native NCR or quality management module in its core. We map NCRs as Dolibarr Project Tasks (categorized as Quality) linked to the relevant Product and the originating Project. Inspection results attach as task notes or file uploads. The customer's admin reviews the inventory and may install a community Dolibarr quality module as a separate post-migration step.
Total ETO
Inspection
Dolibarr ERP
Project Task (Quality)
1:1Inspections record quality checks against parts and link to the inspector. We import inspection results as Dolibarr Project Task entries categorized as Inspection, linked to the relevant Product and the originating Project or Work Order. Inspector identity transfers as a task assignee. NCR linkage migrates as a related task reference. The limitation is that Dolibarr does not enforce inspection workflows natively; this is documented for the customer's admin to address through process or community module.
Total ETO
Inventory
Dolibarr ERP
Stock
1:1On-hand quantities tracked by location in Total ETO map to Dolibarr Stock Warehouse entries. Project-reserved quantities transfer as warehouse reservations tied to the relevant Project. We flag any negative quantities or reserved quantities that conflict with Dolibarr's warehouse logic before import. Multi-location setups require warehouse configuration in Dolibarr before inventory data loads.
Total ETO
Employee
Dolibarr ERP
User
1:1Total ETO Employee records (time-entry data, labor class, department) map to Dolibarr User records with the employee flag. Time-entry logs linked to projects and work orders migrate as Dolibarr Project Task time-spent entries assigned to the mapped User. Department data transfers as a Dolibarr expense category or project cost center tag.
Total ETO
Time Entry
Dolibarr ERP
Project Task (time spent)
1:1Total ETO time entries are project-based with clock-in/clock-out data and assignment to work orders. We import time logs as Dolibarr Project Task time-spent entries, linking each entry to the mapped Project and Work Order task. Duration and date transfer directly. Geolocation data (where captured) is noted as a custom task description field since Dolibarr does not natively store geolocation on time entries.
Total ETO
Document
Dolibarr ERP
No native equivalent
1:1Total ETO stores documents linked to projects, parts, and quality records. Dolibarr's document management is file-attachment based rather than a structured document record with metadata. We extract document references and file paths from Total ETO, then attach the actual files to the corresponding Dolibarr records (Project, Product, or Task) as file uploads. The customer's admin configures Dolibarr's document storage directory before the file migration phase. Native CAD file integration does not transfer.
| Total ETO | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Project | Project1:1 | Fully supported | |
| Bill of Materials (versioned) | Product (with BOM) + Product lot/batch1:many | Fully supported | |
| Part | Product1:1 | Fully supported | |
| Customer | Third-Party (Customer)1:1 | Fully supported | |
| Vendor | Third-Party (Supplier)1:1 | Fully supported | |
| Purchase Order (open) | Supplier Order1:1 | Fully supported | |
| Work Order | Project Task1:1 | Fully supported | |
| Non-Conformance Record | No native equivalent1:1 | Fully supported | |
| Inspection | Project Task (Quality)1:1 | Fully supported | |
| Inventory | Stock1:1 | Fully supported | |
| Employee | User1:1 | Fully supported | |
| Time Entry | Project Task (time spent)1:1 | Fully supported | |
| Document | No native equivalent1: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.
Total ETO gotchas
No public API means migrations are database-centric
Dynamic BOM versioning is not a flat list
Open POs and RFQs require pre-migration cleanup
Accounting data may live outside Total ETO
Permission over-granularity creates data-integrity risk
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
Scoping and database access assessment
We audit the Total ETO environment: hosting model (cloud or on-premise SQL Server), approximate record counts across Projects, BOMs, Parts, Customers, Vendors, POs, Work Orders, NCRs, Inspections, Inventory, Employees, and Documents. We assess the database access method — on-premise customers provide SQL Server backup files directly; cloud customers require a vendor-assisted database export that we coordinate with Total ETO support. We also scope the Dolibarr installation: hosted or self-hosted, PHP version, MySQL/MariaDB version, and which core modules (Third Parties, Products, Projects, Purchasing, Stock, HR) are enabled. The scoping output is a written migration scope document with record counts, a database extraction plan, and a Dolibarr module activation checklist.
Source data extraction
We extract Total ETO data using SQL Server queries (on-premise backups) or coordinated database exports (cloud hosting). The extraction is sequenced by dependency order: reference data first (Customers, Vendors, Parts), then transactional data (Projects, BOMs, BOM revisions, Work Orders, POs), then operational records (NCRs, Inspections, Inventory, Employees, Time Entries), then document references. Each extract produces a structured CSV or JSON file with header rows matching the source schema. We perform a row-count reconciliation against Total ETO's own reports before any transformation begins. Any data anomalies (duplicate part numbers, orphaned BOM lines, missing vendor references) are flagged in a pre-migration data-quality report.
Dolibarr schema setup and module configuration
We configure the destination Dolibarr installation before any data loads. This includes activating and configuring the relevant modules (Third Parties, Products, Commercial, Projects, Purchasing, Stock, HR), setting up warehouse locations matching Total ETO's inventory sites, configuring product categorization matching Total ETO's part type structure, and establishing the Chart of Accounts structure (whether using Dolibarr's built-in double-entry accounting or mapping to an existing external accounting system). We also create the Dolibarr user accounts mapped from Total ETO employee records, assigning roles based on the source permission audit. BOM versioning is handled through a naming convention since Dolibarr does not support native versioning.
Reference data migration and reconciliation
We load reference data first — Third Parties (Customers and Vendors), Products (Parts and BOM revisions), and Employees (Users). Each phase runs against the live or staging Dolibarr instance and emits a reconciliation report comparing source record count to destination record count. Discrepancies are investigated and corrected before the next phase begins. Part master migration includes the supplier pre-qualification link, unit of measure conversion, and cost data. BOM revisions are inserted as separate Products with version tags. Employee records are matched by email or employee number to existing or newly created Dolibarr users.
Transactional data migration
We migrate Projects (with status, owner, dates, and project-level costing), Work Orders (mapped to Project Tasks with routing sequence), open Purchase Orders and RFQs (after Part and Vendor masters are confirmed), and Inventory (warehouse quantities with project reservations). Each object type is loaded in dependency order with foreign-key resolution. Open POs are flagged if any line references a part not yet in the destination; these orphaned lines go to the reconciliation queue for the customer's purchasing team to resolve. NCRs and Inspections are migrated as Project Tasks with quality categorization and file attachments.
Document and file migration
We extract Total ETO document references and file paths, then attach the corresponding files to the relevant Dolibarr records (Project, Product, or Task) using Dolibarr's file upload API or direct file system placement in the documents directory. CAD-linked files are noted as attachments even though Dolibarr has no native CAD viewer. The customer's admin reviews the document mapping inventory to confirm completeness. CAD integration itself cannot migrate — the SolidWorks and Autodesk Inventor add-in connections require reconstruction at the destination if required.
Cutover, final reconciliation, and handoff
We freeze Total ETO writes during the cutover window, run a final delta migration of any records modified during the migration process, then confirm Dolibarr as the system of record. We deliver a final reconciliation report comparing source and destination record counts across all object types, plus a written inventory of BOM version naming conventions, quality record mappings, and open PO line reconciliation items. We do not rebuild Total ETO workflows, CAD integrations, QuickBooks or Sage synchronization, or automations inside Dolibarr — those are documented separately for the customer's admin team to address post-migration.
Platform deep dives
Total ETO
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 Total ETO 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
Total ETO: Not publicly documented.
Data volume sensitivity
Total ETO 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 Total ETO to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Total ETO 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 Total ETO
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.