Skip to content

Migration guide · CRM Platform

Microsoft Dynamics 365 to Salesforce migration

Microsoft Dynamics 365 / Dynamics CRMSalesforce

Short answer

Migrating from Microsoft Dynamics 365 to Salesforce moves accounts, contacts, opportunities, cases and activities, plus custom entities, into Salesforce objects, and replaces Dynamics workflows and Power Automate flows with Salesforce Flow. Firms move for Salesforce's ecosystem, industry clouds and AI capabilities.

Why firms make this move

Dynamics and Salesforce have similar core concepts, which makes mapping familiar, but custom entities, option sets and Power Platform automation need careful translation. Outlook and Teams users also need a clear plan for email, calendar and collaboration integration in the new system.

What moves

  • Accounts, contacts and leads
  • Opportunities, quotes and products
  • Cases and knowledge articles
  • Activities, emails and notes
  • Custom entities and option sets

How the data maps

FromTo
AccountAccount
ContactContact
OpportunityOpportunity
CaseCase
Custom entityCustom object
Option setPicklist
Workflow / Power AutomateFlow

See the field-by-field map ↓

What to watch out for

  • Option sets that need value translation
  • Power Automate flows that touch other Microsoft systems
  • Email and calendar sync moving to Einstein Activity Capture
  • Security roles that map differently to profiles and permission sets

How Vantage Point runs the migration

  1. Discovery and data inventory: what exists, what is clean, what is worth moving
  2. Target design: objects, record types, households or companies, ownership and security
  3. Field-by-field data mapping document, signed off by business owners
  4. Cleanup and deduplication before the move, not after
  5. Test loads into a sandbox with reconciliation reports
  6. User acceptance testing with real scenarios
  7. Cutover: final delta load, integrations switched, old system set to read-only
  8. Hypercare and adoption support

Typical timeline

Typically 8 to 16 weeks.

Frequently asked questions

Will Outlook still work with Salesforce?

Yes. Salesforce integrates with Outlook and Microsoft 365 for email and calendar, including Einstein Activity Capture.

Can we migrate Dynamics attachments?

Yes. Notes and attachments can be migrated as Salesforce Files, subject to storage planning.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Microsoft Dynamics 365 to Salesforce: field by field

16 mappings we start from on this migration, 10 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Accountname / telephone1 / websiteurl AccountName / Phone / Website req direct
Accountparentaccountid AccountParentId lookup
Contactfirstname / lastname / emailaddress1 ContactFirstName / LastName / Email req direct
Contactparentcustomerid ContactAccountId lookup
LeadLead fields LeadLead fields direct
Opportunityname / estimatedvalue / estimatedclosedate OpportunityName / Amount / CloseDate req direct
Opportunitystatecode / statuscode / salesstage OpportunityStageName req picklist map
Opportunitycustomerid (account or contact) OpportunityAccountId req derive Polymorphic: if the customer is a contact, use that contact's account.
Incidenttitle / description / statuscode CaseSubject / Description / Status picklist map
Phone call / taskActivity TaskSubject / ActivityDate / WhoId / WhatId association
AppointmentActivity EventStartDateTime / EndDateTime association
AnnotationNotes and attachments ContentNote / Files— direct
Option setValues PicklistValues picklist map
ownerid (user or team)Owner OwnerIdUser or queue req lookup Teams usually become queues or public groups.
Business unitSecurity Role hierarchy / sharing— rebuild
RecordGUID AnyDynamics_ID__c (external ID) req direct

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.