ERP migration

Migrate from Actindo Core1 to Dolibarr ERP

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

Actindo Core1 logo

Actindo Core1

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

93%

13 of 14

objects map 1:1 between Actindo Core1 and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Actindo Core1 to Dolibarr is a structural migration from a MACH-certified headless commerce ERP to a modular open-source ERP-CRM. Actindo Core1 separates Material master data from Article channel content managed in the PIM module, with both fed through the DataHub ETL layer that normalizes data from Shopware, Shopify, Amazon, and POS systems into a unified order and inventory model. Dolibarr uses a single product model for both goods and services with optional PIM-style modules activated per installation, meaning we must reconstruct the Material-Article parent-child relationship during transformation. Actindo's workflow engine encodes business logic as low-code visual flows that are not natively exportable, so we capture rule screenshots and build a written rule matrix for Dolibarr rebuild. We do not migrate custom workflows, automations, DataHub ETL configurations, or POS register reconciliations as code; these require separate administrative rebuild in Dolibarr. The migration sequence begins with master data (Third Parties, Products, Warehouses), proceeds to transactional records (Orders, Invoices, Purchase Orders), and concludes with engagement and note history.

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

Actindo Core1 logo

Actindo Core1

What's pushing teams away

  • Implementation complexity requires specialized consultants to configure the platform, adding significant time and cost before the system delivers value.
  • Custom workflows and ETL mappings built during implementation become technical debt when the original consultant leaves, limiting in-house control.
  • Steep learning curve for business users unfamiliar with ERP concepts, leading to underutilization of features that were sold during the sales process.
  • Pricing at the Basic tier at $3,500/month scales quickly with order volume, making it costly for growing businesses not yet at enterprise scale.
  • Limited public documentation and English-language support outside the core help center creates knowledge gaps for non-German-speaking teams.

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

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

Actindo Core1

Customer

maps to

Dolibarr ERP

ThirdParty

1:1
Fully supported

Actindo Customer records with address, contact, and segment data map directly to Dolibarr ThirdParty (llx_societe) records. We preserve segment tags as Dolibarr category associations (llx_categories) and contact roles as Dolibarr contact functions. Customer-specific pricing tiers from Actindo's DataHub export migrate to Dolibarr extrafields on ThirdParty. Any Actindo Customer record that is a vendor as well as a buyer creates two ThirdParty records in Dolibarr: one as Customer type and one as Supplier type.

Actindo Core1

Material

maps to

Dolibarr ERP

Product (goods)

1:1
Fully supported

Actindo Material records with SKU, pricing, stock levels, and attribute data map to Dolibarr Product records of type Product (good). The Material SKU becomes the Dolibarr ref field and serves as the dedupe key during import. Channel-specific pricing from Actindo's DataHub export migrates to Dolibarr extrafields or separate price lists linked via llx_product_price. Warehouse stock levels map to llx_product_stock entries with the warehouse reference resolved from the Warehouse object mapping.

Actindo Core1

Article

maps to

Dolibarr ERP

Product extrafields (channel content)

1:many
Fully supported

Actindo Article records extend Materials with channel-specific descriptions, media, and PIM content from the Omnichannel module. We export Article content separately from Material master data and tag each Article record with its parent Material SKU during extraction. In Dolibarr, we attach Article content as extrafields on the corresponding Product record or as linked document records in Dolibarr's document management area. The Article-Product relationship is reconstructed using the SKU foreign key, and the customer determines whether channel-specific content is consolidated into a single Product record or split across Dolibarr product variants.

Actindo Core1

Warehouse

maps to

Dolibarr ERP

Warehouse

1:1
Fully supported

Actindo Warehouse entities with bin-level stock locations and multi-warehouse assignment rules map to Dolibarr Warehouse records (llx_entrepot). We preserve warehouse-level stock totals directly. Bin-level structure from Actindo is not natively supported in Dolibarr's core warehouse module and requires a Dolibarr third-party stock-location addon or custom extrafield configuration; the customer chooses the approach during scoping, and we document bin-to-location mapping in the migration notes.

Actindo Core1

Order

maps to

Dolibarr ERP

Order (CustomerOrder)

1:1
Fully supported

