Migrate from Opal CRM to Microsoft Dynamics 365 Sales

Opal CRM Leads map directly to Microsoft Microsoft Dynamics 365 Sales Lead records. We preserve source attribution fields (campaign, form, channel) as custom fields on the Lead because Microsoft Dynamics 365 Sales stores these as standard fields (leadSource, originatingCampaignId) that map cleanly from Opal's lead capture metadata. Owner assignment from the Opal CRM Sales Rep field resolves to a Dynamics 365 User by email lookup.

Opal CRM Companies map to Microsoft Dynamics 365 Sales Account records. Company address, phone, and domain fields transfer directly. The Account record is created before any Contact or Opportunity import so that the AccountId lookup is satisfied at the moment of record insert. If Opal CRM stores multiple contacts per Company, each becomes a separate Contact record with the Account lookup populated.

Opal CRM Sales Reps (with roles Admin, Manager, Sales Rep) map to Microsoft Dynamics 365 Sales User records. We resolve by email match. Role permissions do not export as structured data from Opal CRM, so we capture per-user role assignments during discovery and document the equivalent Dynamics 365 security role assignment for the customer's admin to configure post-migration. Provisioning of the Dynamics 365 Users must complete before OwnerId lookups can resolve on Lead, Account, and Opportunity records.

Tour Plans in Opal CRM store itinerary data (dates, locations, associated leads) plus expense line items. If the export flattens Tour Plans to a single record, we decompress the expense entries and reconstruct them as individual Task records with custom fields for expense type, amount, and description, linked to the parent Lead or Contact via the RegardingObjectId lookup. Microsoft Dynamics 365 Sales has no native Tour/Visit object, so we use a custom Dataverse table or structured Activity records depending on the customer's preference documented during scoping.

Opal CRM Quotations map to Microsoft Dynamics 365 Sales Opportunity records with OpportunityLineItem entries for each quotation line. The quotation header (customer, total value, date, expiry) becomes Opportunity fields (AccountId, Amount, EstimatedCloseDate). Quotation line items map to OpportunityLineItem with Product2 reference, Quantity, and UnitPrice resolved from the destination Pricebook. The Opal CRM Quotation workflow approval state (pending, approved, rejected) has no standard Dynamics 365 equivalent and is stored as a custom field quotation_workflow_state__c on the Opportunity for the customer's admin to map to an approval flow or pipeline stage logic post-migration.

Opal CRM pipeline stage names and order transfer to Microsoft Dynamics 365 Sales as either a custom Opportunity Stage value added to the active Sales Process, or as a custom picklist field if the destination org uses a non-standard stage naming convention. We preserve stage sequence order and probability percentages where available. If Opal CRM stores multiple pipelines, we map each to a separate Dynamics 365 Record Type on Opportunity.

Opal CRM engagement logs (calls, emails, meetings) against Leads map to Microsoft Dynamics 365 Sales Task records (TaskSubtype=Call for calls), Event records (for meetings with start/end times), and EmailMessage records (for emails). The RegardingObjectId on each Activity points to the migrated Lead. Activity timestamps (ActivityDate) preserve the original engagement date so the timeline ordering is intact in Dynamics 365. Call duration and disposition map to custom Task fields if captured in Opal CRM.

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 inspecting the export file schema, then provision equivalent custom fields in Dynamics 365 Dataverse using the appropriate field type (text, number, picklist, date). Custom field names are preserved with a opal_source__ prefix to indicate provenance. Field-level security and validation rules on the destination org may require coordination with the Dynamics 365 admin before custom field population.