ERP migration

Migrate from Herbst Insight ERP to Dolibarr ERP

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

Herbst Insight ERP logo

Herbst Insight ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Herbst Insight ERP to Dolibarr is a structured extraction-and-load migration where the primary constraint is Herbst's lack of a public REST API. We establish direct database access or staged CSV exports per module during scoping, and we reconstruct the relational graph between Customers, Orders, and Payments using the foreign-key fields present in the export. Dolibarr's modular architecture (CRM, Third-Parties, Products, Orders, Invoices, Stock, Projects) means we activate only the modules matching the customer's active Herbst footprint. Custom fields and custom properties from Herbst map to Dolibarr's ExtraFields system. Workflows, automations, document binary storage, and time-and-attendance records do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Dolibarr's configuration layer. Payroll migration is scoped to summarised effective-dated records subject to Irish employment law sign-off from the customer's finance and HR leads.

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

Herbst Insight ERP logo

Herbst Insight ERP

What's pushing teams away

  • No public pricing — quotes are sales-led through Herbst Software or its reseller network.
  • Ireland-centric — multinational SMEs operating outside Ireland may find international support and localisation thinner than NetSuite or Sage Intacct.
  • Limited public API documentation — extraction requires reseller or vendor engagement.
  • Smaller third-party developer/integrator ecosystem compared to mainstream cloud ERPs.
  • Companies scaling beyond mid-market complexity (multi-entity consolidation, IFRS reporting at scale) typically migrate to NetSuite, Microsoft Dynamics 365, or SAP.

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

Each row shows how a Herbst Insight ERP 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.

Herbst Insight ERP

Customer

maps to

Dolibarr ERP

ThirdParty (Customer)

1:1
Fully supported

Herbst Customer records (billing, shipping, contact details, credit-limit, payment-terms) map to Dolibarr ThirdParty records with the Client checkbox enabled. We map Customer code, name, address, email, phone, and VAT number directly. The Herbst Customer's credit-limit maps to the Dolibarr Conciergerie credit-limit field; payment-terms map to cond_reglement_code. Any multi-address structure in Herbst collapses to a single primary address with shipping address as a separate address record in Dolibarr's addresses table.

Herbst Insight ERP

Supplier

maps to

Dolibarr ERP

ThirdParty (Supplier)

1:1
Fully supported

Herbst Supplier records map to Dolibarr ThirdParty with the Fournisseur checkbox enabled. We preserve supplier code, name, address, banking details, and purchasing terms. Open PO references attached to the Supplier account in Herbst are catalogued separately during scoping and escalated to the customer for disposition (carry forward, close, or archive) before migration.

Herbst Insight ERP

Item

maps to

Dolibarr ERP

Product or Service

1:1
Fully supported

Herbst Items (products with pricing, cost, stock-control settings, BOM data) map to Dolibarr Product records. The Item type (stockable, service, assembly) determines the Dolibarr type (Produit or Service). Primary SKU maps to ref; description maps to label; cost maps to cost_price; pricing maps to price level entries in the Dolibarr price database. Variant attributes for manufacturing items map to Dolibarr product_attribute rows if the productvariants module is activated.

Herbst Insight ERP

Chart of Accounts

maps to

Dolibarr ERP

Account (Plan Comptable)

1:1
Fully supported

Herbst's flexible nominal structure with full COA export maps directly to Dolibarr's double-entry accounting module. We preserve account codes, account names, and posting-level flags. Irish VAT codes and RCT payment retention codes map to Dolibarr tax rules as separate configuration entities. The chart of accounts must be activated in Dolibarr before any invoice or payment migration begins because accounting entries reference the COA at insert time.

Herbst Insight ERP

Open AR

maps to

Dolibarr ERP

Invoice (Customer) with status Open

1:1
Fully supported

Herbst open receivables migrate as Dolibarr Customer invoices with status draft or unpaid. Header records carry customer reference, invoice date, due date, and total; line items carry product references and amounts. The Herbst AR subledger reference is preserved in Dolibarr's fk_payment condition. We flag any orphaned invoice lines (lines without a matching customer reference) and escalate to the customer's finance lead before loading.

Herbst Insight ERP

Open AP

maps to

Dolibarr ERP

Invoice (Supplier) with status Open

1:1
Fully supported

Herbst open payables migrate as Dolibarr Supplier invoices with status draft or unpaid. We map supplier reference, invoice date, due date, and total. Line items carry product/service references and amounts. RCT retention values from Herbst map to Dolibarr accounting entries on a dedicated retention account. Open AP and Open AR are migrated before historical transactions to establish the starting trial-balance reference in Dolibarr.

Herbst Insight ERP

Sales Order

maps to

Dolibarr ERP

Commande (Order)

1:1
Fully supported

Herbst Sales Order history maps to Dolibarr Commande records with the Customer link established via ThirdParty foreign key. Order header status (Draft, Confirmed, Invoiced, Partial, Cancelled) maps to Dolibarr statut_commande. Line items map with product references, quantities, unit prices, and discount rates. Fulfillment links from Herbst are preserved as notes on the Dolibarr order record. Partial or voided orders require explicit value-mapping decisions during scoping and are flagged for customer sign-off.

