Migrate from iCast to Infor CloudSuite Corporate

iCast customer records (with payment terms, credit limits, account managers, and address data) map to Infor CloudSuite Customer records. We map the customer number to the Infor cust_num field and preserve the account manager reference as a Contact link. Any iCast custom fields on the Customer record are flagged during discovery and re-created as Infor OS custom fields before migration; they are not automatically carried forward.

iCast vendor records (address, payment terms, account numbers, and contact information) map to Infor CloudSuite Supplier records. We use vendor number as the dedupe key and preserve the AP contact details. Vendor records must load before any Purchase Order records so that the supplier reference is satisfied at the time of PO import.

iCast inventory items (SKU, description, unit of measure, cost, warehouse location, and serialized tracking flags) map to Infor CloudSuite Item master records. Multi-location inventory requires that iCast warehouse location codes are pre-mapped to Infor Site and Warehouse records before Item load. Serialized items require the Serialized Item flag set in Infor before import so that serial number history can be attached to the correct item record.

iCast inventory snapshots by warehouse location map to Infor Item Warehouse Quantity records. Each iCast location code resolves to a specific Infor Site-Warehouse combination. Quantity on hand, allocated quantity, and available quantity transfer as separate fields in the IWQ record. We flag any negative inventory quantities for customer review before load.

Open iCast sales orders (with line items, pricing, quantities, and order status) map to Infor CloudSuite Sales Order records. We map iCast order status to the equivalent Infor order status codes and preserve the customer reference and salesperson assignment. Orders in Held or Pending status are flagged for manual review before migration so that the customer can decide whether to proceed, cancel, or convert before entering the Infor system.

Open iCast purchase orders (with vendor references, line items, quantities, expected dates, and PO status) map to Infor CloudSuite Purchase Order records. The vendor reference must resolve to a valid Infor Supplier before PO import. Line item resolution requires that the Item master is loaded first so that product codes match at insertion time.

iCast hierarchical chart of accounts maps to Infor CloudSuite Account records. Account number, account type, and description transfer directly. This object is loaded first in the dependency chain because Journal Entries, Sales Orders, and Purchase Orders all reference account numbers for posting. Any accounts used in historical transactions that do not yet exist in the destination are flagged for creation before those transaction imports proceed.

iCast general journal entries (date, account references, debit/credit amounts, memo) map to Infor CloudSuite GL Journal Entry records. We migrate journal entries within the agreed historical window (typically 2-3 years) and flag any entries with non-standard account mappings that reference accounts not yet created in the destination chart. Posting date and period must fall within an open accounting period in Infor.

iCast user accounts (login, roles, and access permissions) map to Infor CloudSuite User records. We resolve by email or by name match against the Infor user table. Roles and permission sets do not migrate as configuration because Infor's role model is structured differently from iCast's; we deliver a role mapping spreadsheet for the customer's admin to configure post-migration. Inactive iCast users are held in a provisioning queue.

iCast custom fields, calculated fields, and extended data columns are inventoried during discovery and re-created as Infor OS custom fields before migration. This is a configuration step, not a data move: the custom field must exist in Infor before records containing that field can be imported. We provide a complete custom field manifest with field name, data type, and purpose so that the Infor consultant or admin can configure them correctly. Custom business rules embedded in iCast calculated fields require manual review for equivalent expression in Infor.

iCast production orders and shop floor work orders map to Infor CloudSuite Industrial Job records. Job status, BOM reference, routing reference, and estimated quantities transfer. Open jobs are flagged for manual review to determine whether they should be migrated as active or closed in the new system. Completed historical production orders migrate as Job records with a closed status within the agreed historical window.

iCast BOM structures (parent item, component items, quantities per, operations, and work centers) map to Infor CloudSuite BOM records. The parent item and all component items must exist in the Infor Item master before BOM import so that the product code references resolve. We flag any BOMs that reference inactive items in iCast for customer review before load.