Migrate from VISCO to Epicor Prophet 21

VISCO product records carry landed cost allocation fields, unit-of-measure conversions, and product identification metadata (SKU, HS codes, country of origin). We map these to Epicor Part with PartCost, PartWhse, and PartPlant records. Unit-of-measure conversions in VISCO map to the Epicor UOMClass and UOMConv table. HS tariff codes and country of origin store in Part custom fields or UD columns for trade compliance. Part number becomes the dedupe key; PartClass and PartGroup map to Epicor's commodity and product group structures.

VISCO customer records include company details, ship-to and bill-to addresses, QuickBooks-linked fields, and payment terms. These map to Epicor Customer with CustCnt (contact) and ShipTo records. The QuickBooks-linked identifier stores as a custom field for reconciliation. Customer credit limits and payment terms map to Epicor's Credit Hold and Terms logic. Customer is created before any Order or Quote import so the CustNum reference is satisfied.

VISCO contact records from the CRM module map to Epicor CustCnt records linked to the Customer. VISCO contact assignments for inquiry workflows map as an Epicor custom field or UD column on CustCnt to preserve the assignment relationship. The contact's role (purchasing, logistics, finance) maps to the Epicor RoleCode or a custom picklist field. Primary contact flag migrates directly.

VISCO Land Costs are structured per-shipment allocations across freight, duty, insurance, and brokerage categories assigned per product. Epicor separates these across PartCost (standard and current costs), LandedCost (allocation screens for incoming receipts), and Supply Chain Cost (freight and handling on PO lines). We decompose VISCO's landed cost record into component allocations and map each to the appropriate Epicor cost layer. Allocation percentages from VISCO become Epicor's LandedCost allocation basis (quantity, weight, volume, or value). This is the most complex transformation in the migration and requires a per-category mapping matrix validated during sandbox testing.

VISCO shipments track containers, ports, carriers, dates, and status from origin through destination. For distribution-configured Epicor environments, VISCO shipments map to ShipHead and ShipDtl records. For manufacturing-configured environments with job-based delivery, VISCO shipment status and container data map to Job Traveler notes or a custom Shipment UD table. Container number, vessel name, port of loading, port of discharge, and carrier reference store in ShipHead UD columns or as shipment notes. The customer's Epicor module configuration (distribution vs. manufacturing) is confirmed during scoping.

VISCO lot records include lot number, expiration date, source shipment reference, warehouse location, and quantity on hand. These map to Epicor PartLot with Plant, Warehouse, Bin, LotNumber, LotDescription, ExpirationDate, and MakeOrBuy fields. Source shipment reference stores as a PartLot UD field for traceability. Quantity on hand per lot per warehouse creates PartBin records with allocated and unallocated quantities. For regulated industries (food, chemical), the FDA or USDA compliance attributes (lot age, quarantine status) map to Epicor PartLot custom fields.

VISCO sales orders carry customer references, line items, pricing, quantity, and landed cost allocations. We map OrderHed (order header with Customer, PO number, terms, ship date) and OrderDtl (order lines with Part, quantity, unit price, discount). Landed cost allocations from VISCO lines migrate as OrderDtl custom fields or UD columns, not as native Epicor landed cost records (which apply at receipt, not order). Open orders and historical orders migrate in separate batches; closed orders migrate as historical records without workflow triggers.

VISCO purchase orders reference suppliers, products, quantities, expected landed costs, and order-to-receipt relationships. POHeader maps to supplier, terms, and FOB; PODetail maps to the line items with PartNum, Quantity, UnitCost, and landed cost allocation. The expected landed cost fields from VISCO map to PODetail UD columns since Epicor's native landed cost screen applies at receiving. PODetail lines link to Receipt records after goods receipt, which we reconcile during the receiving-phase migration.

VISCO generates and stores bills of lading, commercial invoices, certificates of origin, and customs forms. Document files and metadata are exported separately and associated with the corresponding VISCO shipment, customer, or supplier record. We map document metadata (type, date, reference number) to Epicor EDM Document Management with links to Shipment or Customer via the DocumentReference table. The actual document files (PDFs, images) migrate as binary blobs attached to the Epicor document record.

VISCO's CRM module stores customer inquiries separately from contact records, with inquiry status, assigned user, and follow-up history. We map VISCO inquiry records to Epicor Case (Service Track) if the customer licenses the Service module, or to Task records attached to the Contact if Service is not licensed. Inquiry status maps to Case Status or Task Status; assigned user maps to the Epicor User by email match; follow-up history becomes sub-Task or Case Activities. The inquiry-contact relationship is preserved by linking to the migrated CustCnt record.

VISCO warehouse location assignments on lot records map to Epicor's Plant, Warehouse, and Bin hierarchy. Each VISCO warehouse location becomes a combination of Epicor Plant (or site), Warehouse code, and Bin number. Multi-warehouse configurations require separate Plant records in Epicor if the sites have distinct inventory parks or costing profiles.

VISCO supplier records referenced on purchase orders map to Epicor Supplier with SupplierID, Name, PaymentTerms, ShipVia, and address records. Supplier country and currency map to Epicor's supplier payment and currency defaults. Supplier lead times map to PartVend records for MRP scheduling.

VISCO carrier references on shipment records map to Epicor Carrier with CarrierID, Description, and shipping mode. Carrier SCAC codes and freight terms map to Carrier freight class and terms fields. Carrier is referenced on ShipHead and POHeader records.

VISCO stores port of loading, port of discharge, country of origin, and destination country as shipment attributes. Epicor does not have a native ports-of-trade table. We map these to a UD table (UD01 or equivalent) linked to the Shipment record, or as ShipHead custom fields if the customer's Epicor environment has pre-configured port fields. The customer confirms the preferred approach during scoping.

VISCO's automatic container tracking alerts and compliance checklist configurations are user-defined rules that do not have a direct Epicor equivalent. We extract every active alert and checklist configuration from VISCO (trigger condition, recipient, message template, frequency) and deliver them as a written inventory document for the customer's admin to rebuild in Epicor using BPMs, alerts, or the Kinetic Workflow Designer. This is not a data migration deliverable; it is a configuration handoff.