Migrate your Infor VISUAL data

Work Orders are the primary production record in VISUAL, combining a routing and BOM where materials attach to specific operations. We preserve this structure by mapping Work Order headers, operation sequences, and material allocations 1:1. The WORKORDER_TYPE filter (e.g., 'M' for manufacturing) can be applied during migration scoping.

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 and run times, allowing the destination to reconstruct finite scheduling logic.

VISUAL allows BOM materials to be scattered throughout the routing rather than centralized. We preserve this per-operation attachment during migration, but flag cases where destination BOM structures expect flat single-level or multi-level exploded formats for schema alignment.

Customer Orders drive the order-to-cash cycle in VISUAL. We map order headers, line items, and pricing. EDI-ready formats (CPO transaction set) are preserved where applicable.

Purchase Orders and associated接收 records (Advance Ship Notices) migrate with full header and line detail. ASN EDI 856 data is extracted from VISUAL fixed-length file exports.

Invoices export as EDI 810 fixed-length files or through the Excel export background job. We map header, line, and subline detail, but flag any custom invoice layouts or notes fields that require post-migration reconciliation.

Item master records (SKU, description, unit of measure, cost, revision) migrate cleanly. We flag custom properties and revision-controlled items that may have schema divergence in the destination.

Customer master records including addresses, contacts, credit limits, and EDI trading partner assignments migrate as structured records. We map to destination Account or Customer objects by name and ID cross-reference.

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.

Employee records (HR module) include pay rates, departments, and cost center assignments. Where VISUAL uses effective-dated compensation history, we map the current active record and flag historical records for manual reconciliation if the destination requires snapshot preservation.

Account structure and balances export via the database export tool or Excel. We map GL account codes and descriptions, flagging multi-company or intercompany account segments that may need segment-level mapping in the destination ERP.

Open payables and receivables require careful balance verification during migration. We extract open invoice detail, apply payment status mapping, and flag records where partial payments have been made to ensure the destination opens with correct outstanding balances.

EDI configuration (partner IDs, transaction set preferences, BOL formatting) is tied to customer and vendor records. We extract EDI mappings separately and flag any destination-side EDI reconfiguration needed to maintain trading partner continuity.

Quality management data (inspection results, non-conformance records) may exist in custom tables. We assess the schema and flag whether quality data is migratable or requires post-migration manual re-entry.

Document attachments stored in VISUAL's file management system require a separate file-system extraction step. We do not migrate binary file blobs directly; we document the source file paths and advise on a parallel file migration process.