Herbst Insight ERP

Purchase Order

maps to

Dolibarr ERP

CommandeFournisseur (Supplier Order)

1:1
Fully supported

Herbst Purchase Order history maps to Dolibarr CommandeFournisseur records with the Supplier link established via ThirdParty foreign key. Order status, line items, and amounts migrate in the same pattern as Sales Orders. Any open PO references attached to a Supplier account in Herbst are catalogued and either carried forward as open Dolibarr purchase orders or archived per the customer's instruction.

Herbst Insight ERP

Inventory (Stock)

maps to

Dolibarr ERP

Product Stock (Warehouse)

1:1
Mapping required

Herbst stock records include location, batch, and serial number fields that vary by warehouse configuration. We harmonize multi-warehouse stock records into Dolibarr warehouse entries. Bin-level data from Herbst maps to Dolibarr stock location descriptors if the stock warehouse module is activated. We validate stock quantities against a point-in-time snapshot taken during the extraction window to avoid post-extraction drift.

Herbst Insight ERP

User

maps to

Dolibarr ERP

User

1:1
Fully supported

Herbst user records include role assignments and access permissions that do not map 1:1 to Dolibarr's module-level permission model. We extract the user list (name, email, login, status) and map to Dolibarr users. Permission fields from Herbst are catalogued as an inventory document for the customer's admin to reconfigure per Dolibarr's permission system (global or per-module, restricted to specific features). Active and inactive status migrates directly.

Herbst Insight ERP

Custom Fields and Properties

maps to

Dolibarr ERP

ExtraFields

lossy
Mapping required

Herbst custom fields within modules map to Dolibarr ExtraFields on the equivalent entity. We catalog every custom field definition during discovery (field name, type, validation, module归属) and map to Dolibarr's extrafields table. Picklist-type custom fields map to Dolibarr's select or chkbxlst extrafield types. Any custom field with no Dolibarr equivalent is stored as a text-type extrafield and flagged for the customer to review post-migration.

Herbst Insight ERP

Payroll Records

maps to

Dolibarr ERP

Employee Summary (HR module)

1:1
Mapping required

Herbst payroll module stores effective-dated compensation, deduction codes, and payroll run history subject to Irish employment law compliance. We migrate payroll as summarised records (annual compensation totals, deduction code registry, most recent pay rate) rather than granular timesheet lines to avoid jurisdiction-mapping errors. The customer finance and HR leads must approve the payroll schema before any compensation data loads. Time-and-attendance records migrate as summary entries or are excluded if the destination Dolibarr instance does not activate the HR-timesheet module.

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.

Herbst Insight ERP logo

Herbst Insight ERP gotchas

High

Herbst does not publish public API documentation or rate limits

Medium

Herbst Web Portal exports are module-scoped, not transactional graphs

Medium

SaaS hosting means migration windows depend on vendor co-operation

Low

Payroll module migration requires jurisdiction-specific sign-off

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

  • Herbst lacks public API; export method must be established during scoping

    Herbst Insight ERP has no publicly documented REST or bulk API endpoint reference. Export-based migrations must rely on direct SQL access to the hosted database, partner export tools, or the Herbst Web Portal's module-scoped CSV exports. Direct database access provides the cleanest relational graph but requires Herbst vendor sign-off on a data access agreement. Staged CSV exports per module require us to reconstruct relational links (Customer-to-Order, Order-to-Invoice) from foreign-key fields present in the export, and any records missing linking fields are flagged as orphaned and escalated. We establish the access method during scoping before a migration timeline is confirmed.

  • Herbst portal exports are module-scoped; relational graph must be reconstructed

    The Herbst Web Portal exports Customer records, Order records, and Invoice records as separate module-scoped files with no automatic linkage. We reconstruct the relational graph during transformation using the foreign-key fields (customer_id on order, order_id on invoice) present in each export. Records missing these linking fields are escalated as orphaned before load. For invoice-to-payment links, we use the payment reference fields present in the AR/AP export to reconstruct the settlement chain in Dolibarr.

  • SaaS hosting means migration windows require Herbst vendor cooperation

    Because Herbst Insight ERP runs on Herbst's own hosted infrastructure, data extraction windows and any temporary access grants require coordination with the Herbst support or development team. We engage Herbst's professional services team directly during the migration scoping phase. Customers must confirm their current contract status and data extraction entitlements with their account manager before migration kickoff. Any delays in Herbst granting database access directly impact the migration timeline.

  • Binary document migration is out of scope; metadata transfer only

    Herbst's binary document storage (invoice PDFs, attached images, document files) is not accessible via standard export tools or direct database access in most configurations. We export document metadata (filename, document type, linked entity reference, creation date) separately and flag document-level file transfer as a manual step for the customer's IT team post-migration. We recommend exporting document metadata as a spreadsheet and using Herbst's bulk download tool if available to retrieve the binary files before access closes.

  • Payroll migration requires Irish jurisdiction sign-off

    Herbst Insight ERP's payroll module stores effective-dated compensation, deduction codes, and payroll run history subject to Irish employment law compliance. We migrate payroll as summarised records (annual compensation totals, effective pay rates, deduction code registry) rather than granular timesheet lines. The customer finance and HR leads must approve the payroll schema before any compensation data loads. If the destination Dolibarr instance does not activate the HR/Payroll module, payroll summary data migrates as a reference document rather than live records.

