Migrate from Infor VISUAL to Infor CloudSuite Corporate

Work Order headers map directly to CloudSuite Work Order. VISUAL sequences materials to operations so that components release only when the downstream operation requires them, and CloudSuite preserves this scheduling model. We map Work Order header fields (order number, status, priority, scheduled dates) and operation details including operation sequence, work center, and resource assignments. Work Order number becomes the primary dedupe key; we verify against existing CloudSuite Work Order numbers during import to prevent collisions.

Routings define the sequence of operations and the resources (labor, machine, work center) each step requires. We map routing headers and operation details including setup time, run time, queue time, and move time. CloudSuite Work Order Operations inherit the routing operation sequence, and we preserve the operation-to-work-center linkage from VISUAL. Routing revision control transfers as the current active revision with historical revisions flagged for manual review.

VISUAL allows BOM materials to be scattered throughout the routing rather than stored as a centralized structure. We reconstruct the operation-to-material linkage by joining on the Work Order header and operation sequence number, then write materials back to their correct operation step in CloudSuite. This is the highest-risk mapping in the migration because a flat BOM export silently breaks material release scheduling. Multi-level BOMs require recursive explosion before transformation, and we flag any destination BOM structures that diverge from VISUAL's per-operation attachment model.

Customer Orders drive the order-to-cash cycle in VISUAL. We map order headers, line items, pricing, and scheduled ship dates. EDI-ready formats (ANSI X12 850 transaction set) are preserved where applicable. Order status (open, partial, completed, cancelled) maps to CloudSuite Sales Order status with balance quantities recalculated against shipped and invoiced totals during migration.

Purchase Orders and associated ASN records migrate with full header and line detail. VISUAL's EDI 856 Advance Ship Notice data extracts from fixed-length file exports and maps to CloudSuite ASN records linked to the Purchase Order. Line-level promised dates, quantity ordered, and quantity received transfer, with open receipts flagged for post-migration follow-up against the destination's receiving module.

VISUAL invoices export as EDI 810 fixed-length files or through the Excel export background job. We map invoice header (invoice number, date, terms, customer), line detail (item, quantity, unit price, extended price), and subline detail (discounts, taxes, freight). Custom invoice layouts or notes fields that reference VISUAL-specific formatting require post-migration manual re-entry or a CloudSuite invoice template rebuild.

Item master records (SKU, description, unit of measure, cost, revision level, planner code, buying settings) migrate cleanly with direct field mapping. VISUAL revision-controlled items require CloudSuite item revision setup before import so that the revision chain is not broken. Custom properties and user-defined fields on Items map to CloudSuite Item UDFs or auxiliary fields based on data type.

Customer master records including addresses, contacts, credit limits, and payment terms map directly to CloudSuite Customer. EDI trading partner assignments are not in the customer master table itself; they require a separate EDI configuration extraction (see gotcha on EDI storage). Customer number becomes the dedupe key; we cross-reference by customer number and flag duplicate names for reconciliation before import.

Vendor master records including addresses, payment terms, and EDI configuration migrate as vendor records. We cross-reference by vendor number and flag duplicate vendor names that may cause import collisions. Vendor EDI configuration (separate from vendor master) requires a dedicated extraction step to prevent silent loss of trading partner setup.

Employee records (HR module) include pay rates, departments, cost center assignments, and supervisor relationships. VISUAL's effective-dated compensation history requires mapping of the current active record with historical rates flagged for manual review. CloudSuite Employee must be provisioned before any Work Order or Purchase Order import because labor routing operations reference the employee as the primary resource.

Account structure and balances export via the VISUAL database export tool or Excel. We map GL account codes and descriptions, flagging multi-company or intercompany account segments that require segment-level mapping in CloudSuite. Beginning account balances migrate as opening balances with post-migration period verification against VISUAL's trial balance.

Open payables and receivables require careful balance verification during migration. We extract open invoice detail (invoice number, vendor/customer, date, due date, amount open, amount paid, discount taken) and apply payment status mapping. Records where partial payments have been made require allocation tracking preserved in CloudSuite payment application records. We reconcile total open AP and AR balances against VISUAL's aged trial balance before declaring migration complete for financial data.