Migrate from VISCO to Microsoft Dynamics 365 Business Central

VISCO products carry landed cost allocation fields, unit-of-measure conversions, and product identification metadata including hs_sku equivalents and country-of-origin. We map these to Dynamics 365 Item records with Standard Cost and landed cost model assignments. If VISCO tracks items by landed cost per unit, we set the items Costing version to capture the all-in cost (product cost plus allocated freight, duty, insurance, and brokerage). Unit-of-measure conversions migrate as UOM class definitions in the destination system.

VISCO Customer records include company details, payment terms, QuickBooks-linked identifiers, and shipment address data. We map these to Dynamics 365 Customer records with Customer Posting Group and Payment Terms assignments. Any QuickBooks-linked identifiers are preserved as custom properties for reconciliation reference. Customer addresses migrate as address records with the appropriate address purpose (Invoice, Delivery) assigned per D365's address role model.

VISCO Contacts from the integrated CRM module include name, email, phone, company association, and owner assignment. We map these to Dynamics 365 Contact records linked to the corresponding Customer. Contact's Owner field maps to the resolved Dynamics 365 User by email match. Any VISCO CRM inquiry history attached to the contact migrates as Activity records (Phone Calls, Tasks) linked to the Contact for the activity timeline audit trail.

VISCO's Landed Costs object holds per-shipment cost allocations across freight, duty, insurance, and brokerage categories. Dynamics 365 Finance and Supply Chain Management provides a Landed Cost feature with Landed Cost Models, Charge Codes, and Affected Items assignments. We reconstruct each VISCO landed cost record as a Landed Cost Model with line allocations mapped to the equivalent Charge Code (Freight, Duty, Insurance, Brokerage) and the items affected mapped as Product Costing version entries. Business Central requires the Landed Cost feature enabled separately; we configure this during the migration window.

VISCO shipments track containers, ports, carriers, expected and actual arrival dates, and shipment status from origin through destination. We map these to Dynamics 365 Warehouse Management Inbound Shipment records or generic shipment records depending on whether the destination uses the Advanced Warehousing module. Container-level data (container number, seal number, container type) migrates as custom fields or as warehouse shipment line attributes. Shipment status preserves the state transition history as a custom field or linked activity log.

VISCO inventory lots carry lot number, expiration date, source shipment reference, warehouse location assignment, and quantity on hand. We map these to Dynamics 365 Item Tracking with Lot Number records, including ExpirationDate, the originating Inbound Shipment reference, and Warehouse location. The lot-to-location assignment preserves the audit trail required by FDA, USDA, and Customs compliance for food, chemical, and consumer goods companies. We flag any lots with expired or near-expiration dates for the customer's inventory team to review before go-live.

VISCO Sales Orders carry customer reference, line items with quantities and pricing, landed cost allocations, and order status. We export orders in status-based batches (Open, Completed, Invoiced) and reconstruct the full line item structure in Microsoft Dynamics 365 Sales Order lines. Landed cost allocations attached to sales order lines migrate as landed cost postings on the order or as cost percentage fields on the product cost record for post-invoice allocation.

VISCO Purchase Orders reference suppliers, products, quantities, expected landed costs, and order-to-receipt relationships. We map these to Dynamics 365 Purchase Orders with supplier resolution by name or vendor number, line items mapped to Items, and the expected landed cost carried as a note or landed cost line on the order. For partially received purchase orders, we preserve receipt progress for reconciliation in the receiving workflow.

VISCO generates and stores import/export documents including bills of lading, commercial invoices, certificates of origin, and customs forms. Document files and metadata export separately from the document management system. We attach these files to the corresponding records in Dynamics 365 using the Document Handling or SharePoint integration, linking each file to the related Shipment, Purchase Order, Sales Order, or Customer record. We flag any custom document templates for the customer's admin to rebuild as Word templates or SSRS reports in Dynamics 365.

VISCO customers commonly use QuickBooks for accounting alongside VISCO for trade operations. If the migration includes QuickBooks data (invoices, payments, chart of accounts), we map these to Dynamics 365 Finance General Journal Entries or chart of account records. If only VISCO data is in scope, we flag the QuickBooks integration dependencies for the customer's admin to decommission or reconnect to Dynamics 365 via the QuickBooks Sync or a third-party integration from AppSource.

VISCO's automatic container tracking and document alert configurations do not migrate as automation code. We deliver a written inventory of every active alert and checklist configuration in VISCO with its trigger conditions, notification recipients, and recommended Alert Rule equivalent in Dynamics 365. The customer's admin rebuilds these in the Alert functionality or via Power Automate flows. Compliance checklist logic for FDA, USDA, and Customs is documented separately for the customer's compliance team to configure as workflow stages in the receiving process.

VISCO's CRM module stores customer inquiry follow-up data separately from standard contact records. Inquiry records with subject, description, assigned owner, status, and resolution date migrate as Dynamics 365 Activity records (Task or Phone Call) linked to the corresponding Contact. The inquiry assignment and status transition history preserves the relationship trail in the contact's activity timeline. We flag any open inquiries for the customer's CRM admin to review and reassign post-migration.