Migration approach

Six steps for a successful Herbst Insight ERP to Dolibarr ERP data migration

  1. Access method establishment and data audit

    We determine the Herbst export access path during scoping: direct SQL database access (preferred), Herbst professional services export engagement, or staged Web Portal CSV exports per module. We audit the Herbst instance across active modules (accounting, CRM, HR, distribution), record counts per entity, custom field definitions, open AP/AR balances, and any payroll module in scope. The audit output is a written data inventory, an export method recommendation, and a migration feasibility assessment.

  2. Dolibarr module selection and target schema design

    We configure the destination Dolibarr instance based on the Herbst modules in use. We activate only the required Dolibarr modules (ThirdParties, Products, Commercial, Invoices, Stock, Projects, HR if payroll is in scope) and configure country, currency, VAT rules, and chart of accounts before any data import. We map Herbst custom fields to Dolibarr ExtraFields on the equivalent entities, define the chart of accounts mapping (account code to account code), and set up warehouse and location structures for inventory migration.

  3. Direct database extraction or staged CSV export

    If direct SQL access is available, we extract the full relational snapshot (Customers, Suppliers, Items, COA, Orders, Invoices, Payments, Stock, Users, Payroll summaries) in a single coordinated extraction window with Herbst vendor co-operation. If CSV exports are required, we extract module-by-module files from the Herbst Web Portal, document the foreign-key linkage fields present in each export, and begin relational graph reconstruction during transformation. A point-in-time snapshot timestamp is recorded for each extraction to anchor stock quantity validation.

  4. Data transformation and relational graph reconstruction

    We transform source data into Dolibarr import format per module. For each Order, we resolve the Customer foreign key; for each Invoice line, we resolve the Customer, Product, and, where applicable, the originating Order. Orphaned records (Customer-less invoices, Order-less invoice lines) are flagged in a reconciliation report and escalated to the customer's finance lead for resolution before load. Custom field values transform to Dolibarr ExtraField format; payroll summaries transform to HR module entries subject to jurisdiction sign-off.

  5. Staged load and reconciliation in Dolibarr

    We load data into Dolibarr in dependency order: ThirdParties (Customers and Suppliers first because all transactional records reference them), Products/Services, Chart of Accounts (before invoices), Open AR/AP as draft invoices, Orders, Stock, Users, then Payroll summaries last. Each phase emits a row-count reconciliation report against the source extraction. We run validation checks (VAT number format, mandatory field completeness, account code existence) at each phase and pause for customer sign-off before the next phase begins.

  6. Cutover, delta migration, and post-migration document handoff

    We freeze Herbst write access during the cutover window, run a final delta migration for any records modified since the extraction snapshot, then confirm Dolibarr as the system of record. We deliver the custom field inventory, the Herbst workflow and automation summary (for manual rebuild in Dolibarr), the document metadata spreadsheet, and the payroll schema sign-off document to the customer's admin team. We support a one-week hypercare window for reconciliation issues. Workflows, automations, and document file transfer remain outside standard migration scope.

Platform deep dives

Context on both ends of the pair

Herbst Insight ERP logo

Herbst Insight ERP

Source

Strengths

  • SaaS delivery eliminates on-premise hardware, patching, and IT overhead for SMEs.
  • Modular design lets businesses configure only the modules they need — accounting, CRM, HR, payroll, distribution.
  • Irish-headquartered with direct vendor support and local reseller network.
  • Integrated web portal gives customers self-service access to orders, invoices, and statements.
  • Real-time ROM reports provide immediate visibility into accounts data across modules.

Weaknesses

  • Very limited public API documentation — export relies on direct database access or partner tooling.
  • Small market footprint compared to Tier-1 ERPs means fewer third-party integration templates exist.
  • Pricing tiers and feature gates are not publicly published, requiring direct sales engagement.
  • G2 review volume is extremely low (1 verified review), limiting independent quality signals.
  • Hosting is vendor-managed SaaS, giving customers limited control over infrastructure-level customisation.
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. All 8 core objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Herbst Insight ERP and Dolibarr ERP.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.

  • 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

    Herbst Insight ERP: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Migrations land between four and six weeks for straightforward extractions with direct database access, under 10,000 customer records, and no payroll migration. Migrations requiring Herbst professional services engagement for export tooling, multi-module ERP scope (accounting, CRM, HR, distribution), payroll summaries with jurisdiction sign-off, or large order histories extend to eight to twelve weeks. The primary timeline driver is establishing the data extraction path with Herbst's team, not the Dolibarr load itself.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Herbst Insight ERP.
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