ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty (Customer)
1:1Herbst 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
Dolibarr ERP
ThirdParty (Supplier)
1:1Herbst 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
Dolibarr ERP
Product or Service
1:1Herbst 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
Dolibarr ERP
Account (Plan Comptable)
1:1Herbst'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
Dolibarr ERP
Invoice (Customer) with status Open
1:1Herbst 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
Dolibarr ERP
Invoice (Supplier) with status Open
1:1Herbst 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
Dolibarr ERP
Commande (Order)
1:1Herbst 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
Dolibarr ERP
CommandeFournisseur (Supplier Order)
1:1Herbst 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)
Dolibarr ERP
Product Stock (Warehouse)
1:1Herbst 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
Dolibarr ERP
User
1:1Herbst 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
Dolibarr ERP
ExtraFields
lossyHerbst 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
Dolibarr ERP
Employee Summary (HR module)
1:1Herbst 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.
| Herbst Insight ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Customer)1:1 | Fully supported | |
| Supplier | ThirdParty (Supplier)1:1 | Fully supported | |
| Item | Product or Service1:1 | Fully supported | |
| Chart of Accounts | Account (Plan Comptable)1:1 | Fully supported | |
| Open AR | Invoice (Customer) with status Open1:1 | Fully supported | |
| Open AP | Invoice (Supplier) with status Open1:1 | Fully supported | |
| Sales Order | Commande (Order)1:1 | Fully supported | |
| Purchase Order | CommandeFournisseur (Supplier Order)1:1 | Fully supported | |
| Inventory (Stock) | Product Stock (Warehouse)1:1 | Mapping required | |
| User | User1:1 | Fully supported | |
| Custom Fields and Properties | ExtraFieldslossy | Mapping required | |
| Payroll Records | Employee Summary (HR module)1:1 | Mapping required |
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.
Herbst Insight ERP gotchas
Herbst does not publish public API documentation or rate limits
Herbst Web Portal exports are module-scoped, not transactional graphs
SaaS hosting means migration windows depend on vendor co-operation
Payroll module migration requires jurisdiction-specific sign-off
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
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.
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.
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.
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.
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.
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
Herbst Insight ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Herbst Insight ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Herbst Insight ERP and Dolibarr ERP.
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
Herbst Insight ERP: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Herbst Insight ERP 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 Herbst Insight ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Herbst Insight ERP
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.