Migrate from Opto to Odoo ERP

Opto Items map to Odoo Product records. The Item SKU becomes product.default_code; Item name becomes product.name; unit cost becomes product.standard_price; reorder point becomes Odoo product.rule_min_qty if the destination uses Odoo's procurement rules. We extract any barcode associated with the Item and write it to product.barcode. Custom fields on Item are mapped to Odoo custom fields created via Odoo Studio before migration.

Opto Vendors map to Odoo Contact records with the delivery address role. Vendor name becomes res.partner.name; payment terms stored in Odoo property_payment_term_id on the partner. We preserve any configured lead time from the Opto Vendor as vendor_lead_days on the Odoo Contact for use in Odoo procurement rules.

Opto Customers map to Odoo Contact records with the contact type. Name, email, phone, and billing address transfer directly. Customer-specific pricing tiers from Opto map to Odoo pricelist records attached to the Customer contact. We handle one-to-many addresses per customer by creating a primary billing address on the Contact record and any secondary delivery addresses as separate Contact records linked via type.

Open Purchase Orders from Opto migrate to Odoo purchase.order records in draft state. Vendor lookup resolves via the Contact mapping; line items resolve via the Product mapping. Expected delivery date from Opto becomes date_planned on the Odoo purchase.order.line. Closed or historical Purchase Orders migrate as read-only records in Odoo for audit trail purposes. We separate open from closed POs during extraction so that open POs can be re-entered as live Odoo POs while historical ones are imported as locked records.

Opto multi-location inventory maps to Odoo's warehouse and location hierarchy. Each Opto named location or bin becomes an Odoo stock.location record under the configured warehouse's view locations. If Opto uses a flat location model, we preserve the location name as location.complete_name in Odoo. Location-specific quantity balances transfer as Odoo stock.quant records that set initial inventory levels at go-live. Odoo requires locations to be configured before quant import so we sequence location creation before stock.quant migration.

Opto Reorder Rules are account-level configuration data per Item, not transactional records. We export them as a structured CSV with Item SKU, minimum quantity, reorder quantity, and preferred vendor. In Odoo, these map to product.template route rules (procurement rule with Buy or Manufacture route) and to product.template.rule_min_qty for the reorder threshold. Manual reconfiguration in Odoo is required because the Opto reorder logic involves account-level thresholds that do not map automatically to Odoo's rule engine. We deliver the full reorder rule table in the mapping worksheet to guide manual Odoo configuration.

Open and historical Opto customer invoices map to Odoo account.move records with move_type = out_invoice. Line items with Item references resolve to Odoo Product. Paid invoices migrate with state = posted and payment_state = paid; open invoices migrate as draft or posted with a matching open amount on the Odoo partner account. Historical invoice PDFs do not migrate as Odoo attachments; we deliver them as a zipped document archive for manual attachment post-migration.

Opto vendor invoices map to Odoo account.move records with move_type = in_invoice. Vendor lookup resolves via the Contact mapping. Open AP invoices are migrated as posted or draft records matching the open balance; closed AP invoices are migrated as posted with payment_state = paid. Odoo's account.move requires a journal and an account.code for each line item, so we map Opto expense categories to Odoo account codes during the chart of accounts discovery phase.

Opto Items may carry custom fields specific to the account. We extract the full custom-field schema during discovery, create matching custom fields on Odoo product.template via Odoo Studio, and map values during the product import phase. Fields with no Odoo equivalent are flagged in the mapping worksheet for the customer to evaluate whether they remain relevant in Odoo's data model. Custom fields are never silently dropped.

Opto Customer records may include custom fields such as customer tier, tax exemption flag, or internal account codes. We extract these during discovery, create matching custom fields on Odoo res.partner via Odoo Studio, and map values during the contact import phase. Any customer-specific pricing tier from Opto maps to an Odoo pricelist attached to the partner record rather than a custom field.