Migrate from Opal CRM to Salesforce Sales Cloud

Opal CRM Leads map directly to Salesforce Lead. Source attribution (form, upload, campaign, manual) is preserved in a custom field opal_lead_source__c. Any lead score or qualification data from Opal CRM custom fields migrates to a custom field opal_lead_score__c on the Salesforce Lead. We use the Salesforce Bulk API 2.0 for large lead volumes with batch chunking and validate row counts against the Opal CRM export before marking the phase complete.

Opal CRM team members (Admin, Manager, Sales Rep roles) map to Salesforce User records. We match by email address during migration. Role assignments are captured as a custom field opal_role__c on the User record because Opal CRM role definitions do not export as structured data. The customer's Salesforce admin provisions missing Users and assigns Profiles (System Administrator, Sales Manager, Standard User) based on the role mapping document we deliver. OwnerId references on Leads, Accounts, and Opportunities are resolved at migration time via the User lookup table.

Tour Plans in Opal CRM store itinerary data (dates, locations, assigned rep) alongside expense line items (amount, category, description) as a combined record. Salesforce has no native Tour or Visit object, so we decompose each Tour Plan into a Salesforce Task (or custom Tour__c object) carrying the itinerary header fields, then parse individual expense line items and create corresponding Expense__c custom records linked via a lookup relationship to the parent Task. Location coordinates, route sequence, and rep assignment migrate as custom fields on the parent record. If the Opal CRM export flattens expense line items into a notes field, we decompress and reconstruct them before insert.

Opal CRM Quotations map to Salesforce Quote records with line items migrated to QuoteLineItem. The quotation header fields (customer name, total amount, validity date) migrate directly. The platform-specific approval workflow state (Pending Approval, Approved, Rejected) does not map to standard Salesforce Quote fields, so we capture it as a custom picklist field quotation_workflow_state__c on the Quote. PDF attachments and signed documents from Opal CRM migrate as ContentDocument records linked via ContentDocumentLink. The customer decides whether to rebuild the quotation approval logic as a Salesforce Flow approval process post-migration.

Opal CRM pipeline stage names and order migrate to Salesforce Opportunity StageName values in the customer's active Sales Process. Stage probability percentages from Opal CRM map to StageProbability on each Salesforce stage. If Opal CRM stores pipeline-specific stage sets (e.g., different stages per product line or team), we create multiple Salesforce Sales Processes and map each pipeline to its corresponding Sales Process via Opportunity Record Type. Stage configuration happens before Opportunity import so that the StageName foreign key is satisfied at insert time.

If Opal CRM stores company or organization data separate from Leads, those records map to Salesforce Account. The company name becomes Account Name; website and address fields map directly. Account is created before any Contact import so that the AccountId lookup is satisfied on Contact insert. Dedupe key is Company Name combined with Website domain if available.

Opal CRM interaction logs (calls, emails, meetings) stored against Leads migrate to Salesforce as Task (calls and general activities), Event (meetings with StartDateTime and EndDateTime), and EmailMessage (emails with headers and body). The WhoId on the Salesforce record points to the migrated Lead. Activity timestamps are preserved as ActivityDate on Task and StartDateTime/EndDateTime on Event. Activity history uses the Salesforce Bulk API 2.0 with parent-record lookup resolution to handle large volumes without timing out.

Opal CRM role definitions (Admin, Manager, Sales Rep) do not export as structured data, so they cannot migrate as code. We capture the role assignment per user (which users have which roles) as a custom field opal_role__c on the Salesforce User record during migration. We deliver a written role mapping document that maps Opal Admin to Salesforce System Administrator or Custom: Sales profiles, Opal Manager to Sales Manager profiles, and Opal Sales Rep to Standard User profiles. The customer's Salesforce admin applies the Profile assignments post-migration.

Opal CRM supports custom fields on Leads and possibly other objects, but the schema is not publicly documented. We identify custom fields during discovery by reviewing the Opal CRM export file headers or by requesting schema screenshots from the customer. Each identified custom field is pre-created in Salesforce with an equivalent API name (opal_<fieldname>__c), matching field type (text, number, date, picklist), and required/optional setting. Custom field creation happens in the Salesforce Sandbox during the schema design phase before any data loads begin.

Opal CRM quotation approval workflows are platform-specific logic that does not export as code. We capture the workflow state on the migrated Quote record (quotation_workflow_state__c) but do not rebuild the automation. We deliver a written inventory documenting each Opal workflow trigger, conditions, actions, and a recommended Salesforce Flow equivalent (record-triggered or approval process). The customer's admin or a Salesforce partner rebuilds the workflow logic post-migration.

Opal CRM reports and dashboards do not migrate because Salesforce reporting uses a fundamentally different data model, visualization engine, and field reference system. We deliver a written inventory of all Opal CRM reports and dashboards with their filters, groupings, and metrics so the customer's admin can recreate them in Salesforce Reports and Dashboards. Salesforce Lightning Analytics offers more advanced visualization options that may exceed Opal CRM's native reporting capabilities.

Opal CRM's Basic plan includes point-based sales performance tracking (rewards/leaderboard data). This metric does not map to a standard Salesforce field. We preserve the points value as a custom number field opal_performance_points__c on the User record (rep-level) or as a custom field on the Lead or Opportunity depending on where the points data lives in the Opal CRM export. The customer decides whether to maintain this as a custom metric or replace it with Salesforce High Velocity Sales metrics post-migration.