ERP migration
Field-level mapping, validation, and rollback between Icicle ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Icicle ERP
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between Icicle ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
4-8 weeks
Overview
Icicle ERP to Dolibarr is a migration from a food-industry vertical platform to an open-source modular ERP. The structural gap is lot traceability: Icicle models lot genealogy as a native linked graph; Dolibarr stores lot numbers on Product and Stock entries but does not natively model forward-and-backward genealogy chains. We resolve this by configuring a custom Lot Relations module or using Dolibarr's product BOM tracking to replicate the traceability graph, and we verify the configuration before confirming migration scope. Co-packer contract records with formula versioning and NDA flags do not map to standard Dolibarr fields; we translate them as extra attributes on the Product object. Open AP/AR balances, the chart of accounts, and historical production costing data migrate to Dolibarr's accounting module. We do not migrate food-safety workflows, HACCP task chains, IoT sensor logs, or audit trail configurations; we deliver a written inventory of these for the customer's team to rebuild in Dolibarr or a dedicated compliance tool.
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 Icicle 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.
Icicle ERP
Product / Formulation
Dolibarr ERP
Product (Article)
1:1Icicle Products with formulation hierarchies (ingredients, BOMs, allergen declarations, nutritional data) map to Dolibarr Product records with BOM configuration enabled. Ingredient-level formulations migrate as Dolibarr BOM records under the finished product. Allergen declarations and nutritional data transfer as Dolibarr extra attributes. Product codes from Icicle's SKU field become Dolibarr barcodes or product refs for inventory scanning. Unit of measure conventions (weight, volume, case-pack configurations) transfer to Dolibarr's uom fields on each product line.
Icicle ERP
Production Order / Work Order
Dolibarr ERP
Manufacturing Order
1:1Icicle Production Orders linked to Formulations, scheduled batches, and resource allocations map to Dolibarr Manufacturing Orders. Batch quantities, scheduled start/end dates, and finished-goods lot numbers carry forward. Resource allocation data (equipment, labor flags) transfers as extra attributes on the Manufacturing Order since Dolibarr's base manufacturing module handles production routing without native resource scheduling. Co-packer production orders require additional mapping of customer contract references.
Icicle ERP
Lot / Batch Record (Traceability)
Dolibarr ERP
Product Stock Lot
lossyLot records are the highest-risk object in this migration. Icicle stores lot genealogy as a native linked graph (raw-material lot → in-process lot → finished-goods lot). Dolibarr's standard Lot module stores lot numbers per stock entry but does not model genealogy chains. We resolve this by configuring a custom Lot Relations structure using Dolibarr's linked-elements mechanism or a community module that tracks parent-child lot relationships, and we verify the destination schema can represent the full traceability graph before confirming migration scope. If the customer's food-safety requirements demand audit-ready genealogy, we flag this as a configuration requirement in the delivery document.
Icicle ERP
Inventory Lot / Stock Item
Dolibarr ERP
Stock (Warehouse)
1:1Icicle inventory lot records with locations, expiry dates, and QC hold statuses map to Dolibarr Stock entries. Lot IDs from Icicle become Dolibarr lot serial numbers; expiry dates transfer to the lot record; QC hold status transfers as a Dolibarr status flag or stock status update. Multi-facility Icicle locations map to Dolibarr warehouses, which must be configured before stock migration begins so that location lookups resolve at import time.
Icicle ERP
QC Inspection / Quality Check
Dolibarr ERP
Extra attributes on Stock or BOM
1:1QC Inspections in Icicle are tied to specific lots and production orders with pass/fail criteria and inspector assignments. Dolibarr has no native QC Inspection object in its base ERP module. We map inspection records to Dolibarr extra attributes on the relevant Stock lot record (last_inspection_date, inspector_name, pass_fail_flag) and document any inspection records that cannot be represented in Dolibarr's base schema as a gap in the migration scope report. For customers with mandatory QC documentation requirements, we recommend a third-party quality management module from the Dolibarr Marketplace.
Icicle ERP
Supplier / Vendor Record
Dolibarr ERP
ThirdParty (Supplier type)
1:1Icicle Supplier records including food-safety ratings, certifications (organic, kosher, halal), and approval statuses map to Dolibarr ThirdParty records with the Supplier type enabled. Certification fields transfer to Dolibarr extra attributes since the base ThirdParty object does not have native food-safety rating fields. Supplier approval workflow states (approved, pending, suspended) transfer as a status field. Vendor invoice references migrate as separate AP records.
Icicle ERP
Customer / Account Record
Dolibarr ERP
ThirdParty (Customer type)
1:1Icicle Customer records with billing and shipping addresses, contact information, and customer-specific pricing tiers map to Dolibarr ThirdParty records with Customer type enabled. Pricing tiers stored in Icicle's customer-specific fields transfer as Dolibarr price negotiation rules or extra attributes. Customer-specific NDA and specification document references (common in co-packer relationships) transfer as extra attributes on the ThirdParty record.
Icicle ERP
Sales Order / Sales Contract
Dolibarr ERP
Order (Customer Order)
1:1Icicle Sales Orders referencing Products, Customers, and Delivery schedules map to Dolibarr Customer Orders. Open orders migrate by status: draft, validated, shipped, and closed orders all transfer with their line items. Orders tied to specific lots carry the lot reference in the order line notes. Historical closed orders migrate as archived orders; active open orders require a status check to ensure they are not duplicated if the customer plans to keep Icicle running in parallel during migration.
Icicle ERP
Open AP / Vendor Invoices
Dolibarr ERP
Vendor Bills
1:1Open Accounts Payable records from Icicle must be extracted with vendor references, invoice numbers, amounts, due dates, and payment terms. These map to Dolibarr Vendor Bills in open status. Closed historical invoices migrate as archived records for audit trail purposes but are flagged as historical (not active ledger entries). The vendor lookup resolves against the migrated Supplier records using vendor name or ID as the dedupe key. Any Icicle payment terms stored per vendor transfer to Dolibarr's payment term configuration.
Icicle ERP
Open AR / Customer Invoices
Dolibarr ERP
Customer Invoices
1:1Accounts Receivable records from Icicle referencing customer accounts and open sales orders map to Dolibarr Customer Invoices in open status. Outstanding balances, due dates, and ageing buckets transfer to the invoice record. Payment terms stored per customer in Icicle apply to the migrated invoice. Closed historical invoices migrate as archived records. Customer-specific pricing flags from Icicle's sales module carry forward to ensure correct pricing on migrated invoices.
Icicle ERP
Chart of Accounts / General Ledger
Dolibarr ERP
General Ledger (Accounting)
1:1Icicle's GL structure includes food-industry-specific accounts (COGS by product category, facility cost splits) that map to Dolibarr chart of accounts entries. We create the destination account structure in Dolibarr before AP/AR migration so that account references resolve on invoice import. Accounts without a clear Dolibarr equivalent are flagged in the mapping document with a recommended account creation or parent-account assignment. Historical GL balances transfer as opening balance entries in Dolibarr's accounting module.
Icicle ERP
Document / File Attachment
Dolibarr ERP
Documents (Linked Files)
1:1Icicle documents attached to Products, Production Orders, QC Inspections, and Suppliers extract as files and associate with the corresponding migrated Dolibarr record via Dolibarr's document management system. The destination document directory structure mirrors the Icicle attachment hierarchy so that records and their supporting files remain linked. Document metadata (upload date, author, version) transfers where Dolibarr's document model supports it; unsupported metadata is preserved in a companion migration notes document.
| Icicle ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Product / Formulation | Product (Article)1:1 | Fully supported | |
| Production Order / Work Order | Manufacturing Order1:1 | Fully supported | |
| Lot / Batch Record (Traceability) | Product Stock Lotlossy | Fully supported | |
| Inventory Lot / Stock Item | Stock (Warehouse)1:1 | Fully supported | |
| QC Inspection / Quality Check | Extra attributes on Stock or BOM1:1 | Fully supported | |
| Supplier / Vendor Record | ThirdParty (Supplier type)1:1 | Fully supported | |
| Customer / Account Record | ThirdParty (Customer type)1:1 | Fully supported | |
| Sales Order / Sales Contract | Order (Customer Order)1:1 | Fully supported | |
| Open AP / Vendor Invoices | Vendor Bills1:1 | Mapping required | |
| Open AR / Customer Invoices | Customer Invoices1:1 | Mapping required | |
| Chart of Accounts / General Ledger | General Ledger (Accounting)1:1 | Mapping required | |
| Document / File Attachment | Documents (Linked Files)1: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.
Icicle ERP gotchas
No publicly documented API for self-serve data export
Pricing is opaque — no published tiers or per-user rates
Lot traceability links are schema-critical and must survive migration
Co-packer contract records use non-standard field structures
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
Icicle export coordination and data audit
We engage Icicle support directly to request a structured data export covering all objects in migration scope. We audit the exported files against the Icicle schema to confirm field coverage, identify any co-packer contract extensions, count the lot genealogy relationships in the traceability graph, and flag any objects or fields that require custom export formatting. The data audit output is a written inventory of what exists in Icicle, what maps directly to Dolibarr, what requires extra-attribute configuration, and what has no Dolibarr equivalent and will be documented instead of migrated.
Dolibarr schema provisioning and traceability configuration
We deploy Dolibarr into a staging environment and configure the manufacturing, stock, third-party, and accounting modules before any data import. This includes creating Dolibarr warehouses (mapped from Icicle facilities), configuring the BOM/Manufacturing module for production orders, provisioning lot numbers with the custom Lot Relations structure for genealogy chains, setting up extra attributes for food-safety fields, co-packer contract fields, and QC inspection metadata, and configuring the chart of accounts based on the Icicle GL export. The customer validates the schema configuration before we proceed to data migration.
Decimal precision and accounting configuration
We configure Dolibarr's Setup > Limits and accuracy page to match the decimal precision used in Icicle's costing data, set up payment term configurations for vendor and customer records, define the VAT/tax structure matching Icicle's tax codes, and create any required accounting journal configurations for AP, AR, and production costing entries. This step runs in parallel with schema provisioning and must be complete before any financial data imports begin.
Staging migration and reconciliation
We run a full migration into the Dolibarr staging instance using production data volume from the Icicle export. The customer reconciles record counts (Products, Lots, Production Orders, Suppliers, Customers, Invoices) and spot-checks 25-50 records against the Icicle source for accuracy. We specifically validate lot genealogy chains (traceability forward and backward), co-packer contract field completeness, and open invoice balances. Any mapping corrections, missing fields, or extra-attribute gaps are resolved in staging before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Products with BOMs first (to satisfy Manufacturing Order dependencies), then Lot records (with genealogy links established), Stock entries (with lot references resolved), Suppliers, Customers, Production Orders, Sales Orders, AP invoices, AR invoices, and GL opening balances last. Each phase emits a row-count reconciliation report before the next phase begins. Co-packer contract fields and QC inspection metadata load as extra-attribute updates after the base record migration completes.
Cutover, validation, and food-safety handoff
We freeze Icicle writes during cutover, run a final delta migration of any records modified during the migration window, then set Dolibarr as the system of record. We deliver the food-safety and HACCP workflow inventory document to the customer's food-safety team for rebuild guidance. We provide a one-week hypercare window to resolve any reconciliation issues. We do not rebuild HACCP chains, IoT logging configurations, or audit trail workflows inside the migration scope; those are separate engagements or internal compliance team tasks.
Platform deep dives
Icicle ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Icicle ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Icicle ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Icicle 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
Icicle ERP: Not publicly documented.
Data volume sensitivity
Icicle 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 Icicle ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Icicle 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 Icicle 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.