Migrate from Pro-Sales CRM to Microsoft Dynamics 365 Sales

Pro-Sales CRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (fullname, emailaddress1, telephone1, jobtitle, company association) map 1:1. Lifecycle stage from Pro-Sales CRM migrates to a custom field hs_original_lifecycle__c because Microsoft Dynamics 365 Sales does not have a native lifecycle stage property. We inspect Pro-Sales CRM's custom field list during discovery and create equivalent custom fields in Dataverse before migration.

Pro-Sales CRM Company records map to Microsoft Dynamics 365 Sales Account. Address fields (address1_line1, address1_city, address1_stateorprovince, address1_postalcode, address1_country) map directly. Industry and company size map to standard Dynamics 365 fields or custom fields depending on the destination schema. Account is created before Contact import so the parent Lookup is satisfied at insert time.

Pro-Sales CRM Deal records map to Microsoft Dynamics 365 Sales Opportunity. Deal amount maps to estimatedvalue; close date maps to estimatedclosedate; stage name maps to a stage value in the destination Sales Process. We extract the full Pro-Sales CRM stage configuration (names, order, probability percentages) during discovery and use it to configure the corresponding Microsoft Dynamics 365 Sales Process and stage values before any Opportunity records load.

Pro-Sales CRM allows custom stage names and probability weights per stage without tier restrictions. Each Pro-Sales CRM stage maps to a Microsoft Dynamics 365 Sales Process stage value with the matching probability percentage (rounded to the nearest integer that Dynamics 365 allows). If the customer has multiple Pro-Sales CRM pipelines, we create multiple Dynamics 365 Record Types with corresponding Sales Processes so that stage values remain scoped per pipeline.

Pro-Sales CRM activity records (call logs, notes, task completions) map to Dynamics 365 Task and EmailMessage records. Call logs map to Task with TaskSubtype = Call and call duration stored in a custom field. Notes map to Note records linked via ContentDocumentLink. We normalise date formatting and timezone handling to UTC during migration. Large activity histories (over 100,000 records) use the Dataverse Bulk API with batch chunking and parent-record lookup resolution (WhoId for Contact, WhatId for Opportunity or Account).

Pro-Sales CRM custom fields on Contacts and Deals are inspected during discovery and replicated in Dataverse before migration. Custom field types (text, number, date, picklist, checkbox) map to the closest Dataverse column type. On Microsoft Dynamics 365 Sales Professional tier, custom field counts are limited; we confirm the destination tier during scoping and flag any fields that cannot fit within the Professional limit. If the customer intends Enterprise or Premium, we create all fields without tier-based restriction.

Pro-Sales CRM tag assignments on records migrate to a Dynamics 365 multi-select picklist field. We extract all distinct tag strings during discovery, add them as picklist values in Dataverse, and populate the field on each migrated record. If the customer has more than 150 distinct tags on a single field, we discuss splitting them across multiple fields or using a custom entity for tag management in the destination.

Pro-Sales CRM assigns a single owner per record by owner ID. We extract all distinct owner IDs referenced across Contacts, Companies, Deals, and Activities and match them by email to the Dynamics 365 destination User table. Any owner without a matching User record is held in a reconciliation queue, and the customer's Dynamics 365 admin provisions the missing Users before record import resumes. Owner resolution must complete before activity import because Task and Event records reference the OwnerId field.