Migrate from Concord CRM to Microsoft Dynamics 365 Sales

Concord CRM Companies map directly to Microsoft Dynamics 365 Sales Accounts. We export Companies first in the migration sequence because Contacts carry company_id as a foreign key reference that must resolve to an existing Account record at import time. The Concord company domain name maps to Account.Website, and industry/type fields map to the corresponding Dataverse picklist fields. Any Concord Company without a name is assigned a placeholder and flagged for the customer to review post-migration.

Concord CRM Contacts map to Microsoft Dynamics 365 Sales Contact records. We resolve the Concord company_id reference to the Account.recordid we created during the Account import phase, then set Contact.parentcustomerid_account on every Contact insert. First name, last name, email, phone, job title, and address fields map 1:1. Concord custom fields (boolean, date, select, text, number) migrate to Dataverse custom fields pre-created with matching field types before the Contact phase begins.

Concord CRM Deals map to Microsoft Dynamics 365 Sales Opportunity. Concord's deal stage name maps to the Opportunity StageName value that corresponds to the matching Dynamics Sales Process. We pre-configure the Sales Process and stage values before migration so that Closed Won, Closed Lost, and in-progress stages align. Deal value maps to Amount, expected_close_date maps to EstimatedCloseDate, and the Concord assigned user resolves via email match to the Dynamics User.ownerid.

Concord pipeline stages export as raw stage name values that require mapping to a Microsoft Dynamics 365 Sales Sales Process. We create a Sales Process per Concord pipeline, whitelist the relevant stage values, and assign probability percentages matching the Concord source. If Concord has multiple pipelines, each becomes a separate Dynamics Sales Process or Record Type scoped to Opportunity.

Concord CRM Products map to Microsoft Dynamics 365 Sales Product2 records. We create Standard Pricebook entries during the Product import phase using the Concord product price. Product name, SKU (from Concord product code), and description migrate 1:1. Product2 must exist before any Opportunity Line Items are imported if the migration includes Deal-to-Opportunity line items.

Concord CRM Activity records with type = call map to Microsoft Dynamics 365 Sales Task with TaskSubtype = Call. We reconstruct the parent association using Concord's linked_resource_type and linked_resource_id fields: linked_resource_type = contact resolves to WhoId (Contact.recordid), linked_resource_type = company resolves to WhatId (Account.recordid), and linked_resource_type = deal resolves to WhatId (Opportunity.recordid). Call duration and disposition from Concord migrate to custom Task fields.

Concord CRM Activity records with type = meeting map to Microsoft Dynamics 365 Sales Event. We map the Concord activity date and duration to Event.StartDateTime and EndDateTime. Parent association follows the same linked_resource_type resolution as calls, with WhatId and WhoId set accordingly. Location from Concord maps to Event.Location.

Concord CRM Activity records with type = task map to Microsoft Dynamics 365 Sales Task. Status (completed/open), Priority, ActivityDate, and notes body migrate 1:1. Task.OwnerId resolves via the Concord assigned user email match. The WhatId reference resolves using the same linked_resource_type lookup as other activity types.

Concord CRM custom fields are retrieved via the REST API using the field UUID as the payload key. Boolean, date, select, text, and number field types have different payload formats documented in Concord's API reference. We pre-create all custom fields in the Dataverse schema before any data import phase, using the matching field type (bit for boolean, datetime for date, picklist for select, nvarchar for text, decimal for number). Custom field names are preserved with a concord_ prefix to avoid naming conflicts with existing Dynamics fields.