Migrate from Salesforce Sales Cloud to Microsoft Dynamics 365 Sales

Salesforce Account maps directly to Dynamics 365 Account. The primary key mapping uses AccountId-to-accountid with Name, Industry, AnnualRevenue, Type, and BillingAddress migrating as standard fields. Parent-Account hierarchies require a recursive import pass: we import top-level Accounts (where ParentId is null) first, then resolve parent IDs and import child Accounts. The relationship preserves the hierarchy depth up to Dynamics 365's ten-level limit, which covers the vast majority of Salesforce org hierarchies.

Salesforce Contact maps to Dynamics 365 Contact with a critical relationship difference to resolve. Salesforce supports many-to-many Contact-to-Account relationships via the Account Contact Relation junction object; Dynamics 365 uses a primary AccountId on Contact with the Connection entity for secondary relationships. We import Contacts with their primary AccountId set, then replay secondary Account relationships as Connection records (fromcontacts and toaccounts) in a second pass. Email, Phone, Title, and custom contact fields migrate directly.

Salesforce's Account Contact Relation junction table (which enables a Contact to belong to multiple Accounts with roles) maps to the Dynamics 365 Connection entity. Each Account Contact Relation record becomes a Connection with Record1Id pointing to the Account and Record2Id pointing to the Contact, with a custom Connection Role reflecting the original Account Contact Relation roles field. This second-pass migration runs only after both Accounts and Contacts are committed to Dataverse.

Salesforce Lead maps directly to Dynamics 365 Lead with field-level mapping of Name, Company, Email, Phone, LeadSource, Status, Rating, and custom fields. Salesforce Lead Status values map to Dynamics 365 Lead Status values via a pre-migration value map. If the source org uses Lead conversion mapping to auto-create Contacts and Accounts on conversion, we map the pre-conversion Lead record to the Dynamics 365 Lead and set the converted-flag fields accordingly.

Salesforce Opportunity maps to Dynamics 365 Opportunity with Stage, Amount, CloseDate, Probability, Description, and OwnerId fields. The OwnerId maps to the Dynamics 365 Owner (User) entity. Opportunity Record Type maps to Dynamics 365 Opportunity Type or a custom field if multiple sales processes are in use. Multi-currency Opportunities from Salesforce with CurrencyIsoCode map to Dynamics 365 TransactionCurrency with the appropriate exchange rate context.

Salesforce Opportunity Contact Role junction records map to the Contact's opportunitycustomeraccountcontact role relationship in Dynamics 365. The Contact's primary role on the Opportunity is set via the Role field on that relationship. If a Salesforce Opportunity has multiple Contact Roles, we set the first Contact as primary and store additional roles in a custom field or notes for the customer's admin to distribute post-migration.

Salesforce Product2 records map to Dynamics 365 Product (the Dataverse product table). ProductCode from Salesforce maps to ProductID (the product number field). We import Products before Pricebook Entries and before Opportunity Line Items so that the product reference is available at line-item import time. Status field (Active/Inactive) maps to Statecode (Active/Inactive) in Dataverse.

Salesforce PricebookEntry maps to Dynamics 365 ProductPriceLevel within a Price List (which replaces Salesforce Pricebook). The StandardPrice from PricebookEntry maps to the Amount (default) field on ProductPriceLevel. We import the default (standard) Pricebook as the base Price List first, then create product price levels for each product in the catalog, then set the IsStandardPrice flag for the standard price level.

Salesforce Opportunity Line Item maps to Dynamics 365 OpportunityProduct. We resolve the parent Opportunity's OpportunityId, the Product's ProductId, and the PriceList's TransactionCurrencyId at migration time. Quantity, UnitPrice, and TotalPrice migrate as Quantity, PricePerUnit, and LineItemAmount. Discount (percent or amount) maps to the ManualDiscountAmount or ManualDiscountPercent field depending on the source field type.

Salesforce Case maps to Dynamics 365 Case (internally the Incident table in Dataverse). Case Status, Priority, Origin, and Subject fields migrate directly. The Contact and Account lookups resolve via the Contact and Account IDs established in the earlier passes. If Salesforce Cases have nested Case Comments, these migrate as Dynamics 365 Case Articles or as Note records attached to the Case depending on the customer's preference.

Salesforce Campaign maps to Dynamics 365 Campaign with CampaignName, Type, Status, BudgetedCost, and StartDate/EndDate fields. Campaign Members (Contacts and Leads linked to the Campaign) map to Dynamics 365 Campaign Activity Members or to a custom Campaign Member entity. If the source Campaign uses Campaign Member Status values, we map these to Dynamics 365 Campaign Response status values.

Salesforce Contract maps to Dynamics 365 Contract with StartDate, EndDate, ContractTerm, Status, and the AccountId lookup. If the source org uses Salesforce Contracts with the Field Mapping XML feature for parent-to-contract mappings from Opportunity or Order, we document those mappings in the handoff package and the customer rebuilds the equivalent logic in Dynamics 365 using Power Automate or the native contract creation workflow.

Salesforce Task maps to Dynamics 365 Task with Subject, Status, Priority, ActivityDate, and Description fields. OwnerId resolves to the Dynamics 365 Owner (User). If the Task has a WhatId pointing to an Account, Opportunity, or Case, we resolve the Dataverse record ID at migration time. Salesforce TaskSubtype (Call, Email, etc.) maps to a custom field in Dynamics 365 since the native Task record type does not include a TaskSubtype attribute in the same way.

Salesforce Event maps to Dynamics 365 Appointment with Subject, StartDateTime, EndDateTime, Location, and Description. The Dynamics 365 Appointment is a subset of the fuller calendar Event entity which also covers non-appointment events; we use the Appointment entity for calendar-bound events and map remaining Event fields to custom fields where the native Appointment schema does not support them.

Salesforce ContentDocument (files attached to records via ContentDocumentLink) maps to Dynamics 365 Annotation records with a documentbody binary attachment. The Annotation is linked to the parent record via the objectid field in Dataverse. We resolve the parent record ID at migration time so that the document attachment lands on the correct Account, Contact, Opportunity, or Case in Dynamics 365.

Salesforce Custom Objects (with __c suffix) map to Dataverse Custom Tables with the corresponding schema. We pre-create the destination custom table in Dataverse using the Power Platform admin center or the Dataverse API, including all custom columns, lookup relationships, and option set values, before migrating any data. Custom table naming follows Dataverse conventions and we preserve the Salesforce API name in a field or in documentation for the customer's admin.