Migrate from Opera 3 to Zoho CRM

Opera 3's built-in CRM module stores contacts in a separate file from the Sales Ledger customer export. We extract CRM contacts as a distinct CSV, designate each record with a Contact Type value (Customer, Lead, or Prospect) in Zoho CRM, and avoid creating duplicate Account records. If a CRM contact shares an email or account code with a Sales Ledger export row, we merge rather than create two records by matching on the primary key from the CRM module's contact_id field.

Sales Ledger customers from Opera 3 export via CSV with full billing address, payment terms, credit limits, and multi-currency settings. We map to Zoho CRM Account, preserving the customer account code as an external ID for reconciliation. If the customer uses Opera 3 multi-company structures, each company code becomes a separate Zoho CRM Organization or Account depending on the consolidation requirement flagged during scoping.

Opera 3's CRM module stores a Company record linked to CRM Contacts. This maps to a Zoho CRM Account. If the Company also appears in the Purchase Ledger as a supplier, we set Account Type to 'Customer / Vendor' or create a separate Vendor record and link it to the Account via the Vendor ID lookup.

Opera 3 Deals export with deal value, stage, customer link, and product line items. We map to Zoho CRM Deals, translating the Opera 3 deal status to a Zoho CRM Deal Stage value. If Opera 3 uses multiple deal pipelines, we configure multiple Zoho CRM Deal pipelines (supported from Standard tier) and assign the appropriate pipeline during import. Closed-won and closed-lost dates migrate as Zoho CRM custom date fields if the customer's reporting requires them.

Opera 3 Sales Order headers and line items export with order reference, order date, delivery address, pricing, and discount rows. We map order headers to Zoho CRM Sales Orders and line items to Sales Order Items. If Zoho CRM Standard is the destination tier (which does not include Quotes and Sales Orders), we flag this as a tier upgrade recommendation during scoping, or alternatively map to Deals with line items stored as custom fields.

Opera 3 stock codes, descriptions, unit prices, bin locations, and reorder levels export via the stock control CSV. We map to Zoho CRM Products with the Opera 3 stock code preserved as an external ID. The price list entries from Opera 3's standard pricing migrate to Zoho CRM Price Lists.

The OPUS add-on stores customer-specific stock variants with a different stock code and description per customer for the same base product. This exports as a separate CSV with a different schema from the standard stock file. We join it to the main product export using the base stock code and customer account reference, then map each variant to Zoho CRM Price List Entries scoped to the specific customer Account. The customer chooses during scoping whether to use Zoho CRM's multi-variant Product feature or price-list scoping.

Opera 3 employee records export via CSV including name, bank details, start and end dates, P45 data, and national insurance number. We map to Zoho CRM Contacts with Contact Type set to 'Employee' and NI number stored in a custom field. RTI FPS XML files contain employer payment summaries that supplement the CSV export for audit trail purposes. Note that Zoho CRM does not include a native payroll module — payroll functionality requires Zoho Payroll or Zoho Books and is scoped separately.

Opera 3 project records export with project cost codes, phase-level tracking, and labour, purchase,, and expense allocations linked to the Nominal Ledger. We map to Zoho CRM Projects with phase names migrated as Zoho sub-tasks or milestones. The labour and expense allocations migrate as Project Tasks with custom fields for the cost type. Project billing linked to Sales Orders maps to Zoho CRM Deal lookup if the customer uses project-to-deal tracking.

Opera 3 CRM activities are stored as text-based notes rather than structured event records. We extract each activity entry with its timestamp, the linked CRM contact reference, and the activity body text. These migrate to Zoho CRM Notes (for free-text entries) or Tasks (for action items with a due date) linked to the parent Contact record. Activity type designation in Opera 3 (call, email, meeting) is preserved as a custom field in Zoho CRM.

Opera 3's fixed asset register with acquisition dates, cost, depreciation method, net book value, and disposal history does not map to a standard Zoho CRM module. We flag this as out-of-scope for the Zoho CRM migration and recommend Zoho Books Fixed Assets as the destination for the accounting-side fixed asset data. The customer admin creates a custom Fixed Assets module in Zoho CRM if asset tracking within the CRM is required.

Purchase Ledger suppliers export via CSV with full address, payment terms, and bank details. We map to Zoho CRM Vendors, preserving the supplier account code as an external ID. Vendor-to-Account relationships (if the same entity is both a customer and a supplier) are handled by linking the Vendor record to the existing Account via the Vendor ID custom field.

Opera 3 multi-currency transactions export with currency code, exchange rate used at transaction time, and transactional amount in the foreign currency. We map currency codes to Zoho CRM enabled currencies (configured in Setup > Currencies) and store the historical exchange rate as a custom field on the transaction record. Zoho CRM does not support per-transaction exchange rates natively; the customer's admin configures standard price lists per currency and we assign the appropriate price list to each Account.