ERP migration

Migrate from AltheaSuite to Dolibarr ERP

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

AltheaSuite logo

AltheaSuite

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

objects map 1:1 between AltheaSuite and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

AltheaSuite logo

AltheaSuite

What's pushing teams away

  • Prospective customers and app reviewers cite opaque pricing as a primary friction point — AltheaSuite requires booking a demo to get any pricing information, which creates a barrier for self-service evaluation.
  • The Shopify app reviewer notes that after installing the app, they discovered they cannot create an account independently and must go through a sales-driven demo process first.
  • Customers requiring enterprise-scale reporting, multi-entity consolidation, or complex multi-currency accounting often find AltheaSuite's analytics insufficient compared to NetSuite or Odoo.

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

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

maps to

Dolibarr ERP

Product / Service

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Product Serial Number (Stock module)

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Lot / Batch (with expiry tracking)

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Third Party (Customer type)

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Third Party (Supplier type)

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Customer Order

1:1
Fully supported

AltheaSuite 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)

maps to

Dolibarr ERP

Bill of Materials + Project / Task

1:many
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Bill of Materials (nested structure)

lossy
Fully supported

Bill 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

maps to

Dolibarr ERP

Product Extra Fields

lossy
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Stock Replenishment / Alert Threshold

1:1
Fully supported

AltheaSuite 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

maps to

Dolibarr ERP

Product Category

1:1
Fully supported

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

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.

AltheaSuite logo

AltheaSuite gotchas

High

Pricing is not publicly available

High

No public API or documented export endpoints

Medium

Custom fields on Items must be explicitly enumerated

Medium

Serialized and lot-controlled inventory requires traceability reconciliation

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

  • AltheaSuite has no public API — all export is vendor-mediated

    Research across technical queries found no publicly documented REST API, GraphQL endpoint, or bulk export endpoint for AltheaSuite. All export pathways are vendor-mediated, requiring direct coordination with the AltheaSuite team to request a data dump. We handle this by requesting the full dump during the discovery phase and validating the dump's schema completeness before mapping begins. If no structured export is available, migration scope must include manual extraction steps with vendor cooperation. This adds a coordination dependency that can extend timelines if vendor response is delayed.

  • Custom Item fields must be explicitly enumerated from AltheaSuite

    AltheaSuite supports user-defined custom fields on Items, but these are not discoverable via any API. During migration scoping, we request a full list of custom Item field definitions from the customer, verify them against the live system during the profile walkthrough, and map each to an equivalent extra field in Dolibarr. Field types (dropdown, text, numeric) must be converted explicitly to avoid type mismatches at import. If custom fields are not enumerated before import, they appear as blank columns in Dolibarr with no source data.

  • Multi-level BOM flattening changes the Bill of Materials structure

    AltheaSuite supports nested sub-assemblies in multi-level BOMs. Dolibarr's BOM module supports nested structures but the import requires flattening and explicit parent-child relationship resolution. We extract the full BOM tree, map each level to a separate Dolibarr BOM definition, and reconstruct the hierarchy during import. Work Order step-level labor and machine time entries require either task time tracking configuration in Dolibarr or manual entry post-migration. This transformation step adds scope that a flat BOM migration does not.

  • Serial and lot traceability requires child-table re-association

    AltheaSuite tracks serial numbers and lot numbers as separate assignment records linked to Items. When migrating into Dolibarr, which manages serials as part of the Stock module, we extract the full serial-to-item and lot-to-item mapping as child tables, then re-associate each record with the correct Product ID at the destination. We flag any orphaned serial or lot records that have no parent Item and present them for manual resolution before finalizing the import. This is a non-trivial reconciliation step for inventory-heavy manufacturing customers.

  • Dolibarr does not migrate workflows or POS configurations from AltheaSuite

    Dolibarr's workflow engine and AltheaSuite's automation model are architecturally distinct. We do not migrate AltheaSuite workflows, automations, POS screen layouts, or custom document templates as code. POS-specific settings (register configurations, payment gateway mappings, receipt formats) are not portable. We deliver a written inventory of AltheaSuite automations and POS settings that require manual rebuild in Dolibarr's module framework or by a Dolibarr integration partner.

Migration approach

Six steps for a successful AltheaSuite to Dolibarr ERP data migration

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

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

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

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

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

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

Context on both ends of the pair

AltheaSuite logo

AltheaSuite

Source

Strengths

  • Deep inventory tracking with serial numbers, lot control, expiry dates, and reorder level automation.
  • Modular architecture allowing SMBs to adopt only the modules they need and expand over time.
  • Integrated POS and inventory in a single platform for retail-facing businesses.
  • Multi-level BOM support for discrete manufacturing and assembly operations.
  • Cloud-based with mobile access on iOS and Android for field and floor teams.

Weaknesses

  • Pricing is not publicly disclosed — customers must contact sales or book a demo to receive a quote, limiting self-service evaluation.
  • No public API documentation or developer portal found in research, making programmatic data export uncertain without direct vendor engagement.
  • No self-service signup available — even the Shopify app requires linking to an existing AltheaSuite account after a demo booking.
  • Limited independent review volume (9 reviews across major platforms) makes it difficult to assess long-term reliability and support quality at scale.
  • Customization is praised but the effort and cost of that customization is not transparent, leading some customers to feel locked into the vendor for ongoing changes.
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. 2 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 AltheaSuite and Dolibarr ERP.

  • Object compatibility

    B

    2 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

    AltheaSuite: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 5,000 Items, 1,000 Customers, and 500 Orders with straightforward BOM structures. Migrations with multi-level BOM hierarchies, large serialized and lot-controlled inventory, or extended vendor-mediated export coordination move to seven to ten weeks. The absence of a public API on the source side is the primary timeline variable: if AltheaSuite delivers a clean structured dump quickly, migration proceeds at standard pace; if export requires multiple vendor engagements, timelines extend.

Adjacent paths

Related migrations to explore

Ready when you are

Move from AltheaSuite.
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