Migrate from Icicle ERP to Odoo ERP

Icicle Products store full formulation hierarchies (ingredients, packaging BOMs, allergen declarations, nutritional data) as a native concept. We map these 1:1 to Odoo Product records, with the formulation stored as a multi-level Odoo BoM (Bill of Materials) using the appropriate BoM type (kit for components, manufacture for production recipes). Allergen fields and nutritional data migrate as custom fields on the Product record. Unit-of-measure conventions (weight, volume, case-pack configurations) migrate to Odoo's UoM model with the customer's existing UoM category structure preserved.

Icicle Production Orders link to Formulations, scheduled batches, and resource allocations. We migrate production order history, quantities run, and the resulting finished-goods lot numbers to Odoo Manufacturing Orders. The Odoo MRP module must be installed and configured before migration; we create Work Centers and Routing definitions that mirror the resource allocation structure from Icicle so that production scheduling continuity is preserved.

Lot traceability in Icicle is a first-class linked graph connecting raw-material lots to in-process lots to finished-goods lots. Odoo tracks lots at the inventory level with stock moves but does not have a native genealogy graph. We map the full lot graph during scoping and configure Odoo's lot tracking to represent the same traceability relationships using lot numbers, linked stock moves, and a traceability report extension. Forward and backward traceability must be verified in a test migration before production cutover because broken lot links represent a food-safety compliance gap.

Icicle tracks inventory at the lot level with locations, expiry dates, and QC hold statuses. We map these to Odoo Stock Quant records, preserving the lot reference, location (Warehouse/Location), on-hand quantity, and expiry date. QC hold statuses from Icicle migrate as a custom field and a quality alert flag so that lots under active quality holds do not enter the production or sales pipeline without explicit release.

Quality checks in Icicle are tied to specific lots and production orders with pass/fail criteria and inspector assignments. Odoo models QC as Quality Check records attached to manufacturing or picking operations, with Quality Alerts for non-conformance. We map Icicle inspection records to a combined Odoo Quality Check and Quality Alert structure, preserving the lot reference, inspection date, inspector, and pass/fail result. The customer must install the Quality Control app in Odoo before migration.

Icicle Supplier records include food-safety rating fields, certifications (organic, kosher, halal), and approval statuses. We migrate all supplier fields to Odoo Contact records with the supplier flag enabled, and certifications migrate as custom fields or tags. The supplier approval workflow state at migration cutover is preserved so that any vendors currently on hold are not reactivated without explicit review in Odoo.

Customer records in Icicle include standard billing and shipping fields and customer-specific pricing tiers. We map these to Odoo Company records (for B2B customers) or direct Contact records (for B2C), with the customer-specific pricing tier stored as a custom field or pricing list reference on the Contact or Quotation. Customer-specific pricing rules in Icicle may require Odoo pricelist configuration post-migration.

Sales Orders in Icicle reference Products, Customers, and Delivery schedules. We map open sales orders to Odoo Sale Orders by status. Orders tied to specific lots (for lot-reserved deliveries) are flagged during migration so that the lot reservation logic in Odoo is configured correctly. Completed or cancelled historical orders are migrated as closed records for audit purposes but are not activated in the Odoo sales pipeline.

Accounts payable records in Icicle must be extracted and matched to vendor records. Open invoice amounts, due dates, and payment terms map to Odoo Vendor Bills. We preserve the invoice status (open, partially paid, paid) and ageing buckets at cutover. Closed historical invoices are archived rather than loaded into Odoo to avoid cluttering the accounting module. The Odoo Accounting app must be installed and the fiscal year configured before AP migration.

AR records in Icicle reference customer accounts and open sales orders. Outstanding invoice balances, due dates, and payment terms are remapped to Odoo Customer Invoices with the ageing buckets preserved. We flag any invoices linked to lots currently under QC hold so that the finance team does not recognize revenue on holds. Odoo's account receivable reconciliation process begins after AR migration to match payments against the imported invoices.

Icicle's GL structure includes food-industry-specific accounts (cost of goods sold by product category, COGS splits by facility). We map these to Odoo's chart of accounts and flag accounts that require creation as new in Odoo. Multi-facility Icicle deployments may have per-facility cost center structures that require Odoo's analytic accounting configuration to represent the same cost allocation. The Odoo Accounting app must be fully configured with the chart of accounts before any transactional data (AP/AR) migrates.

Icicle's co-packer mode adds customer-specific contract fields (formula versioning, NDA flags, customer-specific spec documents) that do not map directly to a standard Odoo object. We identify these co-packer extensions during the data audit phase and map them as custom fields on the Odoo Product (for formula versioning and spec documents) and Contact (for NDA flags and contract metadata). File attachments associated with co-packer records migrate as Odoo attachments linked to the parent record. The customer must configure NDA tracking and contract workflow logic post-migration using Odoo's standard tools.