Migrate from Opera 3 to Pipedrive

Opera 3's Sales Ledger stores customer accounts with billing address, payment terms, credit limits, and multi-currency flags. The CRM module's contact records attach to these accounts. We map Sales Ledger account_name to Pipedrive Person name, primary email from the contact's email field, phone from the telephone field, and the billing address to the Person's address fields. Where a Sales Ledger account has multiple named contacts, each becomes a separate Person record linked to the same Organization.

Opera 3's Sales Ledger account header maps to Pipedrive Organization. The account code becomes the Organization's Pipedrive ID or a custom external_id field. We preserve payment terms, credit limit, and default currency from the Sales Ledger header as custom fields in Pipedrive because the standard Organization object does not carry these ERP-specific fields natively. Multi-currency accounts require a currency field on the Organization record.

Opera 3's Purchase Ledger supplier contacts export separately from the Sales Ledger. We map these to Pipedrive Person records tagged with a vendor segment label via a custom field. Supplier contacts do not naturally belong in a sales CRM, but teams that want a unified contact record in Pipedrive for both customer and supplier relationships import them with a type flag.

Opera 3's CRM module stores activities as text notes against a contact or company record with a date stamp and an owner reference. These are flat text blobs without type, duration, or participant fields. We parse the note text, detect keywords (call, meeting, email, visit) to assign an Activity type in Pipedrive, and preserve the original note body as an Activity note. Type detection is a best-effort configuration; unstructured notes that cannot be typed migrate as general Task activities.

Opera 3 Sales Order headers with line items map to Pipedrive Deals. The order total becomes the Deal value, the order date becomes the expected close date, and the order status (pending, confirmed, dispatched, invoiced) maps to a Pipedrive stage or a custom status field. Closed Won maps to invoiced orders; Closed Lost maps to cancelled orders. We preserve the line-item product descriptions as Deal notes or a custom product list field since Pipedrive Deals do not natively carry line-item structures without additional configuration.

Opera 3 Sales Invoice headers and line items migrate as Activity records (a completed-task note) linked to the corresponding Deal in Pipedrive. The invoice number becomes the Activity subject, the invoice total becomes a custom field on the Activity record, and the line items are preserved as a formatted note block. Credit notes migrate as Activities with a negative amount in the custom invoice total field. We do not create Pipedrive Invoice objects because Pipedrive does not have a native invoicing feature; customers use third-party integrations like FreshBooks or QuickBooks for document generation.

Opera 3 standard stock codes export with stock code, description, unit price, and bin location. We map these to Pipedrive Products (Product2 records) where the Sales Ledger orders include product references. Stock items without an associated Sales Order do not migrate unless the customer explicitly requests a product catalog setup in Pipedrive. Customer-specific product variants from the OPUS add-on require additional mapping: we join the OPUS export on base stock code plus customer account reference and create a separate price-list entry per variant.

Opera 3 Employee records export via CSV with name, email, start date, and department. We match employees by email against Pipedrive User accounts. Active sales employees who will use Pipedrive must have a User provisioned before migration; back-office employees who will not use Pipedrive are optionally imported as Person records or excluded from the migration scope. The customer defines the cut-off during scoping.

Opera 3 custom fields added via the OPUS add-on or bespoke Visual FoxPro schema modifications are not standardized and vary by installation. We do not automatically migrate bespoke custom fields. We audit the source schema during discovery, identify which OPUS fields map to standard Pipedrive fields or custom fields on People, Organizations, and Deals, and document the gap. Unmapped bespoke fields are listed in the migration inventory for the customer's admin to review and recreate manually in Pipedrive's field editor.

Opera 3's multi-company support stores separate company codes with inter-company debtor and creditor balances. When migrating to Pipedrive, which is a single-tenant CRM without native multi-company structures, we map each Opera 3 company code to a separate Organization record tagged with a company_code custom field. Inter-company balances are preserved as a separate reconciliation document listing the balance, the counterparty company code, and the currency, so the customer's finance team can re-establish inter-company matching in the destination accounting system separately.