Migrate from Opal CRM to Pipedrive

Opal CRM Leads map to Pipedrive Leads by default. If the customer uses Opal's lead engagement tracking to qualify buyers into a sales-ready stage, those records can alternatively map to Pipedrive Contacts attached to an Organization. We determine the mapping strategy during discovery based on how the customer's sales process uses Opal's lifecycle stages. Source attribution (form, upload, campaign) from Opal preserves as a custom field on the Pipedrive record.

Opal CRM may store company records associated with leads. These map directly to Pipedrive Organizations. The company name becomes the Organization name field, and any address or industry data maps to standard Organization fields. If Opal does not have a separate Company object and stores company data as fields on the Lead, we extract and create Organization records during the transform phase.

Opal CRM team members (Sales Rep, Manager, Admin roles) map to Pipedrive Users. We resolve owners by email match against the destination Pipedrive account's User table. Any Opal user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Opal role hierarchies (Admin, Manager, Sales Rep) do not export as structured data; we document the role assignment per user in the handoff notes for manual reconfiguration in Pipedrive.

Opal CRM Tour Plans store itinerary data (dates, locations, assigned rep) and individual expense line items. Pipedrive has no native Tour or Visit object, so Tour Plan itinerary data migrates as Activity records (Meeting or Task type) with location stored in a custom field. Each expense line item within a Tour Plan is reconstructed as a separate Note or as a custom field set on the linked Activity, preserving the expense type, amount, and date. If the expense data flattens during Opal export into a single notes field, we decompress it into individual structured rows during the transform phase.

Opal CRM Quotations with header fields (quotation number, date, total, status) and line items migrate to Pipedrive Deals. The quotation total maps to Deal value, quotation status becomes a custom field (quotation_status__c), and line items with product name, quantity, and price migrate as Deal Product entries. Pipedrive's Products feature (available from Essential plan) must be enabled and populated before line item import. If Opal Quotations use a multi-currency setup, currency codes preserve as a custom field on the Pipedrive Deal.

Opal CRM's internal quotation approval workflow generates a workflow state value (e.g., Draft, Submitted, Under Review, Approved, Rejected) that does not map to any standard Pipedrive field. We capture the workflow state as a custom picklist field (quotation_workflow_state__c) on the Pipedrive Deal and document it in the handover notes so the customer's admin can decide whether to rebuild the workflow logic using Pipedrive's Workflow Automation feature (Professional plan and above). The workflow state is informational only after migration.

Opal CRM tracks lead progress through implied pipeline stages via its lead engagement tools. Stage names and order extract as a configuration set during discovery. We create a Pipedrive Pipeline with matching stage names and probabilities. If Opal uses multiple lead pipelines (e.g., inbound vs outbound), we create multiple Pipedrive Pipelines and map the relevant stages per pipeline. Stage probability percentages round to Pipedrive's allowed integer values.

Opal CRM call logs attached to leads migrate to Pipedrive Activities with type Call. Call duration, disposition, and any notes transfer to the activity's subject, duration, and notes fields. Activity timestamps preserve from Opal to maintain the engagement timeline sequence.

Opal CRM email engagements linked to leads migrate to Pipedrive Activities with type Email. The email subject, body content, and timestamp transfer to the activity. If Opal stores email as a reference link rather than full content, we store the link in the activity notes field and flag for manual review.

Opal CRM meeting records linked to leads migrate to Pipedrive Activities with type Meeting. Start time, end time, location, and attendee data transfer to the corresponding activity fields. Attendee email addresses create Person records or link to existing Leads or Contacts in Pipedrive via the Activity's person_id field.

Opal CRM supports custom fields on Leads and possibly other objects, but the schema is not publicly documented. During discovery we extract all custom field definitions from the Opal export, identify their data types (text, number, date, picklist), and create matching custom fields in Pipedrive before data import. Any custom fields that cannot be typed definitively flag for manual review during the sandbox migration. Pipedrive custom fields are available from the Essential plan onward.

Opal CRM captures lead source from forms, uploads, offline events, and marketing campaigns as a native field. We map this to Pipedrive's built-in label field or a custom field (lead_source__c) on the Lead record. If the customer's sales process requires UTM or campaign attribution data, we create additional custom fields for that context.