Migrate from Opto to Microsoft Dynamics 365 Business Central

Opto Items map to Dynamics 365 Item records. We map Item number to Item No., description to Description, SKU to the destination's cross-reference or barcode field, unit cost to Unit Cost, and reorder point to Reorder Point. Barcode associations stored on the Item record migrate as a structured custom field barcode_id__c or as a cross-reference record in Business Central. If Opto Items carry variant attributes (size, color), these map to Item Variants in Business Central or as product dimensions in Finance and Supply Chain Management.

Opto multi-location inventory with named bins and warehouses flattens into the destination's warehouse-location model. We extract the Opto location hierarchy (warehouse, zone, bin) and map it to Business Central Warehouse code plus Location code, or to Finance and Supply Chain Management Site plus Warehouse. The top-level Opto warehouse name becomes the destination Warehouse name; lower-level bin names become Location codes with a naming convention agreed during scoping. Inventory quantities per location are preserved as bin-level stock entries in the destination.

Opto Vendor records map directly to Dynamics 365 Vendor. We map vendor name to Name, contact to Contact, phone and email to Contact Information, payment terms to Payment Terms, and any lead-time data stored on the Vendor to the Vendor Lead Time field or a custom field on the Vendor. Vendors are inserted before Purchase Orders so that the Vendor No. reference is satisfied at the time of PO import.

Opto Customer records map to Dynamics 365 Customer. We map customer name to Name, billing address to Address, email to Email, phone to Phone, and any customer-specific pricing tiers to Customer Price Group or a custom pricing field. If Opto Customers carry a credit limit or payment term override, these map to Credit Limit and Payment Terms on the Dynamics 365 Customer record. Customer is inserted before any Sales Orders or invoices that reference it.

Opto Purchase Orders link a Vendor to one or more Items with quantities and expected delivery dates. We map the Vendor reference, Item references (resolved to Dynamics 365 Item No.), quantities, unit cost, and expected receipt date. In Business Central, Purchase Orders are inserted directly. In Finance and Supply Chain Management, open Purchase Orders can map to Purchase Requisitions if the organization's approval workflow routes requisitions before PO creation. We confirm the preferred object during scoping based on the customer's approval process.

Opto Reorder Rules are account-level configuration per Item, not transactional records. We export the full rule set as a structured CSV during discovery, documenting each Item's minimum quantity threshold, reorder quantity, and preferred vendor. These rules must be re-entered manually at the destination in Business Central's Reorder Point field and Planning Worksheet, or in Finance and Supply Chain Management's Master Planning parameters. We include a complete Reorder Rule reference worksheet in the mapping document to make manual reconfiguration straightforward and auditable.

Opto open and historical invoices separate into two migration batches. Open invoices are recreated in Dynamics 365 as open records (Sales Invoice in Business Central, Customer Invoice Journal line in Finance and Supply Chain Management) with line items, amounts, due dates, and payment status preserved. Closed invoices migrate as historical posted records with full line-item detail for audit and financial reporting. The Opto invoice number becomes the External Document No. on the Dynamics 365 record for cross-reference.

Opto AP invoices map to Dynamics 365 Purchase Invoice records. We preserve vendor reference, invoice number, invoice date, due date, amounts, and line items. Open AP items migrate as open invoices so that the accounts payable team can make payments against the correct vendor ledger entries. Closed AP invoices migrate as posted records for historical reporting and audit trail.

Opto barcode-to-Item associations are extracted as a structured reference table and mapped to Business Central Item Cross-Reference records (with Cross-Reference Type set to Bar Code) or to a custom barcode_id__c field on the Item. In Finance and Supply Chain Management, barcode associations map to a WHSBarcodeTable extension or a custom field on the released product. We document the barcode symbology and any scan-logic customizations for the customer's IT team to evaluate the best Dynamics 365 barcode implementation path.

Opto Item custom fields are extracted during discovery with their data types and populated values. We map each to a matching Dynamics 365 user-defined field (Business Central) or an extension field (Finance and Supply Chain Management). Fields with no direct equivalent are flagged in the mapping worksheet with a recommendation (custom field, notes field, or drop as non-operational). No custom field is silently dropped; every field appears in the mapping document with a disposition decision.

Opto Customer custom fields follow the same approach as Item custom fields. We extract the schema during discovery, map to equivalent Dynamics 365 user-defined or extension fields, and document any unmapped fields with a disposition recommendation. Customer-specific pricing tiers, discount schedules, or regional flags migrate to the appropriate Dynamics 365 Customer fields or custom fields.

Opto does not expose its chart of accounts structure directly, but the customer's accounts receivable and accounts payable balances must reconcile post-migration. We extract AP and AR subledger balances from Opto's invoice records and cross-reference them against the destination's control accounts. We deliver a chart-of-accounts mapping worksheet that the customer's accountant completes for any Opto expense and revenue accounts, then validate that total debits equal total credits in the destination general ledger before go-live.