ERP migration
Field-level mapping, validation, and rollback between AltheaSuite and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
AltheaSuite
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between AltheaSuite and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from AltheaSuite to Dolibarr is a migration from a vertical-first proprietary ERP with opaque pricing to an open-source modular ERP with transparent free and cloud tiers. AltheaSuite's core data model centers on Items (with custom fields, serial numbers, lot numbers, and expiry dates), Customers, Vendors, Purchase Orders, Sales Orders, and Work Orders tied to multi-level BOMs. Dolibarr models these as Products/Services, Third Parties (combined Customers and Suppliers), Supplier Orders, Customer Orders, and Bill of Materials with varying manufacturing depth. The most critical pair-specific constraint is that AltheaSuite exposes no public API or self-service export; all data extraction must be coordinated directly with the AltheaSuite team during discovery, and the resulting dump must be validated for schema completeness before mapping begins. We flatten multi-level BOM structures, re-associate serial-to-item and lot-to-item mappings as child records, and load through Dolibarr's CSV import wizard and REST API in dependency order. Workflows, automations, and POS configurations do not migrate; we deliver a written inventory of these for the customer to rebuild in Dolibarr's module framework.
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 AltheaSuite 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.
AltheaSuite
Item
Dolibarr ERP
Product / Service
1:1AltheaSuite Items (Products and Services) map to Dolibarr Products/Services. Standard fields (SKU, name, description, unit price, cost) migrate directly. Custom Item fields (text, number, lookup, date, fractional) are enumerated during schema profiling, typed against Dolibarr's field type equivalents, and created as extra fields on the Product record. We validate each custom field has a value in the dump before importing to avoid null-handling mismatches.
AltheaSuite
Serial Number Record
Dolibarr ERP
Product Serial Number (Stock module)
1:1AltheaSuite serial numbers are assigned records linked to Items. We extract the full serial-to-item mapping as a child table during the export phase, then re-associate each serial record with the correct Dolibarr Product ID at import time. We flag any orphaned serial records (serial with no parent Item) for manual resolution before the import finalizes. Dolibarr's serial number tracking requires the Stocks module to be enabled.
AltheaSuite
Lot and Expiry Record
Dolibarr ERP
Lot / Batch (with expiry tracking)
1:1AltheaSuite lot-controlled items carry lot number and expiry date metadata. We migrate lot assignment records with their parent Items, preserving expiry dates for destinations that support FEFO (First Expired First Out) logic. Dolibarr's base lot tracking is included in the Stocks module; expiry date enforcement requires configuration or the Perishable Stock add-on depending on the Dolibarr version.
AltheaSuite
Customer
Dolibarr ERP
Third Party (Customer type)
1:1AltheaSuite Customer records migrate to Dolibarr Third Parties with the Customer flag enabled. Contact details, addresses, and account-level fields transfer intact. In Dolibarr, customers and suppliers share a single Third Party object with a Type field; we set Type=Customer based on the AltheaSuite source record type. The customer code from AltheaSuite becomes the Dolibarr Ref (reference) field as the dedupe key.
AltheaSuite
Vendor
Dolibarr ERP
Third Party (Supplier type)
1:1AltheaSuite Vendor records migrate to Dolibarr Third Parties with the Supplier flag enabled. Contact info, addresses, and supplier-level fields transfer intact. The vendor-managed inventory flag from AltheaSuite (indicating whether the vendor supplies managed stock) migrates as a boolean property on the Dolibarr Third Party record. The vendor code becomes the Dolibarr Ref field as the dedupe key.
AltheaSuite
Purchase Order
Dolibarr ERP
Supplier Order
1:1AltheaSuite Purchase Orders carry line items, quantities, and costs. We map PO headers and line items to Dolibarr Supplier Order and Supplier Order Line. Multi-currency or landed-cost fields require explicit value-mapping against Dolibarr's currency fields; we flag any landed-cost line items that cannot map cleanly for manual handling. Purchase Order status (draft, sent, received) maps to Dolibarr Draft, Validated, Approved states.
AltheaSuite
Sales Order
Dolibarr ERP
Customer Order
1:1AltheaSuite Sales Orders include header data, line items, fulfillment status, and delivery assignments. We preserve order-to-delivery linkage in the mapping notes but note that fulfillment state (partial vs. complete) must be explicitly set in Dolibarr's order status workflow. Delivery addresses from AltheaSuite migrate to Dolibarr's contact address or delivery address fields on the Customer Order header.
AltheaSuite
Work Order (Manufacturing)
Dolibarr ERP
Bill of Materials + Project / Task
1:manyAltheaSuite Work Orders are tied to multi-level BOMs and track production status with step-level labor and machine time. We flatten BOM hierarchies during migration mapping: each level of the AltheaSuite BOM becomes a separate BOM definition in Dolibarr, and Work Order header data migrates to Dolibarr Project records with tasks representing production steps. Step-level labor and machine time entries migrate as child task records if the destination supports task time tracking; otherwise they are flagged for manual entry post-migration.
AltheaSuite
Multi-level BOM
Dolibarr ERP
Bill of Materials (nested structure)
lossyBill of Materials structures in AltheaSuite support nested sub-assemblies. We flatten BOM hierarchies during migration mapping and reconstruct the correct parent-child relationships in Dolibarr's BOM module. Each AltheaSuite BOM level maps to a Dolibarr BOM with line items referencing sub-assembly Products. The BOM revision and有效期 fields migrate as custom properties on the Dolibarr BOM.
AltheaSuite
Custom Item Fields
Dolibarr ERP
Product Extra Fields
lossyAltheaSuite supports user-defined custom fields on Items (Text, Number, Lookup Value, Date Time, Fractional Number). We discover these during schema profiling by requesting a full list of custom Item field definitions from the customer and verifying them against the live system during the profile walkthrough. Each field type converts explicitly: AltheaSuite Lookup Value becomes a Dolibarr select-type extra field; Number becomes an integer or decimal extra field; Fractional Number becomes a decimal extra field. Field types are converted explicitly to avoid type mismatches at import.
AltheaSuite
Reorder Level
Dolibarr ERP
Stock Replenishment / Alert Threshold
1:1AltheaSuite reorder levels per Item migrate to Dolibarr's stock replenishment alert thresholds on the Product record. We map reorder point quantities to Dolibarr's stock alert level, enabling the reorder workflow in Dolibarr's Stocks module after migration.
AltheaSuite
Category / Label
Dolibarr ERP
Product Category
1:1AltheaSuite Item categories and labels migrate to Dolibarr Product Categories. We preserve the category hierarchy as a flat or nested category structure depending on Dolibarr's category module configuration. Categories with no assigned Items are flagged for the customer to handle post-migration.
| AltheaSuite | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Item | Product / Service1:1 | Fully supported | |
| Serial Number Record | Product Serial Number (Stock module)1:1 | Fully supported | |
| Lot and Expiry Record | Lot / Batch (with expiry tracking)1:1 | Fully supported | |
| Customer | Third Party (Customer type)1:1 | Fully supported | |
| Vendor | Third Party (Supplier type)1:1 | Fully supported | |
| Purchase Order | Supplier Order1:1 | Fully supported | |
| Sales Order | Customer Order1:1 | Fully supported | |
| Work Order (Manufacturing) | Bill of Materials + Project / Task1:many | Fully supported | |
| Multi-level BOM | Bill of Materials (nested structure)lossy | Fully supported | |
| Custom Item Fields | Product Extra Fieldslossy | Fully supported | |
| Reorder Level | Stock Replenishment / Alert Threshold1:1 | Fully supported | |
| Category / Label | Product Category1: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.
AltheaSuite gotchas
Pricing is not publicly available
No public API or documented export endpoints
Custom fields on Items must be explicitly enumerated
Serialized and lot-controlled inventory requires traceability reconciliation
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 vendor-mediated export coordination
We audit the AltheaSuite instance for Items (standard and with custom fields), Customers, Vendors, Purchase Orders, Sales Orders, Work Orders, BOM structures, and serial/lot records. Because AltheaSuite has no public API, we coordinate directly with the AltheaSuite team to request a full structured data dump in CSV or JSON format. We validate the dump's schema completeness during discovery: checking that every custom field is present, that parent-child relationships are intact (Items with serials, Items with lots, Work Orders with BOMs), and that no export truncation occurred. Any schema gaps are raised with AltheaSuite before mapping begins.
Dolibarr instance provisioning and module activation
We provision the destination Dolibarr instance (self-hosted or cloud) and activate only the modules required for the migration scope: Third Parties, Products/Services, Stocks (with serial and lot tracking), Supplier Orders, Customer Orders, and BOMs. We configure currency, tax, country, and language settings to match the AltheaSuite source data. We create the product categories, warehouse locations, and unit-of-measure definitions before any product data loads.
Custom field enumeration and schema mapping
We enumerate every custom Item field from AltheaSuite during the profile walkthrough, verify the list against the live system, and create equivalent extra fields in Dolibarr's Product module. Field type conversion is explicit: text fields to varchar extra fields, numeric fields to decimal extra fields, lookup values to select extra fields. We document the full mapping matrix in a CSV and validate it with the customer before any data is transformed.
Sandbox migration and reconciliation
We run a full migration into a Dolibarr test instance using production-like data volume. The customer reconciles record counts (Items in, Third Parties in, Orders in, BOMs in), spot-checks 25-50 random records against the AltheaSuite source, and validates that serial and lot traceability is intact. Any mapping corrections are made in this phase. BOM flattening and serial/lot re-association are validated specifically for manufacturing and inventory-heavy accounts.
Production migration in dependency order
We run production migration in record-dependency order: Third Parties (Customers then Suppliers), Products (with extra fields), BOM definitions, serial number assignments, lot assignments, Supplier Orders, Customer Orders, and Work Orders (as Projects with tasks). Each phase emits a row-count reconciliation report before the next phase begins. AltheaSuite writes are frozen during cutover and a final delta migration captures any records modified during the migration window.
Cutover, validation, and automation rebuild handoff
We enable Dolibarr as the system of record after final reconciliation. We deliver the automation and POS configuration inventory document to the customer, detailing every AltheaSuite workflow, automation, and POS setting that requires manual rebuild in Dolibarr. We support a one-week hypercare window where we resolve any data issues raised during the first production week. We do not rebuild AltheaSuite workflows in Dolibarr's module framework; that work is handled by the customer's admin or a Dolibarr integration partner.
Platform deep dives
AltheaSuite
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 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 AltheaSuite and Dolibarr ERP.
Object compatibility
2 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
AltheaSuite: Not publicly documented.
Data volume sensitivity
AltheaSuite 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 AltheaSuite to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your AltheaSuite 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 AltheaSuite
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.