Migrate from Opto to Acumatica

Opto item records map directly to Acumatica's InventoryItem DAC. InventoryCD serves as the keyed identifier equivalent to Opto's item code. ItemClass must be selected in Acumatica — FlitStack creates a default class during schema setup if none exists, so the item can save without blocking PO/SO lines.

Opto customer records split into two Acumatica records: a Customer (BAccountID-based) and a Contact subrecord. The primary contact name, email, and phone migrate to the Contact DAC linked by ContactID. Acumatica requires a CustomerClass on the Customer record — FlitStack maps Opto's customer type to the nearest Acumatica class or creates a default.

Mirrors the customer pattern: Opto vendors become Acumatica Vendor records (BAccountID-based) with an associated Contact for the primary AP contact. VendorClass is mandatory in Acumatica and is derived from Opto's vendor type or created as a default. AP workflows in Acumatica use VendorClass to route approvals.

Opto PO headers map to POOrder; PO lines map to POLine. The POOrder.VendorID references the migrated Vendor record — all vendors must be committed before PO records can land. POLine.InventoryID references the migrated InventoryItem; all inventory items must be present before PO lines validate.

Opto SO headers map to SOOrder; lines map to SOLine. SOOrder.CustomerID requires the Customer record to exist first. SOLine.InventoryID requires the InventoryItem to exist. UOM on each SOLine must be specified — FlitStack derives the item's default selling UOM from Opto's UOM field.

Opto's warehouse or bin-location assignment per item maps to Acumatica Warehouse records and ItemWarehouse (availability) rows. Each ItemWarehouse record is scoped by Branch. If Opto tracks multiple stocking locations, FlitStack creates corresponding Warehouse records in Acumatica and populates on-hand quantities per location.

Opto general ledger accounts migrate as Acumatica Account records with the same account code. Account type (Asset, Liability, Revenue, Expense) maps to the Acumatica Account type pick-list. Active flag and posting settings are preserved. Branches are assigned to accounts during Acumatica's chart-of-accounts setup.

Opto UOM definitions (each, box, case, etc.) map to Acumatica's UOM table. Conversion factors between UOMs are preserved if Opto stores them. When Acumatica's POLine or SOLine references a UOM, the UOM must exist in the UOM table first — FlitStack loads UOMs as a first-stage entity before any line records.

Opto custom fields and extended attributes that have no native Acumatica equivalent are migrated as user-defined fields prefixed USR. These require a published Acumatica customization project before data loads — FlitStack generates the customization project XML as part of the migration plan so your Acumatica admin can deploy it before the data run.

Opto receipt-of-goods records map to Acumatica APReceipt (AP bill or receipt) with lines linked to POLine and InventoryItem. APReceipt.VendorID and APReceipt.POOrderNbr are populated from the migrated PO and vendor records. Receipt date and quantity are preserved as the original Opto transaction date and received quantity.

Opto AR invoices map to Acumatica ARInvoice (or ARInvoice with SO invoice reference). CustomerID references the migrated Customer. Line items link to InventoryItem where applicable. Payment terms and due dates are preserved from Opto's invoice date and terms field. Original invoice number is stored in ARInvoice.ExtRefNbr for traceability.