Migrate from crmConnect to Microsoft Dynamics 365 Sales

crmConnect Contacts with qualification indicators (lead score, stage property) map to Salesforce-style Lead. Contacts with established company association and active deal history map to Dynamics 365 Contact attached to an Account. We compute the split during migration scoping using crmConnect contact properties and preserve the original crmConnect contact ID in a custom field crconnect_id__c for reconciliation.

crmConnect Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The company domain becomes the Account Website field and serves as the dedupe key during import. Account is created before any Contact import so the AccountId Lookup is satisfied at Contact insert. Billing address and shipping address from crmConnect map to the corresponding Account address fields; Dynamics 365 enforces a single primary address per address type.

crmConnect pipeline stage names and transition rules map to Microsoft Dynamics 365 Sales Process stage values. Each crmConnect pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate to StageProbability on each stage definition.

crmConnect Opportunities map to Dynamics 365 Opportunity with deal amount, close date, owner, and stage preserved. The crmConnect pipeline assignment determines the Opportunity Record Type and Sales Process at import time. Custom opportunity fields require field-level discovery during the export phase and typed mapping against the destination Opportunity schema.

crmConnect calendar records with Google Calendar or Outlook sync map to Dynamics 365 Event. StartTime, EndTime, Location, and attendee list migrate directly. EventRelation records are created linking attendees to the correct Contact, Account, or Opportunity. crmConnect Standard tier limits to 1 calendar; Professional tier allows unlimited calendars, which we confirm before migration scoping.

crmConnect membership portals and course enrollments exist as separate non-standard record types. We migrate membership status, enrollment date, student contact reference, and course name as a custom Dataverse entity (e.g., Enrollment__c) with lookup to the Contact. The customer's admin defines the custom entity schema before migration begins.

crmConnect automations use a drag-and-drop builder with no documented export format. We capture automation trigger types, conditions, and action sequences as structured JSON metadata and screenshot documentation. Microsoft Dynamics 365 Sales automations rebuild in Power Automate or classic Workflows by the customer's admin using this documentation as the rebuild spec.

crmConnect custom contact and opportunity properties lack a documented API schema endpoint. We discover available custom fields during the CSV export phase and map them field-by-field during import. Field types (text, number, date, picklist) are inferred from the CSV data and typed to equivalent Dynamics 365 field types in the target schema.