Migrate from VISCO to Dolibarr ERP

VISCO products carry landed cost allocation fields (freight, duty, insurance, brokerage per unit), unit-of-measure conversions, and product identification metadata. We map these to Dolibarr Product records with the landed cost per unit stored in the CostPrice field at the time of import. Because Dolibarr has no native landed cost recalculation engine, we compute the fully-loaded cost before import and write it as a static value. Product categories map to Dolibarr's Categories system.

VISCO Customer records include company details and QuickBooks-linked fields that have no Dolibarr equivalent. We map to Dolibarr Third Party (type Customer), dropping QB-linked identifiers or storing them in a custom field as a reference note. Customer addresses and shipping locations map to Dolibarr's address fields; multiple shipping addresses in VISCO map to Dolibarr contact addresses under the primary third party.

VISCO CRM contacts map to Dolibarr Contacts linked to the imported Third Party. Email, phone, role, and assignment data migrate directly. The VISCO contact-to-inquiry relationship (which inquiry a contact is assigned to) migrates as a Contact Note or Project Note in Dolibarr referencing the inquiry.

VISCO CRM inquiry records (stored separately from contact records in VISCO) have no direct Dolibarr equivalent. We merge inquiry data into Dolibarr Notes attached to the relevant Contact or Third Party, preserving the inquiry subject, description, assigned contact, status, and follow-up dates. This preserves the relationship trail without creating a separate inquiry object.

VISCO Landed Cost records hold per-shipment cost allocations across freight, duty, insurance, and brokerage categories distributed across product lines. Dolibarr has no Landed Cost object. We split each VISCO Landed Cost record by distributing the cost categories back to the affected product lines, computing a per-unit landed cost for each product at import time, and storing the result in Dolibarr's Product CostPrice. We preserve the original VISCO Landed Cost breakdown as a JSON custom field on each product for audit.

VISCO shipments track containers, ports, carriers, and dates from origin through destination. Dolibarr has no native shipment or container tracking object. We map shipments to Dolibarr Product Lots (using VISCO lot numbers as the Lot field), storing the VISCO shipment reference, carrier, origin port, and destination port as custom fields on the lot record. For multi-container shipments, each container becomes a separate lot.

VISCO lot records carry lot number, expiration date, warehouse location, source shipment reference, and quantity on hand. We map these to Dolibarr Product Lots with the VISCO warehouse assignment stored as the Lot field or a custom lot attribute. Expiration dates migrate to the relevant Dolibarr lot date fields. If the customer uses multiple warehouses, Dolibarr's Warehouse module is enabled and each warehouse is created before lot import.

Open and historical VISCO sales orders carry customer references, line items, pricing, and landed cost allocations. We export orders in status-based batches (open, in-progress, closed) and reconstruct the full line item structure in Dolibarr Customer Order with products resolved by SKU or product reference match. Landed cost allocated to each line item is preserved in the order line price at migration time.

VISCO purchase orders reference suppliers, products, quantities, and expected landed costs. We map to Dolibarr Supplier Order (CommandeFournisseur) with supplier resolved via the imported Third Party. Order-to-receipt relationships in VISCO require mapping to Dolibarr's receiving workflow (if the Stock module is enabled), and any partially-received orders are flagged for the customer to reconcile post-import.

VISCO generates and stores bills of lading, commercial invoices, certificates of origin, and customs forms as document files and metadata. Dolibarr stores files attached to records via its ECM module. We export VISCO document files and attach each to the relevant shipment lot, order, or third-party record in Dolibarr. Document metadata (type, date, issuing authority) is stored in a custom field or in the document note. Note that Dolibarr has no native certificate of origin generator; this requires manual recreation or a third-party module.

VISCO customer and order records carry QuickBooks-linked identifiers from the integration layer. Dolibarr has no QuickBooks integration module in the core package (third-party modules exist on DoliStore). We store QB-linked identifiers as custom reference fields on the relevant Third Party and Order records, flagging them for the customer's admin to reconnect to QuickBooks via a Dolibarr QB module or alternative accounting handoff if needed.

VISCO compliance checklists and alert configurations (FDA, USDA, Customs authority requirements) are feature-configured objects that carry business logic specific to VISCO's event model. These do not map to any Dolibarr object. We document every active checklist and alert configuration in a written inventory with its trigger conditions, assigned contacts, and recommended Dolibarr equivalent (Project tasks, alerts via Dolibarr's Agenda module, or a third-party compliance module). The customer's admin rebuilds these post-migration.