Migrate from Infor VISUAL to Microsoft Dynamics 365 Business Central

VISUAL Work Order headers map to Dynamics 365 Production Order records. The Work Order number, description, scheduled start and end dates, priority, and status migrate as typed fields. We resolve the Work Order type to a corresponding Production Order type in Finance and Operations or a Manufacturing setup in Business Central. Closed and historical Work Orders migrate as completed production orders with actual cost and actual dates populated from VISUAL's actual costing records.

VISUAL Routing definitions map to Dynamics 365 Route records. Each operation sequence, work center reference, setup time, run time, and queue time migrate as typed Route operations. We preserve the operation sequence order and link each operation to the correct Work Center or Machine Center in Business Central, or to the Operations resource group in Finance and Operations. Resource skill and proficiency requirements on the routing map to Route requirement records in the destination.

VISUAL BOM materials are scattered across routing operations rather than stored as a flat single-level or multi-level structure. We reconstruct the BOM by joining on Work Order header and operation sequence number to build the operation-material linkage, then write the BOM items back to their correct operation step in the destination. Where VISUAL uses multi-level BOMs with phantom assemblies, we flatten or preserve the hierarchy based on the destination's BOM explosion settings. Any BOM items without a routing operation attachment are flagged as orphans for customer review.

VISUAL Item records (SKU, description, unit of measure, cost, revision) map to Released Products in Finance and Operations or Items in Business Central. Item type (stocked, service, BOM, planning) maps to the corresponding Product type. Revision-controlled items from VISUAL become versioned items in Dynamics 365 with effective date ranges. Custom properties on the VISUAL item record map to extension fields on the destination item.

VISUAL Customer Orders drive the order-to-cash cycle and map to Microsoft Dynamics 365 Sales Orders. Order headers, line items, quantities, pricing, and discount structures migrate as typed fields. Open orders migrate with full detail; completed orders migrate as closed historical records. We resolve Customer Order number to Sales Order number and map the VISUAL order status to the corresponding Dynamics 365 status. EDI-ready CPO transaction set data from VISUAL is preserved in a custom field if the customer maintains EDI-based order processing.

VISUAL Purchase Orders and associated ASNs migrate with full header and line detail. Line items, quantities, prices, delivery dates, and vendor references map to typed Purchase Order fields. ASN EDI 856 data extracted from VISUAL fixed-length file exports maps to Dynamics 365 Shipment notice records or a custom ASN entity. Open POs migrate as active records; closed POs migrate as historical records with receipt and invoice matching preserved.

VISUAL invoices export as EDI 810 fixed-length files or through the Excel export background job. We map header, line, and subline detail including invoice number, date, customer reference, amounts, and tax codes. Custom invoice layouts and notes fields are flagged for post-migration layout rebuild in Dynamics 365 Report Designer or SSRS. Historical invoices migrate as posted records; open invoices migrate as pending.

VISUAL Customer master records including addresses, contacts, credit limits, and payment terms migrate as Customer records. We map to the destination Customer by customer number and address structure. EDI trading partner assignments stored in VISUAL's linked configuration tables are extracted separately and mapped to the destination's EDI trading partner or electronic document settings. Address roles (invoice, delivery, primary) map to Dynamics 365 address purpose fields.

VISUAL 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 for customer resolution. EDI configuration on vendors is extracted as a separate configuration plane and mapped to the destination's vendor EDI or electronic document settings. Payment terms and hold status migrate as typed fields.

VISUAL GL account codes and descriptions export via database export tool or Excel. We map account numbers and descriptions and flag multi-company or intercompany account segments that require segment-level configuration in Dynamics 365. Account balances for open and closed periods migrate as part of the financial migration scope. The account structure (numbering format, segment count, segment delimiters) is preserved as a configuration deliverable.

Open payables and receivables require careful balance verification during migration. We extract open invoice detail including invoice number, date, due date, outstanding amount, partial payment status, and payment application history. We apply payment status mapping and flag records where partial payments have been made so that the remaining balance and payment application are both reflected in the destination. Balance totals are reconciled against VISUAL trial balance before and after load.

VISUAL Employee records from the HR module include pay rates, departments, and cost center assignments. We map current active employee records to the destination Worker or Employee entity. Where VISUAL uses effective-dated compensation history, we map the current active record and flag historical compensation records for manual entry or a separate HR migration engagement. Cost center and department assignments map to the destination's organizational hierarchy.

Quality management data in VISUAL (inspection results, non-conformance records) may exist in custom tables or quality module records. We assess the source schema during discovery and flag whether quality data is migratable or requires post-migration manual re-entry. When migratable, we map inspection types, sampling plans, and non-conformance codes to the corresponding quality entities in Finance and Operations.

VISUAL EDI trading partner preferences (partner ID, transaction set version, BOL formatting) are stored in configuration records linked to customer and vendor records, not in the customer or vendor master tables. We run a dedicated EDI configuration extraction and map each partner's settings to the destination's trading partner records. We flag any destination-side EDI configuration that requires manual setup, particularly for AS2, OFTP, or REST-based EDI integrations.