Migrate from VISCO to Odoo ERP

VISCO products carry landed cost allocation fields, unit-of-measure conversions, and product identification metadata. We map VISCO product fields to Odoo Product Template (the product definition) and generate Product Variants for each unit-of-measure or country-of-origin combination. Landed cost values from VISCO transfer as the initial Standard Price on the product; Odoo recalculates average or FIFO cost as receipts are posted through the Purchase module. SKU mapping preserves the VISCO item code as the product's default_code field for cross-system reconciliation.

VISCO's Land Costs object holds per-shipment cost allocations across freight, duty, insurance, and brokerage categories. Odoo does not have a native landed cost allocation object at the same level of granularity; instead, it tracks valuation layers per product (Quantity on Hand, Virtual on Hand, IN Draft, OUT Draft) and calculates average cost. We map each VISCO landed cost category to a separate Journal Entry in Odoo Inventory Valuation, and reconstruct the total allocated cost as an initial stock valuation adjustment so that on-hand inventory reflects the fully-loaded landed cost before the first Odoo receipt is posted.

VISCO shipments track containers, ports, carriers, and dates from origin through destination. We map VISCO shipments to Odoo Receipts (Incoming Shipments under Inventory) linked to the related Purchase Order. Container numbers, carrier references, and port data migrate as custom fields on the Odoo picking record. Shipment status (in transit, customs clearance, delivered) maps to Odoo's picking state (waiting, confirmed, assigned, done) with a custom status field for customs-specific states that Odoo does not natively model.

VISCO tracks inventory by lot number with warehouse location assignments, expiration dates, source shipment reference, and quantity on hand. We map VISCO lots to Odoo Lots under the lot/serial number tracking feature. The warehouse location assignment maps to Odoo's location_id on the Stock Quant record. Expiration dates migrate as use_date fields on the lot. Source shipment reference maps as a custom lot property so that lot genealogy is traceable back to the original VISCO shipment record.

VISCO customers include company details and QuickBooks-linked fields. We map to Odoo res.partner with customer=True and supplier=False. The QuickBooks-linked identifier from VISCO migrates as a custom field qb_ref for cross-system reconciliation. Customer-specific landed cost or pricing rules in VISCO map to Odoo's Pricelist rules on the partner record.

VISCO's CRM module stores contact details and inquiry assignments. We map VISCO contacts to Odoo res.partner with contact=True, linked as child addresses of the parent Customer record. The CRM inquiry-to-contact relationship is preserved by creating activity records (mail.message) on the contact in Odoo's native activity timeline. Phone, email, and address fields map directly; inquiry subject and status migrate as custom fields if the customer requires visibility into the original inquiry context.

VISCO's inquiry module stores follow-up records separately from contact records. Each inquiry record maps to a Task activity on the related Contact in Odoo. The inquiry subject becomes the Task name, inquiry status becomes Task stage, and follow-up notes migrate as Task description. The inquiry creation date and last modified date become the Task's date_deadline and activity_date_deadline respectively, preserving the activity timeline order for audit purposes.

VISCO sales orders carry customer references, line items, pricing, and landed cost allocations. We map open and historical sales orders to Odoo sale.order. Line items map with product reference, quantity, and price. Landed cost allocations on the VISCO order (freight, duty, insurance) do not natively replicate in the Odoo sale.order line; we document these as custom fields on the order and the customer decides whether to embed them in the product price or carry them as separate cost lines in the Purchase workflow.

VISCO purchase orders reference suppliers, products, quantities, and expected landed costs. We map open purchase orders to Odoo purchase.order with supplier address, line items, and expected dates. Landed cost categories from VISCO (freight, duty, insurance, brokerage) migrate as custom order-level fields for later allocation against the related incoming shipment.

VISCO generates and stores import/export documents including bills of lading, commercial invoices, certificates of origin, and customs forms. Document files export as binary blobs and attach in Odoo as ir.attachment records linked to the related Shipment (Incoming Shipment), Purchase Order, or Inventory Lot. Document metadata (type, issue date, authority) migrates as custom fields on the attachment record so that compliance teams can search and filter documents within Odoo without navigating to a separate system.

VISCO suppliers map to Odoo res.partner with supplier=True. Supplier-specific landed cost terms, payment terms, and carrier preferences from VISCO map to Odoo's vendor Pricelists, Fiscal Position (for tax mapping on imports), and Carrier configuration on the purchase workflow.

VISCO warehouse locations map to Odoo Warehouse records and the internal location hierarchy (view location, internal location, partner location). Each VISCO warehouse with lot-tracking enabled generates a corresponding Stock Location in Odoo. Multi-warehouse configurations in VISCO map to multiple Odoo Warehouse records under a single Odoo instance or a multi-company Odoo setup depending on the customer's organizational structure.