Migrate from Opera 3 to monday CRM

Opera 3's Sales Ledger contact exports map to Monday.com Contacts. We extract name, email, phone, address, payment terms, credit limit, and multi-currency settings from the CSV export. Opera 3's contact code becomes the Monday.com Contact ID column for dedupe verification. Any OPUS add-on customer-specific product variants attached to a contact are noted in a separate text column because Monday.com does not have a native customer-product variant schema.

Opera 3 company records (from the CRM module, distinct from the Nominal Ledger legal entity codes) map to Monday.com Organizations. We extract company name, address, industry classification, and any contact links. Opera 3's multi-company legal entity codes require a decision during scoping: they can map to separate Monday.com Organizations (one per entity) or be grouped under a single parent Organization using the Group feature, depending on whether the customer wants consolidated or separated deal tracking.

Opera 3 Sales Order headers and line items map to Monday.com Deals. We extract order number, customer reference, order value, order date, and status flags. Line items map to Deal items or sub-items depending on whether the customer wants per-line deal tracking or a single deal with a total value. Discounts, delivery addresses, and payment terms from the order header carry forward as custom columns on the Deal board.

Opera 3 invoices split into two Monday.com record types: Deals with a Closed status capture the commercial relationship (account, value, date, customer PO reference), while invoice PDF attachments migrate as file columns on the Deal item. Credit notes receive the same treatment with a Credit Note type tag. Opera 3 enforces invoice-total-to-line-sum reconciliation during export, so we validate this constraint before loading into Monday.com. Historical invoices without a linked order are created as standalone closed Deals.

Opera 3 CRM activity logs are text-based note entries (calls logged, emails sent, meetings held) with timestamps and owner references. We parse the CSV activity export, map each entry to a Monday.com Activity entry with the activity type, body text, date, and person linked. Note that Opera 3 activities are plain text with no structured subtype field; we infer the activity type from the notes header or subject line pattern and map to the closest Monday.com Activity type (Call, Email, Meeting, or Note). Historical timestamps are preserved in the Activity date column.

Opera 3 employee records (exported via CSV) map to Monday.com Contacts with an Employee type tag, or to Work Items on a People board if the customer wants to track internal team members alongside external contacts. Bank details, start/end dates, and P45 data do not migrate unless the destination is a dedicated HR system; we flag these fields during discovery as data that should remain in Opera 3 or be handed to the customer's payroll provider. RTI FPS XML employee payment summaries are mapped to a structured text column rather than native payroll fields since Monday.com has no payroll schema.

Opera 3 stock codes, descriptions, bin locations, reorder levels, and BOM structures map to Monday.com Products (if the customer uses Monday.com Sales CRM or a product-tracking board). Stock valuation and cost price fields migrate as custom number columns. Customer-specific product variants from the OPUS add-on (stock code plus customer reference) require a separate mapping to a customer-product board or to a custom column on the main Products board, as Monday.com has no native customer-variant schema.

Opera 3 multi-company setups store inter-company transactions as normal invoices with a counterparty company code. We split these into separate Monday.com Workspaces or Boards per company code, and add an Inter-Company flag column on each record. The counterparty company reference is stored as a text column pointing to the relevant Organization or Deal in the counterpart workspace. This preserves the consolidated view intent while fitting Monday.com's flat workspace architecture. Customers without a multi-company requirement can map all records to a single Monday.com Workspace.