Actindo Orders sourced from DataHub with line items, fulfillment status, and channel attribution map to Dolibarr Commande records. Each Actindo order source channel (webshop, marketplace, POS, B2B) becomes a Dolibarr source type. We preserve order total, tax amounts, and payment status from Actindo. Order-level discounts and shipping fees from DataHub exports become Dolibarr order line adjustments. The Actindo order number becomes the Dolibarr ref_customer field for traceability.

Actindo Core1

Purchase Order

maps to

Dolibarr ERP

SupplierOrder

1:1
Fully supported

Actindo Purchase Orders linked to Materials and inbound receipts map to Dolibarr CommandeFournisseur records. Vendor-specific reference numbers from Actindo become Dolibarr ref_supplier fields. Line item mapping uses the Material SKU to resolve Product references in Dolibarr. Inbound receipt quantities from Actindo reconcile against Dolibarr stock movements (llx_stock_mouvement) after the PO import completes.

Actindo Core1

Invoice (customer)

maps to

Dolibarr ERP

Invoice

1:1
Fully supported

Actindo Invoice records linked to Orders with tax codes and payment status map to Dolibarr Facture records. We extract the full invoice line detail including tax rates, discounts, and payment terms. Invoice PDFs from Actindo are imported as Dolibarr document attachments. Actindo payment status (paid, unpaid, partial) migrates to Dolibarr Facture status fields, and historical payment records migrate as llx_paiement_facture entries linked to the corresponding bank movement.

Actindo Core1

Invoice (vendor)

maps to

Dolibarr ERP

SupplierInvoice

1:1
Fully supported

Actindo vendor invoices linked to Purchase Orders map to Dolibarr FactureFournisseur records. Tax codes and vendor-specific reference numbers transfer directly. Vendor payment terms migrate to Dolibarr payment term configuration. Any Actindo invoice records without a corresponding Purchase Order are imported as standalone supplier invoices and flagged for reconciliation during cutover review.

Actindo Core1

Vendor

maps to

Dolibarr ERP

ThirdParty (Supplier type)

1:1
Fully supported

