Migrate from Opto to Infor CloudSuite Corporate

Opto Items (SKU, name, description, unit cost, reorder point) map to Infor CloudSuite Item Master. The Infor Item Master schema varies by edition: CloudSuite Industrial uses Item Master with plant-specific planning data; CloudSuite Distribution uses Item Master with branch and territory associations. We identify the target edition during scoping and map Opto's standard Item fields to the matching Infor table columns. Barcode data from Opto maps to Infor's barcode or GTIN field. Any Opto custom Item fields are extracted to a separate mapping sheet and flagged for Infor OS custom field extension.

Opto Customers (contact name, email, phone, billing address, customer-specific pricing tier) map to Infor CloudSuite Customer records. Infor uses Customer as the AR主体 in some editions and Account in others (particularly CloudSuite Industrial which mirrors ERP-typical Account-Contact models). We map to the correct Infor object based on the target edition during scoping. Customer-specific pricing tiers become Infor price groups or extended price records attached to the Customer.

Opto Vendors (supplier name, contact, payment terms, lead-time data per Item) map directly to Infor CloudSuite Vendor. Vendor lead-time associated with specific Items is preserved by linking the Vendor to the corresponding Item Master after both records are loaded. Payment terms from Opto map to Infor's Terms of Payment code.

Opto Purchase Orders (Vendor reference, Item lines, quantities, expected delivery dates) map to Infor CloudSuite Purchase Order. Infor's PO model includes approval workflows, tax lines, and multi-line structures that Opto does not enforce. Where the target Infor edition uses a Purchase Request pre-stage before Purchase Order, we load Opto POs as Purchase Requests and document the approval chain for the customer's admin to configure post-migration. Open POs migrate as open records; closed POs migrate as historical records.

Opto multi-location inventory with named bins or warehouses maps to Infor CloudSuite's warehouse and location hierarchy. Infor's location model supports multi-level hierarchies (Site > Warehouse > Bin) that Opto does not. We flatten Opto's location names into Infor Location labels and preserve the location code. If Opto uses a bin-level tracking model, we map bins to Infor Locations and document the bin-to-location mapping in the reference table.

Opto Reorder Rules are account-level per-Item configuration (minimum threshold, reorder quantity) rather than transactional records. Infor encodes reorder parameters as fields on the Item Master (Min Qty, Max Qty, Reorder Point) or in the planning module. We export Reorder Rules as a structured CSV reference table with Opto Item ID, reorder threshold, reorder quantity, and preferred vendor. The customer's admin enters these values into Infor Item Master or configures the planning module using the reference table; we do not migrate them as records because they have no direct Infor equivalent.

Opto open and historical A/R invoices map to Infor CloudSuite A/R Invoice records. We separate open invoices from closed history: open items carry forward as open A/R Invoices with original amounts, due dates, and customer references preserved; historical invoices load as posted records. Payment history attaches to each invoice record. Opto invoice line items map to Infor Invoice Detail lines.

Opto A/P invoices map to Infor CloudSuite A/P Voucher records. Vendor references resolve via the Vendor mapping. Unpaid A/P vouchers migrate as open items requiring vendor reconciliation; paid vouchers migrate as historical records. Tax amounts and payment terms carry forward to match Infor's voucher structure.

Opto account-level custom fields on Items have no standard Infor equivalents. We extract the full custom-field schema during discovery, document each field's name, type, and sample values, and provide the Infor OS custom field extension definition for the customer's admin to create post-migration. Custom fields are never silently dropped. We validate the custom-field count against Infor OS limits for the target edition.

Opto account-level custom fields on Customers are extracted as a structured reference table mapped to Infor OS custom field extensions on the Customer object. We provide the field definitions (name, data type, picklist values where applicable) so the customer's Infor admin creates matching fields before production migration. Any customer-specific pricing tiers that Opto stores as custom fields map to Infor price groups.