Migrate from Icicle ERP to Infor CloudSuite Corporate

Icicle Products with full formulation hierarchies (ingredients, BOMs, allergen declarations, nutritional data) map to Infor CloudSuite Industrial Items with Bill of Materials structures. Icicle uom codes (weight, volume, case-pack configurations) must be extracted first because Infor requires UOM codes to exist as reference data before creating Items. We extract all Icicle units of measure, provision matching Infor UOM codes, then create the Item records. Allergen and nutritional data that Icicle stores as formulation extensions migrate as custom fields on the Infor Item. Multi-facility Icicle deployments may store facility-specific formulations; we map these to Infor's site-specific BOM assignments.

Icicle Production Orders link to Formulations, scheduled batches, resource allocations, and the resulting finished-goods lot numbers. We map these 1:1 to Infor CloudSuite Industrial Work Orders. Production order history (quantities run, actuals, scrap) migrates as closed Work Order records with completion dates preserved. The key constraint is that Work Orders reference Items (finished goods) and BOMs that must exist before Work Order creation; we sequence provisioning accordingly. Resource allocations from Icicle map to Infor work center assignments, and the production order scheduling data migrates as work order planned start and completion dates.

Lot/Batch Records are the highest-risk migration object. Icicle stores lot genealogy as a native graph with forward and backward traceability links connecting raw-material lots to in-process lots to finished-goods lots. We extract the full lot graph (every lot ID, its parent lot references, child lot references, lot attributes, expiry dates) and map it to Infor CloudSuite Industrial's lot-controlled inventory structure. Before confirming this mapping, we verify that Infor's lot model can represent the same parent-child genealogy relationships; if not, we flag a gap in the food-safety compliance chain and work with the customer to define an alternative traceability representation (lot attributes, custom fields, or reference document linking). QC hold statuses on lots migrate as Infor lot hold flags so lots under active quality review are not available for allocation.

Icicle QC Inspections are tied to specific lots and production orders with pass/fail criteria, inspector assignments, and test results. Infor CloudSuite Industrial has a Quality Management module; we map inspection records to inspection headers with results and criteria migrated as inspection detail lines. Where Icicle inspection criteria do not map directly to Infor's quality code structure, we create custom fields on the inspection record to carry forward the original Icicle inspection type, test method, and acceptance criteria. Inspector assignments migrate as user references resolved through the Owner/User mapping phase.

Icicle Supplier records include food-safety rating fields, certifications (organic, kosher, halal), and approval workflow statuses. We map these 1:1 to Infor CloudSuite Industrial Suppliers. Food-safety rating fields migrate as custom Supplier fields if Infor's standard supplier schema does not include a food-safety rating attribute. Approval workflow state (approved, under review, suspended) migrates as a supplier status field, and certification expiry dates migrate as certification record fields or custom date fields on the Supplier.

Icicle Customer records include standard billing and shipping fields plus customer-specific pricing tiers. We map these 1:1 to Infor CloudSuite Industrial Customers. Customer-specific pricing tiers migrate as price code assignments or custom fields on the Customer record. Shipping addresses migrate as Customer ship-to addresses with the primary address designated as default. Customer financial terms from Icicle migrate as payment terms on the Infor Customer.

Icicle's co-packer mode adds customer-specific contract fields (formula versioning, NDA flags, customer-specific specification document references) that do not exist as standard fields in Infor CloudSuite. We identify these co-packer extensions during the data audit phase, create corresponding custom fields on the mapped Infor Product or Customer record, and map the values across. The original Icicle co-packer document IDs are preserved as text references so the customer can cross-reference source documents post-migration. This mapping is the most customer-specific part of an Icicle co-packer migration and requires explicit sign-off during scoping.

Open Accounts Payable records in Icicle must be extracted with vendor references resolved to the migrated Infor Supplier records. Open invoice amounts, due dates, and payment terms migrate to Infor's AP ledger; closed historical invoices are migrated as PDF attachments or reconciled offline because Infor CloudSuite typically resets AP at go-live and carries only open items into the new system. Vendor invoice numbers and PoNumbers migrate as invoice reference fields. Any pre-payments or credit memos attached to the vendor account migrate as credit memos on the Infor Supplier.

Open Accounts Receivable records in Icicle reference Customer accounts and open Sales Orders. We extract outstanding invoice balances and remap them to Infor CloudSuite AR with customer accounts resolved via the Customer mapping phase. Payment terms and aging buckets migrate as AR terms. Pre-payments and credit memos attached to the customer account migrate as credit memos in Infor. Closed historical AR invoices are migrated as attached documents or reconciled offline; only open items at migration cutover carry forward as live AR records.

Icicle's GL structure includes food-industry-specific accounts (cost of goods sold by product category, COGS splits by facility). We map these to Infor CloudSuite's chart of accounts, flagging any Icicle accounts that do not have a direct Infor equivalent. Infor requires a structured account code hierarchy; we work with the customer's finance team to design the account mapping before migration and create any missing accounts in Infor as custom GL accounts. Multi-facility Icicle deployments may have inter-company accounts; we map these to Infor's inter-company configuration.

Icicle attaches documents to Products, Production Orders, QC Inspections, and Suppliers. We extract all files with their associated record references and associate them with the corresponding migrated record in Infor. Infor CloudSuite includes Infor IDM (Infor Document Management) for document storage; if the customer has licensed IDM, we attach files natively. If not, we store them as ContentDocument records in Salesforce Content or as URL-linked file references pointing to the extracted source file location. We deliver a document index mapping each Icicle document to its destination record and file location.