Actindo Vendor master records with supplier data, payment terms, and lead times map to Dolibarr ThirdParty records of type Supplier. We preserve contact information, default payment terms (from Actindo's vendor purchasing defaults), and lead time data as Dolibarr extrafields. Vendor-specific PO history links to the corresponding SupplierOrder records via the ThirdParty reference.

Actindo Core1

POS Transaction

maps to

Dolibarr ERP

Order (CustomerOrder) with store attribute

1:1
Fully supported

Actindo POS transaction records from Venduo POS sync as Orders with a store-location attribute. We extract POS transactions as Dolibarr Commande records with the store warehouse and location tagged in extrafields. Register reconciliation data from Actindo (opening cash, cash drops, closing cash) migrates as Dolibarr bank statement entries or bank reconciliation records rather than as native POS register data, since Dolibarr's core POS module handles reconciliations separately.

Actindo Core1

DataHub ETL configuration

maps to

Dolibarr ERP

Dolibarr module configuration + documentation

1:1
Fully supported

Actindo DataHub ETL mappings (CSV, XML, EDIFACT transforms between source channels and Actindo) do not migrate as functional code to Dolibarr. We document each DataHub mapping in a written inventory: source format, target schema in Actindo, field transforms, and scheduling. This document serves as the reference for the customer's admin to rebuild equivalent data imports using Dolibarr's native import tool or a third-party connector. Channel-specific POS and marketplace integrations (Shopware, Shopify, Amazon) each get a separate ETL summary page.

Actindo Core1

Workflow Engine definitions

maps to

Dolibarr ERP

Written rule matrix + documentation

1:1
Fully supported

Actindo Workflow Engine definitions encoding order routing rules, fulfillment automation, and process orchestration are not natively exportable in a standard schema. We capture workflow screenshots, rule descriptions, and condition logic during extraction and build a written rule-mapping matrix. Each Actindo workflow maps to a Dolibarr module recommendation (e.g., using Dolibarr's Trigger system, third-party workflow addons, or manual process documentation for the admin team to implement post-migration). Workflow rebuild is outside standard migration scope.

Actindo Core1

Product category

maps to

Dolibarr ERP

Category

1:1
Fully supported

Actindo Materials and Articles assigned to category hierarchies map to Dolibarr llx_categories with type=product. We preserve the full category tree structure including parent-child relationships. Multi-category assignments on a single Material or Article become multiple CategoryAssignment records in Dolibarr.

Actindo Core1

Bank movement / payment

maps to

Dolibarr ERP

Bank transaction + payment

1:1
Fully supported

Actindo payment records linked to invoices and orders map to Dolibarr llx_paiement records connected to llx_bank entries. Payment method (credit card, bank transfer, cash) migrates as the Dolibarr payment type. Each payment record links to the corresponding Facture or CommandeFournisseur for reconciliation.

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.

Actindo Core1 logo

Actindo Core1 gotchas

High

Legacy ERP coupling creates dual-direction migration complexity

Medium

Custom workflow configurations require manual rule translation

Medium

Article PIM data and Material product data are separate entities

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

  • Material and Article split requires manual reconstruction in Dolibarr

    Actindo separates Material master data (SKU, pricing, stock) from Article channel content managed in the PIM module, and these two entities have a parent-child relationship that is exported independently from the DataHub. Dolibarr does not have a native equivalent two-tier product structure. We preserve the relationship by tagging each Article record with its parent Material SKU during extraction, but in Dolibarr the Article content must be manually associated with the corresponding Product record either via extrafields or as document attachments. Skipping this step results in Products with correct pricing and stock but no channel descriptions or media.

  • Actindo often runs alongside a legacy ERP creating dual-direction data flows

    Actindo Core1 is architected to sit alongside existing ERP systems rather than replace them, meaning source data often exists in two places simultaneously — the legacy ERP and Actindo — and business rules reference both systems. Migration plans must account for which records are Actindo-primary versus ERP-primary during discovery. If the legacy ERP continues to run during cutover, we coordinate a delta synchronization window to prevent inventory or order state from splitting across systems. We flag this in the discovery phase and recommend a coordinated freeze window between both systems.

  • Dolibarr v20 service modification integrity constraint requires field-level attention

    A reported bug in Dolibarr v20 (GitHub issue #34052) causes integrity constraint errors on the fk_product_finished field between llx_product and llx_c_product_nature tables when modifying existing service records migrated from v19. We validate Dolibarr version before migration and recommend a stable v19 LTS or patched v20 environment. If migrating to v20, we flag service-type Products as requiring post-migration verification of any edit operations before the cutover is considered complete.

  • DataHub ETL mappings do not migrate and must be rebuilt

    Actindo DataHub ETL configurations (CSV, XML, EDIFACT transforms for Shopware, Shopify, Amazon, commercetools, and Venduo POS) are not exportable in a standard schema. We deliver a written inventory of every active DataHub mapping with source format, field transforms, target schema, and scheduling. The customer's admin or a Dolibarr implementation specialist uses this document to rebuild the integrations via Dolibarr's native import tool, REST API, or a third-party connector such as the CS-Cart Dolibarr Connector or a custom Dolibarr module. Channel synchronization resumes only after the replacement integrations are validated.

  • Actindo API rate limits and authentication are not publicly documented

    Actindo Core1 does not publicly document API rate limits, authentication token lifetimes, or per-endpoint throttling behavior. We plan extraction passes conservatively, using retry logic with exponential backoff and batch sizes tuned to observed responses rather than documented thresholds. If the customer has an Actindo consultant relationship, we request the API documentation as part of discovery. Without documented limits, we proceed with throttled extraction that adds one to three days to the data extraction phase compared to a platform with published rate limits.

Migration approach

Six steps for a successful Actindo Core1 to Dolibarr ERP data migration

  1. Discovery and DataHub audit

    We audit the source Actindo Core1 environment through the DataHub layer and REST API. We identify all active modules (Order Management, Omnichannel, PIM, Warehousing, Venduo POS, Accounting integration), the volume of Materials, Articles, Orders, Invoices, Purchase Orders, Warehouses, and Vendors, the count of active Workflow Engine definitions, the DataHub ETL mapping inventory, and any records that are Actindo-primary versus legacy ERP-primary. We also identify the Dolibarr version target (v19 LTS or v20 with post-migration service-modification verification) and which Dolibarr modules need activation. The discovery output is a written migration scope with record counts, object dependency tree, and a Dolibarr module activation checklist.

  2. Material-Article relationship design and Dolibarr schema preparation

    We design the Dolibarr target schema before any data extraction. This includes activating the required Dolibarr modules (Products, Stock, ThirdParty, Customers, Suppliers, Orders, Invoices, Supplier Orders, Projects), creating extrafields for Actindo-specific attributes (channel source, Actindo order ID, original Material SKU for Article linkage), and defining the category hierarchy. We create the warehouse structure matching Actindo's warehouse and bin assignments, or document the bin-to-location reduction plan if the customer opts not to use a third-party stock-location addon.

  3. DataHub extraction in dependency order

    We extract Actindo data in dependency order through the DataHub layer. The sequence is: Third Parties (Customers and Vendors), Products (Materials first, then Articles with SKU tags), Warehouses, Orders, Purchase Orders, Invoices, and POS transactions. Each extraction pass produces a CSV or JSON file validated against the Actindo source record count. For the Article-PIM content, we run a separate extraction pass and join it to Material records using the SKU foreign key during the transformation phase. DataHub ETL mapping definitions are screenshotted and documented rather than extracted as code.

  4. Transformation and Material-Article reconstruction

    We transform the extracted data to match Dolibarr's schema. The Material-Article split is resolved by tagging Article content records with the parent Material SKU, then during Dolibarr import we either merge Article attributes into Product extrafields (single-channel consolidation) or attach Article content as Dolibarr documents linked to the Product record (multi-channel separation). Order channel source tags from Actindo become Dolibarr order source types. Tax codes and payment terms are normalized to Dolibarr dictionary values. We run a transformation dry-run against a subset of records and compare counts against the Actindo source before proceeding to full import.

  5. Sandbox import and reconciliation

    We run a full import into a Dolibarr test instance using production-like data volume. The customer's operations lead reconciles record counts (Third Parties in, Products in, Orders in, stock levels in), spot-checks 25-50 records against Actindo source data, and verifies the Material-Article linkage in Dolibarr. We resolve any mapping corrections in the transformation scripts before production import begins. Any Actindo records that cannot be mapped to a Dolibarr equivalent are flagged in a reconciliation report with a recommended resolution (archive, merge, or skip).

  6. Production migration and cutover

    We run the production migration with master data first (Third Parties, Products, Warehouses), followed by transactional records (Orders, Purchase Orders, Invoices), and closing with engagement notes and POS history. We freeze Actindo writes during the cutover window, run a final delta extraction for any records modified during migration, and load the delta into Dolibarr. We deliver the DataHub ETL mapping inventory and Workflow rule matrix to the customer's admin team for post-migration rebuild. We do not rebuild DataHub integrations or Workflow Engine definitions as part of standard migration scope.

  7. Post-migration support and rebuild handoff

    We support a five-business-day hypercare window following cutover, during which we resolve any reconciliation issues identified by the customer's team. We verify that Products with Article content are correctly linked, that stock levels in Dolibarr match Actindo's warehouse totals, and that order and invoice totals reconcile against Actindo's published figures. We do not provide ongoing admin support, training, or workflow rebuild as standard scope; these are separate engagements with the customer's Dolibarr implementation partner or in-house admin.

Platform deep dives

Context on both ends of the pair

Actindo Core1 logo

Actindo Core1

Source

Strengths

  • MACH-Alliance certified composable ERP that integrates without replacing existing systems
  • Handles up to 40,000 orders per hour across B2C, B2B, marketplace, and social commerce channels
  • Real-time inventory reconciliation across multiple warehouses and POS locations
  • Built-in DataHub ETL module supporting CSV, XML, EDIFACT formats for flexible data exchange
  • Pre-built connectors to major ecommerce platforms including Shopware 6, Shopify, and Amazon

Weaknesses

  • Limited verified customer reviews make independent quality assessment difficult
  • Pricing and tier features not publicly documented for Pro and Enterprise plans
  • Implementation typically requires specialized external consultants
  • English-language documentation coverage is thinner than German help center content
  • API rate limits and authentication details not publicly documented
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 Actindo Core1 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

    Actindo Core1: Not publicly documented.

  • Data volume sensitivity

    A

    Actindo Core1 exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

Walk through your Actindo Core1 to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Standard migrations under 10,000 orders and 5,000 product records with a clean DataHub export and no legacy ERP co-running complete in three to five weeks. Migrations involving complex Material-Article splits across multiple sales channels, large warehouse bin structures, POS transaction history, or a legacy ERP still running alongside Actindo that requires dual-direction sync coordination move to eight to twelve weeks. Dolibarr module activation and extrafield configuration add one to two weeks to the schedule if the target instance is a fresh installation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Actindo Core1.
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