ERP migration

Migrate from Icicle ERP to Dolibarr ERP

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 logo

Icicle ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

objects map 1:1 between Icicle ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

4-8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Icicle ERP logo

Icicle ERP

What's pushing teams away

  • Navigation complexity for new users — Capterra reviewers note the UI has many avenues to access the same function, and the learning curve is steep without formal training and the vendor's help videos.
  • Limited review volume — G2 shows only 28 verified reviews for Icicle ERP, making it difficult for prospective buyers to assess long-term reliability compared to competitors with hundreds of reviews.
  • Pricing opacity — Icicle publishes no public pricing tiers; all quotes go through a sales process, which creates friction for small food businesses evaluating budget constraints.
  • Smaller vendor footprint — with roughly 15 employees, Icicle is a niche Canadian vendor compared to global ERP players, raising concerns about long-term product roadmap stability and support scalability.

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

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

maps to

Dolibarr ERP

Product (Article)

1:1
Fully supported

Icicle 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

maps to

Dolibarr ERP

Manufacturing Order

1:1
Fully supported

Icicle 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)

maps to

Dolibarr ERP

Product Stock Lot

lossy
Fully supported

Lot 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

maps to

Dolibarr ERP

Stock (Warehouse)

1:1
Fully supported

Icicle 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

maps to

Dolibarr ERP

Extra attributes on Stock or BOM

1:1
Fully supported

QC 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

maps to

Dolibarr ERP

ThirdParty (Supplier type)

1:1
Fully supported

Icicle 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

maps to

Dolibarr ERP

ThirdParty (Customer type)

1:1
Fully supported

Icicle 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

maps to

Dolibarr ERP

Order (Customer Order)

1:1
Fully supported

Icicle 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

maps to

Dolibarr ERP

Vendor Bills

1:1
Mapping required

Open 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

maps to

Dolibarr ERP

Customer Invoices

1:1
Mapping required

Accounts 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

maps to

Dolibarr ERP

General Ledger (Accounting)

1:1
Mapping required

Icicle'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

maps to

Dolibarr ERP

Documents (Linked Files)

1:1
Fully supported

Icicle 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.

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.

Icicle ERP logo

Icicle ERP gotchas

High

No publicly documented API for self-serve data export

Medium

Pricing is opaque — no published tiers or per-user rates

High

Lot traceability links are schema-critical and must survive migration

Medium

Co-packer contract records use non-standard field structures

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

  • Lot genealogy has no native Dolibarr equivalent

    Icicle models lot traceability as a native linked graph connecting raw-material lots to in-process lots to finished-goods lots with explicit parent-child relationships. Dolibarr's standard Lot module stores lot numbers on stock entries but does not natively model genealogy chains. We configure a custom Lot Relations structure using Dolibarr's linked-elements mechanism or a third-party traceability module before migration. If the customer's food-safety compliance audit requires verified genealogy at cutover, we identify this as a pre-migration configuration requirement and do not begin data migration until the traceability schema is validated in a test environment.

  • No public API for Icicle data export

    Icicle ERP does not publish a public REST API reference and no bulk-export endpoint was identified in vendor documentation. Customers must request data exports through Icicle support or their implementation team. We engage Icicle directly at the start of every outbound migration project to coordinate a structured data package, agree on the export format and field mapping before extraction begins, and document the agreed export format in the migration scope. This step adds one to two weeks to the project timeline compared to migrations with self-serve source APIs.

  • Co-packer contract fields require extra-attribute translation

    Icicle's co-packer mode adds customer-specific contract fields including formula versioning, NDA flags, customer-specific specification document references, and co-packer approval statuses that do not map to standard Dolibarr Product or ThirdParty fields. We identify these co-packer extensions during the data audit phase and map them as Dolibarr extra attributes on the Product (for formula versioning and spec documents) and ThirdParty (for NDA and approval flags) objects. The customer must confirm which co-packer attributes are audit-required in Dolibarr before we finalize the mapping.

  • Dolibarr's decimal precision limits may truncate cost data

    Dolibarr's Setup > Limits and accuracy page controls maximum decimals for unit prices (default 5) and total prices (default 2). Icicle's food-industry costing model may carry fractional unit costs at higher precision for ingredient-level production costing. If Icicle stores unit costs with more than 2 decimal places, Dolibarr's default total-price precision will truncate the calculated totals during migration. We identify the precision used in Icicle's cost fields during audit and configure Dolibarr's decimal settings before AP/AR migration begins.

  • Food-safety workflows and HACCP chains do not migrate

    Icicle's built-in HACCP task chains, IoT sensor logs, and audit trail configurations are food-safety compliance tools that exist as workflow and logging records in Icicle. These do not map to any Dolibarr base module. We extract a written inventory of every active HACCP task chain, IoT logging rule, and audit trail configuration from Icicle and deliver it as a rebuild guide for the customer's food-safety team to recreate in Dolibarr or a dedicated food-safety compliance platform. This is explicitly outside data migration scope.

Migration approach

Six steps for a successful Icicle ERP to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Icicle ERP logo

Icicle ERP

Source

Strengths

  • Purpose-built for food & beverage manufacturing, not a horizontal ERP with a food module bolted on.
  • First-class lot traceability with forward and backward genealogy as a native data concept, not a workaround.
  • Cloud-based with multi-facility support, enabling single-database operations across multiple plants.
  • Integrated food safety and quality modules (HACCP, FSMA) reduce the need for separate compliance tooling.
  • Strong customer service reputation with 5.0/5.0 on Capterra for support quality.

Weaknesses

  • Very small vendor with approximately 15 employees, raising long-term roadmap and support scalability questions.
  • No public pricing published; all licensing requires a direct sales conversation.
  • Small review base (28 verified G2 reviews) limits third-party reliability signals for buyers.
  • Limited publicly documented API or data export tooling, making self-serve data extraction harder for customers.
  • Less suitable for food businesses with complex international operations across multiple regulatory jurisdictions.
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 Icicle ERP and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between Icicle 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

    Icicle ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Straightforward migrations under 5,000 products, 3,000 lots, and 500 production orders with clean traceability data complete in four to six weeks. Migrations with complex lot genealogy chains, co-packer contract records, multi-facility stock locations, or open AP/AR balances exceeding 1,000 records move to eight to fourteen weeks. The Icicle export coordination step adds one to two weeks compared to migrations with self-serve source APIs; this is included in our timeline estimate.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Icicle 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