Migrate from IS Packaging to Infor CloudSuite Corporate

IS Packaging Items map to CloudSuite Industrial Part records (item_num, description, uom_code, item_type, and costing layers). We extract all standard Item fields plus any custom properties added by the VAR. The item type (purchased, manufactured, phantom) maps directly to Infor's ItemType domain. Costing layers (standard, average, lot) map to Infor's CostType structure. Source item numbers become Infor item_num; the item revision cross-reference table built during discovery maps effective dates to Infor ItemRev revision codes.

IS Packaging BOMs are revision-controlled recipes linking parent Items to component Items with quantities and operations. We preserve every BOM revision, routing steps, and phantom assembly flag. BOM revisions map to Infor BOMRevision records with the effective date cross-referenced to Infor's revision code. Phantom assemblies map to Infor's bom_mtl_item_type = P (Phantom). If the destination uses a different revision scheme than the source, we apply the revision cross-reference table built during discovery.

IS Packaging Production Orders link BOMs to scheduled quantities, plant, and work center. They map to CloudSuite Industrial Job records. The production order status (Open, Released, Complete, Closed) must map to Infor's Job status codes (E=Entered, R=Released, F=Firm, U=Unreleased). We either quiesce open orders before migration or build a status mapping matrix that resolves the lifecycle difference. Partial completion percentages migrate to JobMaterial and JobOper records with issued quantities set accordingly.

IS Packaging Work Orders carry scheduling, labor, and machine time tied to Production Orders. They map to CloudSuite Industrial JobOper (operations) and LaborTicket records. Status flags on Work Orders vary between plants so we apply destination status mapping during import. If IS Packaging tracks machine and labor time separately, these map to Infor's LaborTick and LaborCode records with the appropriate work center reference.

Finished Goods in IS Packaging are stored at Location records tied to Items with lot/serial tracking. We map Locations to Infor Warehouse and ItemLoc records. On-hand quantities preserve at migration time. Lot and serial associations migrate as LotMst and SerNum records linked to ItemLoc. Multi-plant location names map to Infor's Site-Warehouse hierarchy.

IS Packaging transaction history (receipts, issues, adjustments) maps to CloudSuite Industrial InvTrans records. Large transaction volumes require chunked extraction and sequencing to preserve chronological integrity. We recommend migrating 12-24 months of transactional history into CloudSuite and archiving older history to the Infor Data Lake or an external data warehouse, because CloudSuite's transactional database has storage and performance implications for multi-year loads.

IS Packaging Customer Orders reference Items and pricing rules. We map order headers and line items to Infor OrderHead and OrderDetail. Any custom pricing or uom conversion rules are flagged for manual review before import. Open orders migrate with current status; completed or invoiced orders migrate as historical records with a closed status flag. Pricing rules that cannot be mapped directly are noted in the handoff document.

IS Packaging Vendor masters include contact info, terms, and item-supplier cross-references. We extract and reassociate vendor-to-item links at migration time. Vendor records map to Infor Vendor records with payment terms, bank details, and the supplier part number cross-reference preserved in VendorItem.

Custom fields added to standard objects in IS Packaging require field-level mapping. We inventory all custom field names, types, and values during the discovery phase. CloudSuite Industrial supports user-defined columns (UD columns) on standard tables. We pre-create the UD column schema in the destination database before import and map source values accordingly. Fields that cannot map to UD columns are flagged in the handoff document for manual entry or Mongoose-based custom form development.

IS Packaging's accounting structure may differ between instances. We map account codes to Infor Account segments and flag any inactive or intercompany accounts that need reactivation. If IS Packaging uses a different segment structure (e.g., cost center embedded in account code vs. separate dimension), we build a mapping matrix during discovery and apply it at import. GL transaction history migrates as summary balances rather than line-level detail to avoid overwhelming the CloudSuite GL.