Migrate from VISCO to Acumatica

VISCO customer records (name, contact info, address, trade terms) map directly to Acumatica's Customer master. Primary shipping address becomes the default address on the Acumatica Customer. Trade terms (FOB, payment days) migrate as custom fields or note text since Acumatica uses Payment Terms directly.

VISCO vendor master (supplier name, contact, address, lead time) maps to Acumatica's Vendor record. Vendor classification (manufacturer, freight forwarder, customs broker) can map to Acumatica's Vendor Class or stored as a custom field. Primary port of entry migrates as a note.

VISCO inventory items with HS codes, country of origin, and unit-of-measure conversions map to Acumatica Stock Items. Unit of measure sets must be recreated in Acumatica to handle VISCO's multi-UOM purchase vs. sales conversions. Lot/serial tracking settings transfer based on VISCO lot tracking flags.

VISCO's landed cost breakdown (freight, duty, insurance, handling) cannot map to a single Acumatica field. We split each component to a dedicated Cost Layer on the Stock Item and add component-specific custom fields (Freight_Cost__c, Duty_Cost__c) for traceability. Acumatica's landed cost feature requires configuration per item category.

VISCO shipment records (BOL number, vessel name, container count, port of loading, port of discharge) map to Acumatica Purchase Receipts or Transfer Orders depending on whether the shipment is inbound or inter-company. Original shipment date and carrier details preserved as custom fields on the receipt.

VISCO container records (container number, seal number, container type, packing list reference) map to Acumatica Lot/Serial records linked to the Stock Item received. Container-level packing details migrate as lot attributes using Acumatica's custom attribute framework on the Lot/Serial object. This allows your team to track and trace container-specific information within Acumatica's inventory management screens after the migration is complete.

VISCO compliance documents (certificates of origin, bills of lading, customs entries, inspection certificates) re-upload to Acumatica as file attachments on the related Customer, Vendor, or Stock Item record. We preserve the original filename and document date. Acumatica's Files entity supports versioning for document control.

VISCO purchase orders with line items, quantities, landed cost allocations, and scheduled delivery dates map to Acumatica Purchase Orders. Status (open, closed, cancelled) transfers to Acumatica's PO status field. Line-level landed cost breakdowns are stored as custom fields on each PO line, allowing your team to preserve the detailed cost allocation that VISCO captured at the line-item level within Acumatica's purchase order management screens.

VISCO sales orders (customer reference, line items, pricing, requested delivery) map to Acumatica Sales Orders. VISCO pricing rules and discount structures are stored as custom fields since Acumatica's standard price lists handle base pricing but may require additional configuration to replicate VISCO's full trade discount logic across all customer and item combinations.

VISCO's product cost history (landed cost, standard cost, last purchase price) maps to Acumatica's Cost Layers on Stock Items. The cost type (standard, average, FIFO) must be configured in Acumatica based on VISCO's valuation method per item. Cost Effective Date maps to Acumatica's cost layer activation date.

VISCO user accounts resolved by email match against Acumatica users. Unmatched users flagged before migration — teams either create the user in Acumatica first or assign records to a fallback owner. Original VISCO user ID preserved as a custom field on migrated records for audit traceability.

VISCO custom properties that have no direct Acumatica equivalent (trade lane classification, import quota tracking, duty drawback flags) require custom fields in Acumatica. We map these as custom fields on the relevant entity using Acumatica's customization project framework and preserve the data type where possible.