Migrate from Sales ERP to Microsoft Dynamics 365 Business Central

Salesforce Account maps directly to Dynamics 365 Account. We use Account Name as the primary match key, with Website and BillingAddress as secondary dedupe fields. Parent Account hierarchies migrate as Account.ParentAccountId lookups resolved against the stored Salesforce Account ID in a reference field. Ownership maps from Salesforce OwnerId to Dynamics 365 OwnerId systemuser via email match. Multi-currency Accounts require CurrencyId resolution if the Dynamics 365 destination has a multi-currency configuration enabled.

Salesforce Contact maps to Dynamics 365 Contact with AccountId resolved to the target Account.ID before insert. We run deduplication on email address during transform. Salesforce's Account Contact Relation (ACR) object has no direct Dynamics 365 equivalent; we flatten primary-contact relationships into Contact.ParentCustomerId on the Contact record. Secondary contact roles are stored in a custom Contact Relationship entity in Dynamics 365 if the customer requires that granularity.

Salesforce Opportunity maps to Dynamics 365 Opportunity with StageName mapped to Dynamics StatusReason on the Opportunity entity. Probability migrates to an integer field; if Salesforce uses non-integer probabilities (e.g., 37%), we round to the nearest supported integer or store the original value in a custom field. OwnerId resolves to Dynamics OwnerId via email match. RecordTypeId on Salesforce maps to Dynamics opportunitycustomerassuranceprocessid if multiple sales processes are configured.

Salesforce Lead maps to Dynamics 365 Lead with LeadSource, Status, Industry, and Rating preserved. We preserve any custom lead scoring fields in Dynamics 365 custom fields. Salesforce Lead conversion produces Account, Contact, and Opportunity in Salesforce; Dynamics 365 Lead qualification creates the same downstream records via the Qualify action on the Lead entity. We document the qualification rule mapping during scoping.

Salesforce Order maps to Microsoft Dynamics 365 Sales Order (Business Central) or Order entity (Microsoft Dynamics 365 Sales CRM). The mapping depends on whether the destination includes the ERP layer. Order status (Draft, Activated, Fulfilled, Cancelled) maps to the corresponding Dynamics status codes. OrderItems map to SalesOrderLine records with LineAmount, Quantity, and ProductId resolved against the target Product entity. We flag whether the customer needs historical closed orders migrated or only open/active orders.

Salesforce Contract maps to Dynamics 365 Business Central Agreement or CRM Contract entity depending on the deployed ERP layer. StartDate, EndDate, Status, and Renewal Terms migrate as standard fields. Contract-Order lineage from Salesforce (Orders linked to Contracts) requires the Contract ID to be preserved in a reference field so that the relationship can be rebuilt in Dynamics 365's ERP layer after migration.

Salesforce Product2 maps to Dynamics 365 Product. ProductCode (hs_sku equivalent) becomes the Dynamics ProductNumber. IsActive in Salesforce maps to StateCode (Active/Inactive). We validate that all migrating products have at least one active price list entry in the destination before completing the product phase; missing price list entries are flagged as a reconciliation item.

Salesforce PricebookEntry maps to Dynamics 365 ProductPriceLevel (CRM Sales) or SalesPrice (Business Central ERP). Each Pricebook in Salesforce becomes a PriceList in Dynamics 365. UnitPrice migrates to Amount. We resolve Pricebook2Id to the target pricelevelid before inserting price list entries. Custom Pricebook-specific pricing requires explicit mapping because Dynamics 365 separates price list assignment from product pricing more strictly than Salesforce does.

Salesforce Case maps to Dynamics 365 Customer Service entity Incident. Case Status maps to Incident statecode and statuscode. Case Origin maps to a custom field or the Priority field if the destination does not use Origin. AccountId and ContactId lookups resolve to Dynamics Account and Contact before Case insertion. Entitlement and SLAs from Salesforce require mapping to Dynamics 365 Service Level Agreement entities; we flag any entitlement-specific fields that cannot map to standard Dynamics fields.

Salesforce Campaign maps to Dynamics 365 Campaign with CampaignType, Status, BudgetedCost, and StartDate preserved. Campaign Member migration requires resolving the CampaignMember's Contact or Lead reference to the migrated Dynamics 365 record. Custom Campaign fields (e.g., regional codes, campaign budget categories) map to Dynamics custom fields on the Campaign entity. Campaign hierarchies map to Dynamics 365 Campaign Parent Campaign ID lookups.

Salesforce User records map to Dynamics 365 SystemUser by email address match. We extract all Users referenced as OwnerId on migrating records before migration begins. Users without a match in the Dynamics 365 destination org are placed in a reconciliation queue for the customer's admin to provision. Deactivated Salesforce Users are not migrated by default to avoid consuming Dynamics 365 licenses.

Salesforce custom objects (API Name ending in __c) map to Dynamics 365 custom entities created via a solution or the Power Apps maker portal. We pre-create the destination entity schema—including all attributes, lookup relationships, and option set values—before any custom object records are imported. Custom field types (picklist, multi-select picklist, formula, roll-up summary) require type-by-type mapping decisions during discovery because Dynamics 365 does not support all Salesforce field type equivalents (e.g., Salesforce formula fields must be computed in Power Automate or as calculated columns in Dataverse).

Salesforce Attachment records migrate to Dynamics 365 Annotation entity with noteType = 1 (attachment). The Base64-encoded Body from Salesforce maps to the Dynamics documentbody attribute. We validate that Dynamics 365 has sufficient storage quota before attachment migration; if the target environment has SharePoint integration enabled, we prefer file-based document storage via SharePoint libraries rather than Dataverse annotation storage to avoid storage quota exhaustion.

Salesforce Note records migrate to Dynamics 365 Annotation with noteType = 0 (note). Notebody rich text maps to annotation's notetext field. We preserve the parent record reference by resolving the Salesforce ParentId to the corresponding Dynamics record ID via stored original ID lookups before inserting annotations.

Salesforce Task records migrate to Dynamics 365 Task. Subject, Status, Priority, ActivityDate, and Description preserve. OwnerId resolves to Dynamics SystemUser via email match. WhatId (Opportunity, Account, Case reference) resolves via the stored Salesforce original ID lookup table. Tasks linked to custom objects resolve against those custom entity IDs after custom object migration completes.

Salesforce Event records migrate to Dynamics 365 Appointment with Start, End, Location, and Subject preserved. Salesforce Event attendees map to Dynamics 365 Appointment's optionalattendees and requiredattendees party list fields via Attendee resolved against the migrated Contact or User ID. Recurring events (RecurrenceRule) from Salesforce require transformation to the Dynamics 365 recurrence pattern format.

Salesforce OpportunityLineItem maps to Dynamics 365 OpportunityProduct (Sales CRM) or SalesOrderLine (Business Central ERP). The mapping depends on whether the order management layer is in the CRM or ERP application. We resolve the PricebookEntry reference to a Dynamics price list item ID, the Product reference to a Dynamics Product ID, and the Opportunity reference to the migrated Opportunity ID before inserting line items.