Migrate from Icicle ERP to Microsoft Dynamics 365 Business Central

Icicle Products carry formulation hierarchies (ingredients, packaging BOMs, allergen declarations, nutritional data) that map to Dynamics 365 Item records with Bill of Materials structures on the Item. Unit-of-measure conventions specific to food production (kg, L, case-pack configurations) migrate as UOM schedule entries. Allergen declarations carry as custom text fields or as extended attribute records on the Item. We resolve formulation versioning by selecting the most recent active formula at migration time.

Icicle Production Orders link to Formulations, scheduled batches, and resource allocations with order history, quantities run, and resulting finished-goods lot numbers. We map these to Dynamics 365 Production Orders, preserving the production order number as a reference field, the scheduled start and end times, and the output lot assignment. Closed Production Orders migrate as historical records with estimated versus actual output quantities retained. Active in-process Production Orders require special handling to map the current production stage correctly.

Lot traceability is the highest-severity migration object because Icicle stores it as a linked graph (raw-material lot → in-process lot → finished-goods lot) with forward and backward genealogy. Dynamics 365 does not have a native multi-level lot genealogy table. We represent this as a custom LotGenealogy table in Dynamics 365 with parent-lot ID and child-lot ID lookups, plus a genealogy depth field. Every raw-material receipt and finished-goods output lot number is registered in the Inventory Lot table, and the genealogy links are reconstructed as separate relational records. We verify this structure in the destination Dynamics 365 environment before migration to confirm it meets the customer's food-safety audit requirements.

Icicle tracks inventory at the lot level with locations, expiry dates, and QC hold statuses. We map these to Dynamics 365 Warehouse Management lot numbers, preserving the lot ID, location code, expiry date, and QC hold flag as a custom field or warehouse quality order status. Lots under active quality holds are flagged so they cannot be allocated to outbound orders without explicit QC release.

Quality checks in Icicle are tied to specific lots and production orders with pass/fail criteria, inspector assignments, and attached documents. Dynamics 365 Quality Management uses Quality Associations (linked to sampling rules on item model groups) and Quality Journals (recording inspection results). We map Icicle QC records to Quality Journal lines, linking each journal entry to the relevant lot number and production order. The pass/fail determination maps to Quality Journal status, and inspector name carries as a free-text or User lookup field.

Icicle Supplier records include food-safety rating fields, certifications (organic, kosher, halal, SQF, BRC), and approval workflow states. We map these to Dynamics 365 Vendor records with the food-safety rating carried as a custom numeric or rating field, certifications stored as vendor contact certifications or as extended attributes, and the approval status mapped to the Vendor's blocked or workflow status. Vendor payment terms, lead times, and addresses migrate directly.

Customer records in Icicle include standard billing and shipping fields plus customer-specific pricing tiers and delivery schedules. We map these to Dynamics 365 Customer records (Sales and Receivables module), preserving pricing group assignments, ship-to addresses, and any customer-specific delivery window requirements. Customer credit limits and payment terms migrate to the Receivables management section.

Sales Orders in Icicle reference Products, Customers, and Delivery schedules. Open Sales Orders migrate to Microsoft Dynamics 365 Sales Orders with order lines mapped to Item numbers and quantities. Where Icicle links Sales Orders to specific production lots for shelf-life or recall compliance, we preserve those lot references as order line custom fields or as linked records. Closed Sales Orders migrate as historical records without changing inventory.

Open accounts payable records in Icicle must be extracted, matched to vendor records, and mapped to Dynamics 365 Vendor Invoice Journal entries. Open invoice amounts, due dates, and payment terms migrate to open Vendor Transactions in the AP ledger. We flag any invoices linked to lots under QC hold so that payment release aligns with QC clearance in the destination system. Historical paid invoices migrate as posted ledger entries for audit continuity.

AR records reference customer accounts and open sales orders. We extract outstanding invoice balances and remap them to Dynamics 365 Customer Ledger Entries, preserving payment terms, ageing buckets, and the original invoice dates. AR records linked to specific lots carry the lot reference in a custom field for recall management. Historical closed invoices migrate as posted customer entries.

Icicle's GL structure includes food-industry-specific accounts (cost of goods sold by product category, COGS splits by facility). We map these to the Dynamics 365 chart of accounts, flagging accounts that require new G/L dimensions (Department, Cost Center, Facility) for multi-facility cost allocation. We also flag accounts that do not have a clear Dynamics 365 equivalent and require the customer's finance team to define the mapping during scoping.

Icicle's co-packer mode adds customer-specific contract fields (formula versioning, NDA flags, customer-specific spec documents, and approval workflows) that do not map to a standard Dynamics 365 Product or Vendor object. We identify these co-packer extensions during the data audit phase and represent them as custom fields on the Vendor record (NDA status, contract expiry) and on the Product record (formulation version, spec document reference). The customer approves the custom field design before we implement the schema in the Dynamics 365 sandbox.

Icicle attaches documents to Products, Production Orders, QC Inspections, and Suppliers. We extract files and associate them with the corresponding migrated record. Dynamics 365 Business Central uses document attachments on records; Finance and Operations can use SharePoint integration or the Manage Document feature. We align the attachment strategy to the customer's chosen Dynamics 365 storage model during scoping.