Migrate from Prospect CRM to Microsoft Dynamics 365 Sales

Prospect CRM stores all prospects as a single contact record without a Lead-Contact distinction. We resolve the split at migration time: Contacts with a linked Deal or Opportunity history become Salesforce-style Contacts attached to an Account; Contacts with no deal association become Leads. We preserve the original Prospect CRM contact record ID in a custom field prospect_crm_id__c on both Lead and Contact for audit and cross-reference.

Prospect CRM Company records map directly to Microsoft Dynamics 365 Sales Account. The Company record is created before any Contact import to satisfy the Account lookup reference on Contact. We map the primary address fields and any custom Company-level properties to custom Account fields.

Prospect CRM Deals map to Dynamics 365 Opportunities. Pipeline stage names from Prospect CRM require explicit mapping to Dynamics 365 stage values because stage IDs are not portable across platforms. We capture stage order and probability percentages during scoping and configure the corresponding Sales Process in Dynamics 365 before migration.

Prospect CRM's Problem Pipelines (used for tracking delivery issues, returns, and complaints) are a non-standard object with no direct Dynamics 365 equivalent. We extract Problem records with Status, Outcome, and linked Customer fields and map them to Dynamics 365 Cases. We configure a dedicated Case Business Process and map Problem Pipeline stage names to Case Status values. This is the most schema-dependent mapping in the migration and requires explicit customer sign-off before Case Business Process configuration.

RFM (Recency, Frequency, Monetary) segmentation is a native Prospect CRM classification with no equivalent in Microsoft Dynamics 365 Sales . We export RFM segment assignments as three custom fields on the Contact record (RFM_Recency__c, RFM_Frequency__c, RFM_Monetary__c) and a combined RFM_Segment__c picklist. These custom fields support segmentation queries in Dynamics 365 Views and Reports without rebuilding the classification logic.

Product catalog data including SKU, name, description, and pricing migrates to Dynamics 365 Product2 records. We create Standard Price Book entries during import. The stock-aware flag and live inventory linkage from Prospect CRM do not migrate as a feature; we document the inventory integration path via Power Automate or Dataverse for the customer's admin to configure against their back-office system.

Activity history including notes, calls, emails, and tasks migrates as chronological Task and Event entries in Dynamics 365. Call logs map to Task with TaskSubtype=Call and CallDurationInSeconds preserved. Email engagements map to EmailMessage records linked to the parent Contact or Account. Activity timestamps are preserved to maintain the timeline ordering that sales reps rely on.

Custom fields on Contacts, Companies, and Deals in Prospect CRM migrate as custom fields on the corresponding Dynamics 365 entity. We capture field type (dropdown, date, number, text) during scoping to ensure validation rules are configured correctly in Dynamics 365 before import. Custom field names are preserved with a PC suffix appended to the API name to distinguish migrated fields from new fields created post-migration.