Migrate from edge CRM to Microsoft Dynamics 365 Sales

edge CRM uses a unified Contact object that may contain unqualified prospects as well as existing customer contacts. Microsoft Dynamics 365 Sales separates unqualified prospects (Lead) from qualified buyers (Contact attached to Account). During scoping, we define the split rule based on edge CRM's contact status field or AI qualification flag, route unqualified records to Dynamics Lead, and move qualified records to Contact with AccountId resolved. We preserve the original edge CRM contact record ID in a custom field edecrm_id__c on both Lead and Contact for audit traceability.

edge CRM Company records map directly to Dynamics 365 Account. The company domain or website URL becomes the Account Website field. We import Accounts first in the migration sequence so that Contact-Account lookups resolve correctly at Contact insert time. Any Company without a contact association becomes a standalone Account.

edge CRM Deals map to Dynamics 365 Opportunity. The dealstage property maps to a Dynamics Opportunity StageName, and the pipeline assignment maps to a Dynamics Record Type and Sales Process that we configure in the destination org before migration. Monetary value, expected close date, and deal owner transfer directly. Closed-Lost and Closed-Won reasons from edge CRM become custom Opportunity fields in Dynamics.

edge CRM's Lead object (distinct from Contact) maps to Dynamics Lead. If edge CRM has AI-scored qualification data, we preserve the score in a custom field edecrm_lead_score__c on the Dynamics Lead. Lead status maps to Dynamics Lead Status with a value set we configure during schema design.

edge CRM allows custom stage names and ordering per pipeline. We extract the full stage list including custom names, sequence order, and stage probabilities, then create a corresponding Dynamics Sales Process with matching StageName values. Stage probability percentages migrate to Dynamics StageProbability fields rounded to the nearest integer.

edge CRM activities with type=calls map to Dynamics Task with TaskSubtype=Call; type=meetings map to Event with StartDateTime and EndDateTime preserved; type=emails map to EmailMessage records linked to an Activity Task; type=notes map to Note records linked via ContentDocumentLink. We use Dynamics Bulk API 2.0 for large activity volumes with chunking and parent-record (WhoId, WhatId, AccountId) resolution so each activity lands against the correct record in the timeline.

edge CRM follow-up tasks with due dates and completion status map to Dynamics Task. We preserve Status (completed vs. open), Priority, ActivityDate, and assigned owner. Task owner resolution follows the same User mapping as Contacts and Deals.

edge CRM custom properties on Contacts, Companies, Deals, and Leads require pre-creation in Dynamics 365 before data import. We extract the full custom field schema including field names, types, and picklist values, then create equivalent custom fields in Dynamics (with __c suffix per Dataverse naming convention) before migration begins. Field type mapping: text strings to Text fields, numbers to Decimal or Integer, dates to Date fields, and multi-select values to Choice or MultiSelectOptionSet fields.