Migrate from VISCO to Infor CloudSuite Corporate

VISCO products carry landed cost allocation fields, unit-of-measure conversions, and product identification metadata (SKU, HS codes, country of origin). We map VISCO item records to Infor CloudSuite MITMMAST (Item Master) and MITBAL (Item Balance) tables via Infor's Migration Utility or direct SQL ingestion where the utility does not cover a VISCO item field. Landed cost allocation percentages and cost category assignments migrate as MITICST cost element records. HS tariff codes map to Infor's Trade Compliance fields if the destination CloudSuite edition includes trade management capabilities.

VISCO Customer records include company details, QuickBooks-linked identifiers, and billing addresses. We map these to Infor CloudSuite OECUSMA (Customer Master) and OECOSHP (Customer Ship-To) tables. QB-linked identifiers are preserved as custom fields on the customer record for reconciliation. Address structures are mapped to Infor's country/state/postal code format with validation against Infor's address format tables.

VISCO Contacts are tied to the CRM module's inquiry workflow. We map VISCO contact records to Infor OEPERMA (Person Master) and link them to the corresponding OECUSMA Customer via the Contact-to-Customer relationship. VISCO's CRM inquiry follow-up data is mapped as OEHISTH (Customer History) activity records in Infor to preserve the relationship trail. Any inquiry records without a matching contact are imported as standalone OEHISTH entries.

VISCO's Landed Cost object holds per-shipment cost allocations across freight, duty, insurance, and brokerage categories. Infor CloudSuite does not have a native landed cost allocation engine equivalent to VISCO's, so we map each VISCO cost category to Infor cost element records (CPRIAMTN or equivalent tables in the destination CloudSuite edition) with the shipment reference preserved. Allocations that cannot be mapped to standard Infor cost elements are documented as manual entry items for the customer's finance team to configure post-migration.

VISCO shipments track containers, ports, carriers, and dates from origin through destination. We map VISCO shipment records to Infor CloudSuite OEORDH (Order Header) with a shipment record type distinction. Container-level data maps to Infor's container and freight handling tables. Port of origin and destination map to Infor's country and port-of-entry tables. Shipment status and tracking state preserve as custom fields or OEHISTH activity records.

VISCO lot records include lot number, warehouse location assignments, expiration date, source shipment reference, and quantity on hand. We map these to Infor CloudSuite MMIBLOT (Lot Master) and MITBAL (Item Balance by lot/location) tables. Warehouse locations map to Infor's warehouse code tables. Expiration dates and lot traceability data migrate with the lot record. For regulated goods (food, chemicals), we flag lot compliance attributes that may require mapping to Infor quality management module fields.

VISCO open and historical sales orders carry customer references, line items, pricing, and landed cost allocations. We export orders in status-based batches (open, closed, historical) and reconstruct the full line item structure in Infor OEORDL (Order Line). Landed cost allocations from VISCO carry forward as cost element lines attached to the order or as MITICST records linked to the ordered items. Customer references resolve via the OECUSMA mapping established before order import.

VISCO purchase orders reference suppliers, products, quantities, and expected landed costs. We map VISCO PO records to Infor PREPOH (PO Header) and PRPOLH (PO Line) tables. Order-to-receipt relationships map to Infor's receiving workflow tables (MHPOREC or equivalent). For partially received purchase orders, we preserve received quantities and open quantities as separate line statuses in Infor's PO structure.

VISCO generates and stores import/export documents including bills of lading, commercial invoices, certificates of origin, and customs forms. Document files and metadata are exported separately from VISCO's database and attached to the corresponding Infor records via Infor Document Management (IDM) or as file attachments on the Shipment/Order/Contact records. Document metadata (type, date, issuing authority) is mapped to IDM index fields for searchable document management.

VISCO's QuickBooks integration handles accounting handoff. Since Infor CloudSuite replaces the accounting layer rather than integrates with it, we flag QuickBooks-specific GL account mappings, QB-linked customer identifiers, and QB invoice references as custom fields on the migrated records for the customer's finance team to reconcile against Infor's GL chart of accounts post-migration.