Migrate from ContactDB to Microsoft Dynamics 365 Sales

ContactDB contact records map directly to Dynamics 365 Contact. Name, title, email, phone, and mailing address fields migrate to the standard Contact fields (fullname, jobtitle, emailaddress1, telephone1, address1_line1/2/3/4). The Contact record is created after its parent Account so that the accountid lookup is satisfied at insert time. We apply a pre-import validation pass that flags records with malformed email formats, missing first or last name, or empty phone and email for customer review before the Dynamics import.

ContactDB exposes firmographic attributes per contact including company name, size range, industry, and SICCODE. We extract unique company names from all Contact records, deduplicate by normalized company name, and create Account records before Contact import. Dynamics 365 Account fields populated include name, industry (mapped from ContactDB industry), numberofemployees (from size range bucketing), and a custom siccode__c field carrying the raw SICCODE value. The Account is the parent of the Contact so that the accountid lookup is resolved at migration time.

ContactDB segments contacts by industry, profession, title, country, and software-usage criteria, but these segment labels are not exported as standalone tag objects. We reconstruct segment membership as custom fields on the Contact record. During scoping, the customer confirms which segment categories are meaningful post-migration—typically industry__c (picklist), profession__c (text), country__c (text), and software_usage__c (multi-select text). We create these custom fields in Dynamics 365 via the metadata API before any contact import begins.

ContactDB provides SICCODE as a firmographic attribute per contact. Microsoft Dynamics 365 Sales does not have a native SICCODE field, so we create a custom text field siccode__c on the Account object and populate it from the ContactDB export. The customer may alternatively use a Dynamics 365 industry classification; the migration maps ContactDB SICCODE to the closest Dynamics 365 industry value where a mapping exists.

ContactDB includes credit rating as a firmographic signal in its export. We create a custom field credit_rating__c on the Account object and populate it from the ContactDB export. Note that Microsoft Dynamics 365 Sales does not have a native credit rating field; this is a custom enrichment field that the customer's sales or credit team uses for lead scoring or routing.

ContactDB is a purchased list database and does not store engagement history, email opens, call logs, or meeting records. No activity data is available to migrate. Dynamics 365 activity objects (Task, EmailMessage, Event) are created from the customer's live outreach tools post-migration, not from ContactDB. We scope activity migration out of the project and document this limitation in the migration scope agreement.

ContactDB does not implement a pipeline or deal-tracking model. There are no opportunity stages, deal amounts, or sales cycle data to migrate. Dynamics 365 Opportunities are created by the sales team post-migration and do not inherit any pipeline history from ContactDB. We scope pipeline objects out of the migration scope.

ContactDB is a data product, not a team CRM. There are no internal user accounts or owner assignments in the export. Dynamics 365 User provisioning is handled by the customer's IT or Dynamics admin outside the migration scope. We flag that every Contact in Dynamics 365 requires an OwnerId at insert time and advise the customer to provision at least one System Administrator or migration-service user with the appropriate Security Role before migration begins.