ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
13 of 14
objects map 1:1 between Actindo Core1 and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty
1:1Actindo 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
Dolibarr ERP
Product (goods)
1:1Actindo 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
Dolibarr ERP
Product extrafields (channel content)
1:manyActindo 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
Dolibarr ERP
Warehouse
1:1Actindo 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
Dolibarr ERP
Order (CustomerOrder)
1:1Actindo 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
Dolibarr ERP
SupplierOrder
1:1Actindo 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)
Dolibarr ERP
Invoice
1:1Actindo 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)
Dolibarr ERP
SupplierInvoice
1:1Actindo 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
Dolibarr ERP
ThirdParty (Supplier type)
1:1Actindo 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
Dolibarr ERP
Order (CustomerOrder) with store attribute
1:1Actindo 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
Dolibarr ERP
Dolibarr module configuration + documentation
1:1Actindo 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
Dolibarr ERP
Written rule matrix + documentation
1:1Actindo 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
Dolibarr ERP
Category
1:1Actindo 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
Dolibarr ERP
Bank transaction + payment
1:1Actindo 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.
| Actindo Core1 | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty1:1 | Fully supported | |
| Material | Product (goods)1:1 | Fully supported | |
| Article | Product extrafields (channel content)1:many | Fully supported | |
| Warehouse | Warehouse1:1 | Fully supported | |
| Order | Order (CustomerOrder)1:1 | Fully supported | |
| Purchase Order | SupplierOrder1:1 | Fully supported | |
| Invoice (customer) | Invoice1:1 | Fully supported | |
| Invoice (vendor) | SupplierInvoice1:1 | Fully supported | |
| Vendor | ThirdParty (Supplier type)1:1 | Fully supported | |
| POS Transaction | Order (CustomerOrder) with store attribute1:1 | Fully supported | |
| DataHub ETL configuration | Dolibarr module configuration + documentation1:1 | Fully supported | |
| Workflow Engine definitions | Written rule matrix + documentation1:1 | Fully supported | |
| Product category | Category1:1 | Fully supported | |
| Bank movement / payment | Bank transaction + payment1: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.
Actindo Core1 gotchas
Legacy ERP coupling creates dual-direction migration complexity
Custom workflow configurations require manual rule translation
Article PIM data and Material product data are separate entities
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 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.
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.
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.
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.
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).
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.
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
Actindo Core1
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 Actindo Core1 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
Actindo Core1: Not publicly documented.
Data volume sensitivity
Actindo Core1 exposes a bulk API — large-volume migrations stream efficiently.
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 Actindo Core1 to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Actindo Core1
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.