Migrate from Info.Net to Infor CloudSuite Corporate

Info.Net Items (finished goods, raw materials, and components with SKU, description, unit of measure, and cost) map 1:1 to Infor CloudSuite Product2 records. The Item number becomes ProductCode, description becomes Name, and unit of measure maps to the Infor Unit of Measure class. We confirm the Infor price book structure during scoping and create Standard Price Book entries during the Products phase. Multi-site manufacturers must confirm whether CloudSuite is configured for single-site or multi-site item assignments.

Info.Net Production Orders (manufacturing jobs with status, quantity, scheduled dates, and assigned work centers) map to CloudSuite Work Order. We preserve the full production history including completion dates, scrap quantities, and actual labor consumption. The production order number becomes the Work Order number; the Item number links to the Product2 lookup. Open Production Orders require status carry-forward confirmation; closed orders migrate as historical records with post dates preserved.

Info.Net Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. The full work order lifecycle including status transitions and actual labor consumption transfers to CloudSuite Work Order with the same lifecycle representation. Work Center assignments map to Infor Work Center codes that must exist in CloudSuite before Work Orders are loaded.

Info.Net multi-level BOM structures with revision versions and effective dates map to Infor CloudSuite BOMs. We preserve the component hierarchy across BOM levels, map revision naming conventions (Info.Net revision labels to CloudSuite BOM revision codes), and link BOMs to their parent Items via the Product2 lookup. BOMs must load before Work Orders because Work Orders reference the BOM as a production template.

Info.Net QC logs (inspection results, pass/fail flags, measurement data linked to production lots) map to CloudSuite Quality Management Inspection records. Field naming conventions differ between ERPs; we map measurement field names and preserve linked lot numbers. Inspection Plans in CloudSuite define the inspection criteria and acceptable ranges, and we flag any QC records referencing inspection types not pre-defined in the target CloudSuite QM module for manual setup.

Info.Net inventory movements (receipts, issues, adjustments, and transfers) with timestamps, quantities, and locations transfer to CloudSuite inventory transaction ledgers. Post dates are preserved to maintain accurate stock valuation. We sequence the transaction load to follow Items, Warehouses, and Work Centers so that location and item lookups resolve correctly. Inventory balances are recalculated in CloudSuite after transaction load to confirm matching on-hand quantities.

Info.Net Customer records with billing addresses, shipping addresses, and credit limits map to CloudSuite Customer. Multi-address customer accounts (ship-to and bill-to) require special handling to ensure address roles are assigned correctly in CloudSuite. We apply field-level mapping for address structures and deduplicate any duplicate customer records identified during data profiling. Credit limit data transfers as a custom field if the Infor CloudSuite edition does not include native credit management.

Info.Net Vendor master records with contact details, payment terms, and lead times map to CloudSuite Supplier. Address structures and multi-contact handling differ between ERPs; we apply field-level mapping and deduplicate duplicate vendor records. Payment terms map to Infor payment code definitions that must exist in CloudSuite before Supplier records load.

Info.Net custom fields on Items, Customers, and Vendors require pre-creation in CloudSuite before the corresponding records load. We extract custom field definitions (name, data type, picklist values if applicable) during discovery, map them to Infor CloudSuite field equivalents, and flag any custom fields with no matching target for customer decision on whether to carry them forward. Custom field migration happens after base schema validation in the CloudSuite Sandbox.

Info.Net user accounts with role assignments and permission sets map to CloudSuite User records. Roles map to Infor role definitions that we confirm exist in the target CloudSuite configuration. We cannot preserve individual password hashes; users require password resets post-migration. Inactive Info.Net users can be provisioned as inactive Users in CloudSuite for historical record ownership purposes.

Info.Net custom workflow configurations do not migrate as code. We document every active workflow, its trigger conditions, sequence of actions, and routing logic during the discovery phase, and deliver a written inventory with recommended CloudSuite Workflow equivalents for the customer's Infor consultant to rebuild. Workflow dependencies on custom fields are noted in the handoff document so that the rebuild sequence respects the field availability dependency.