Migrate from DinamikCRM to Microsoft Dynamics 365 Sales

DinamikCRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (full name, email, phone, address, company link) transfer to the Dataverse contact entity via the Web API. We resolve the parent Company reference during import so that each Contact is linked to the correct Account record. Any DinamikCRM custom fields on the Contact module map to custom contact fields (new_customfield__c) that we pre-create in Dataverse before migration.

DinamikCRM Company records map to Microsoft Dynamics 365 Sales Account. The accountname and website fields transfer directly. Account is the parent of Contact and the lookup target for Opportunity (WhatId). We import Accounts first in dependency order so that AccountId is available at Contact and Opportunity insert time, avoiding orphaned records.

DinamikCRM Lead records map to Microsoft Dynamics 365 Sales Lead. Lead status values from DinamikCRM map to Dynamics 365 leadstatus optionset integers; mismatches are corrected in a pre-migration transform step. Lead scoring or grade fields from DinamikCRM migrate to custom numeric fields on the Lead entity for reporting consistency.

DinamikCRM Deal records map to Microsoft Dynamics 365 Sales Opportunity. The deal value and stage name transfer to estimatedvalue and stagecode respectively. We resolve the parent Contact (潜在的客户) and Account references to populate the Opportunity WhatId and CustomerId fields. Closed-won and closed-lost outcomes from DinamikCRM map to Microsoft Dynamics 365 Sales Process stage outcomes.

DinamikCRM pipeline stages map to a Microsoft Dynamics 365 Sales Process with corresponding stagecode values. Each stage from DinamikCRM becomes a stage in the sales process; stage probability percentages transfer to stageprobability on the ProcessStage entity. We configure the Sales Process in Dataverse during the schema design phase before any Opportunity data loads.

DinamikCRM Activity records cover calls, emails, meetings, and tasks under a single object type. We split them at migration time by activity type identifier: email-type activities become EmailMessage records linked to an ActivityPointer; call and task activities become Task records with the appropriate TaskSubtype; meeting activities become Event records. All activity records resolve their Regarding (objectid) to the correct Contact, Account, or Opportunity in the destination.

DinamikCRM Appointment records map to Microsoft Dynamics 365 Sales Event (Appointment). Start time, end time, location, description, and attendee list transfer to the corresponding Event fields. Attendees resolve to Contact or User records via email lookup, creating EventRelation records to preserve the attendee relationship in Dynamics 365.

DinamikCRM Invoice records with line items, totals, and status map to Microsoft Dynamics 365 Sales Invoice. The customer account and product line items resolve to existing Account and Product2 records in the destination. Financial fields are flagged during scoping for customer validation since tax, currency, and discount logic may differ between the two platforms and require post-migration review.

DinamikCRM custom modules (a frequent pattern in this platform) are discovered during the scoping phase by enumerating the live module list via the API discovery endpoint. Each active custom module maps to a custom Dataverse entity (new_modulename) with fields translated to matching Dataverse types. Custom entity relationships with standard objects (Contact, Account, Opportunity) are pre-configured as Dataverse lookup relationships before data migration begins. This step adds time to scoping for accounts with more than five active custom modules.

DinamikCRM user accounts and record owners map to Microsoft Dynamics 365 Sales User records by email address lookup. Owners assigned on Contact, Account, Opportunity, and Activity records resolve to the corresponding Dynamics 365 UserId. Any DinamikCRM owner without a matching user in the destination tenant is placed in a reconciliation queue for the customer's admin to provision before record import resumes.