---
title: "Dynamics 365 to Salesforce Migration | FlitStack AI"
description: "Migrate Dynamics 365 to Salesforce with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/dynamics-365-sales/to/salesforce-sales-cloud"
---

# Dynamics 365 to Salesforce migration

We migrate Accounts, Contacts, Leads, Opportunities, and Activity history from Microsoft Dynamics 365 Sales into Salesforce Sales Cloud with the Dataverse schema translated to Salesforce field types, the option-set-to-picklist conversion applied during transformation, and every inactive-owner reference resolved against a designated migration account before cutover.

Short answer

FlitStack AI migrates accounts, contacts, leads, opportunities and quotes from Dynamics 365 to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/salesforce-sales-cloud#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Account Contact Lead Opportunity Quote

Mapped field by field · sample run · one-click rollback

## What moves from Dynamics 365 to Salesforce?

Moving from Microsoft Dynamics 365 Sales to Salesforce Sales Cloud is a schema translation as much as a record copy.

Read the full summary

Dynamics 365 uses Dataverse entities with a flat option-set data model; Salesforce uses typed objects with picklists, record types, and a separate Lead-to-Contact conversion lifecycle. We extract from the Dataverse Web API and bulk operations endpoint, transform option sets into Salesforce picklists during the ETL phase, pre-create all custom fields in the destination Salesforce org's UI before any API write, and load through Salesforce's Bulk API with parent-record resolution. Workflows, Power Automate flows, and Dataverse plugins do not migrate; we deliver a written automation inventory for the customer's admin to rebuild in Salesforce Flow. We do not provide post-migration admin support, training, or workflow rebuild as standard scope.

1:1

### Account → Account

Dynamics 365 Accounts map directly to Salesforce Account.

How it maps

The AccountID in Dataverse (accountid GUID) is the primary key for cross-referencing all child records. We use accountid as the external ID field during Salesforce Bulk API upserts so that child Contact and Opportunity records can resolve the AccountId lookup at insert time without a separate lookup pass. Address fields (address1\_line1, address1\_city, address1\_stateorprovince, address1\_postalcode, address1\_country) map to the Account's shipping address fields. If the Dynamics environment uses multiple address records per account, we migrate the primary address and flag multi-address records for the customer's admin to handle in Salesforce.

1:1

### Contact → Contact

Dynamics 365 Contacts map to Salesforce Contact with a required lookup to Account via the parentcustomerid field.

How it maps

We resolve parentcustomerid to the AccountId of the matching Salesforce Account at migration time. Email address (emailaddress1) maps to Contact.Email and is used as the deduplication key. The contact's preferredcontactmethodcode (Email, Phone, Mail, Fax) has no direct Salesforce equivalent; we store it in a custom field preferredcontactmethod\_\_c. Mobile phone (mobilephone) maps to Contact.MobilePhone. Birthdate (birthdate) maps to Contact.Birthdate only if the field exists as a standard or custom field in the destination schema.

1:1

### Lead → Lead

Dynamics 365 Leads map directly to Salesforce Lead.

How it maps

The lead's statecode (Open, Qualified, Disqualified) and statuscode map to Salesforce Lead Status values. Lead scoring fields (leadqualityscore,leadsource) map to custom fields or standard Lead Source. If the Dynamics Lead has been disqualified and the customer wants to preserve that history, we set Lead Status to Closed-Not Converted with a Disqualified reason custom field rather than importing as an open Lead. The lead's parentcontactid reference is preserved as a custom field lead\_parentcontactid\_\_c for post-migration reconciliation.

1:1

### Opportunity → Opportunity

Dynamics 365 Opportunities map to Salesforce Opportunity with the accountid reference resolved to the Salesforce AccountId and the owning user reference resolved to a Salesforce UserId.

How it maps

The estimatedvalue field maps to Amount; closeprobability maps to Probability; actualclosedate maps to Close Date; stepname maps to StageName. Loss Reason and Win Reason from Dynamics custom fields map to custom Salesforce fields. Pipeline and territory assignments from Dynamics map to Salesforce Record Types and the Opportunity's sales\_team\_\_c custom field. We validate that every Opportunity has a resolved AccountId before insert to avoid orphaned opportunities.

1:1

### Quote → Quote

Dynamics 365 Quotes map to Salesforce Quote with the customerid reference (account) and opportunityid reference (opportunity) resolved to Salesforce IDs at migration time.

How it maps

The quotenumber, name, effectivefrom, effectiveto, totalamount, and discount fields map directly. Quote line items (quotedetail) map to QuoteLineItem with the productid reference resolved to a Salesforce Product2 ID. We pre-create all Salesforce Pricebook2 records matching the Dynamics price list names before Quote migration begins so that Pricebook2Id is available at QuoteLineItem insert.

1:1

### SalesOrder → Order

Microsoft Dynamics 365 Sales Orders map to Salesforce Order with the accountid resolved to Salesforce AccountId and the opportunityid resolved to Salesforce OpportunityId.

How it maps

The ordernumber, name, datefulfilled, and totalamount fields map directly. Order products (salesorderdetail) map to OrderProduct with the productid resolved to a Salesforce Product2 ID. The order's status (Pending, Invoiced, Cancelled, Completed) maps to Salesforce Order Status with a pre-configured StatusCode mapping in the transformation layer.

******What moves 16 objects

Dynamics 365 Salesforce

- Account Account 1:1
- Contact Contact 1:1
- Lead Lead 1:1
- Opportunity Opportunity 1:1
- Quote Quote 1:1
- SalesOrder Order 1:1

\+ 10 more in the mapping below

## How Dynamics 365 and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension             | Dynamics 365                                                                                    | Salesforce                                                                                                                       |
| --------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Lead-to-Contact model | Single Lead entity with a qualification status field and stage progression                      | Separate Lead and Contact objects with an explicit Convert action that creates an Account-Contact-Opportunity record chain       |
| Commercial documents  | Quotes, Orders, and Invoices as a chained entity sequence with parent Opportunity reference     | Quotes, Orders, and Invoices as independent objects with Opportunity lookup and a separate OrderProduct/InvoiceLine object model |
| Custom fields         | Custom fields created in the Dynamics 365 UI first, then populated via Web API                  | Custom fields created in Salesforce Setup UI first, then populated via Bulk API or REST                                          |
| Custom table limit    | 15 custom tables hard cap on Professional tier; unlimited on Enterprise                         | Custom objects available from Professional tier ($80/user/mo) without per-object fees                                            |
| Activity storage      | Activities stored in Dataverse as ActivityPointer and typed subtypes (Task, Email, Appointment) | Activities split across Task, Event, and EmailMessage objects with separate WhatId and WhoId lookups                             |
| Territory management  | Territory hierarchy on Enterprise tier only; defined in Sales Territory settings                | Territories modeled as a separate object with a Territory2 data model, or as geographic fields on User and Account               |
| Pricing history       | October 2024 increase of $15/user/month applies at renewal for all existing customers           | Sales Cloud Professional at $80/user, Enterprise at $165/user, with no recent mandatory price increase for existing customers    |

## What to watch for in a Dynamics 365 to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Professional tier 15-table cap blocks custom table migration

Sales Professional enforces a hard cap of 15 custom tables.

How we handle it

If the source environment exceeds 15 custom tables, records referencing tables above the limit cannot be imported without either a Dynamics 365 Enterprise license upgrade or schema simplification before migration. We detect the exact count during scoping and present the customer with a concrete list of tables to merge, drop, or map to existing Salesforce standard objects. This step must be resolved before schema pre-creation in Salesforce begins; proceeding without it results in a blocked migration at the custom table boundary.

high

### Option sets have no direct Salesforce field type

Dynamics 365 option sets (stored as integer values with a label map in the metadata) do not map directly to any Salesforce field.

How we handle it

A Dynamics option set field like statecode with values 0=Open, 1=Qualified, 2=Disqualified must be transformed to a Salesforce picklist with string values during the ETL phase, or the integer values must be preserved in a custom number field with a separate value mapping document. We extract the OptionSetMetadata during scoping, generate a picklist mapping table, and apply it during transformation. Skipping this step results in integer values appearing in Salesforce picklists that don't match any defined picklist value.

medium

### Custom fields must be pre-created in Salesforce UI

Dynamics 365 does not allow creating custom fields via the Web API alone; you must create them through Advanced Settings or a solution in the Dynamics UI, publish them, and then use the API to populate values.

How we handle it

Salesforce has the same constraint: custom fields must be created in the Setup UI before API writes. We coordinate with the customer's Salesforce admin to pre-create all target custom fields (including those from Dynamics custom tables and extended option sets) before our Bulk API import job runs. Any missing field causes the entire batch to fail with a field-not-found error, so this step is a hard prerequisite.

medium

### Dataverse rate limits cap bulk export throughput

The Power Platform enforces per-user and per-environment request limits that cap how many Dataverse API calls can be made per day.

How we handle it

For large migrations with hundreds of thousands of records, this can throttle the export phase significantly. We use Dataverse batch operations (up to 25 records per batch) with configurable concurrency limits and run export jobs during off-peak hours. If the environment is heavily used concurrently, we negotiate a dedicated migration window with the customer's IT team. On the Salesforce side, Bulk API 2.0 handles ingestion with its own chunking and backoff logic, but we must ensure the Dataverse export does not become the bottleneck.

medium

### SharePoint attachment extraction requires SharePoint authentication

Dynamics 365 file attachments are stored in SharePoint Online (modern) or Dataverse blob storage (legacy).

How we handle it

Modern SharePoint attachments require OAuth2 authentication against the customer's Azure AD tenant to download files for ContentDocument migration. We request SharePoint site read access during scoping, extract the relative file path from each SharePointDocument URL, and download the file content before creating Salesforce ContentVersion records. Legacy Dataverse attachments stored in documentbody (base64) can be extracted directly via the Dataverse API without additional authentication. We identify the attachment storage pattern during scoping.

## How the migration runs

1. ### Dataverse schema discovery and scoping

   We connect to the source Dynamics 365 environment via the Dataverse Web API using an OAuth2 service account and perform a full entity metadata export.

   What this step covers

   This captures all standard and custom entity schemas, attribute data types, option set value mappings, lookup relationships, and ownership metadata. We produce a Schema Inventory document listing every entity, every custom field, every option set with its value-to-label map, every custom table above the 15-table threshold, and every SharePoint document location. This document is the foundation for all subsequent mapping and transformation design.

2. ### Migration account provisioning and permission setup

   We provision a dedicated migration user account in Salesforce with API-access permissions (API Enabled, Bulk API 2.0, REST API), the Modify All Data system permission, and object-level create/edit/read access for every object in scope.

   What this step covers

   We also configure the migration user's profile to bypass validation rules during the data load phase, either by adding a migration-context checkbox to each rule's condition or by temporarily disabling rules in a Salesforce permission set that is deactivated after cutover. On the Dynamics 365 side, we provision a Dataverse service account with read access to all entities and the ability to use batch operations.

3. ### Salesforce schema pre-creation

   We pre-create all Salesforce custom objects (\_\_c API names), custom fields, picklist value sets (mapped from Dynamics option sets), Record Types (one per Dynamics price list or pipeline), Sales Processes (stage whitelist per Record Type), and Page Layouts in a Salesforce Sandbox before any data moves.

   What this step covers

   Custom fields include a migration\_flag\_\_c boolean we set to true on all migrated records so that data stewards can filter migrated vs native records in reports. The customer reviews and approves the schema in Sandbox, and we deploy it to the destination production org via metadata API before the production migration window opens.

4. ### Sandbox migration and reconciliation

   We run a full migration into a Salesforce Full Copy or Partial Copy Sandbox using production-like data volumes extracted from Dataverse.

   What this step covers

   The customer's RevOps lead reconciles record counts (Accounts in, Contacts in, Leads in, Opportunities in, Quotes in, Orders in, Activities in, custom objects in), spot-checks 30-50 records per object against the Dynamics source, and verifies that option set values render correctly as picklist labels in Salesforce. Any field mapping corrections, picklist value set adjustments, or custom field additions happen in Sandbox before production migration begins.

5. ### Owner reconciliation and User provisioning

   We extract every distinct ownerid (Dynamics User GUID) referenced on Accounts, Contacts, Leads, Opportunities, Quotes, Orders, and Activities and match by email against the Salesforce destination org's User table.

   What this step covers

   Any owner without a matching Salesforce User goes to a reconciliation queue. The customer's Salesforce admin provisions missing Users (active for users who will remain licensed, inactive for departed users) before record migration continues. Inactive Dynamics owners are mapped to a designated migration admin User in Salesforce so no record is created without an owner. This step gates all subsequent record imports because OwnerId is a required field on most standard objects.

6. ### Production migration in dependency order

   We run production migration in record-dependency order.

   What this step covers

   Accounts (from Dynamics Accounts, no parent dependency). Contacts (with AccountId resolved from the Account mapping). Leads (standalone, no parent required until conversion). Pricebook2 (Salesforce standard pricebook pre-created; custom pricebook2 created per Dynamics price list). Product2 (with PricebookEntry created per product-pricebook pair). Opportunities (with AccountId, OwnerId, and RecordTypeId resolved). Quotes (with AccountId and OpportunityId resolved, QuoteLineItem with product and pricebook resolved). Orders (with AccountId and OpportunityId resolved, OrderProduct with product resolved). Activities (Tasks, Events via Bulk API 2.0 with WhoId and WhatId resolved). Custom Objects (last, with all parent-lookup references resolved). Notes and Attachments (via ContentVersion/ContentDocument). Each phase emits a row-count reconciliation report and a field-sampling validation report before the next phase begins.

7. ### Cutover, delta sync, and automation rebuild handoff

   We freeze Dynamics 365 writes at cutover, run a final delta migration of any records modified or created during the production migration window, and enable Salesforce as the system of record.

   What this step covers

   We deliver the Automation Inventory document listing every active Power Automate flow, plugin step, and business rule in Dynamics 365 with its trigger, conditions, and a recommended Salesforce Flow equivalent. Workflow rebuilds are outside standard migration scope; the customer's admin or a Salesforce implementation partner handles them as a separate engagement. We provide a one-week hypercare window to resolve post-migration reconciliation issues raised by the sales team.

![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365 ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Salesforce Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**8-14 weeks** Large or heavily customised accounts

A quote scales with record volume, custom table count, and the option-set-to-picklist transformation workload. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Dynamics 365 to Salesforce →](https://flitstack.ai/contact)

## Why teams move from Dynamics 365 to Salesforce

- Microsoft's October 2024 pricing increase of $15 per user per month across all Microsoft Dynamics 365 Sales tiers applies at renewal for existing customers, adding $180 per user annually for a 10-person team. Salesforce Sales Cloud Professional at $80 per user offers comparable CRM depth with a stable, non-escalating per-seat price, and teams already evaluating the switch cite the price increase as the renewal-year tipping point that justifies the migration project cost.
- Implementation typically requires a certified Microsoft partner, adding 30-50% to the total project cost beyond licensing. Reviewers on Capterra and Reddit consistently cite partner quality as the difference between a functioning system and a misconfigured one, with no clear remediation path when the partner relationship sours. Salesforce's implementation ecosystem is larger and more competitive, with certified consultants available at lower marginal cost for mid-market migrations.
- Dynamics 365 is purpose-built for Microsoft-first organizations; non-Microsoft integrations require additional configuration or third-party middleware. Teams moving to Salesforce report the AppExchange ecosystem (over 9,000 listings) as a primary driver, particularly for ERP connectors, CPQ tools, revenue intelligence, and contract lifecycle management that exist as first-party or certified integrations rather than bespoke middleware configurations.
- The Professional tier 15-custom-table limit on Microsoft Dynamics 365 Sales traps growing teams into a license ceiling. When a team's data model requires a custom record type (Projects, Subscriptions, Regulatory Records, Asset Registries), they must upgrade to Enterprise at $105 per user per month or simplify the schema. Salesforce Sales Cloud Professional at $80 per user supports custom objects from the first tier, making it the destination of choice for teams that have outgrown the Professional ceiling without wanting to pay for Enterprise.
- Performance degrades in Dynamics 365 with large datasets and complex multi-entity customer journeys, particularly in organizations running multiple Dynamics 365 modules concurrently. Reviewers on G2 and TrustRadius cite slow load times, delayed pipeline updates, and reporting lag as the reason they moved to Salesforce for a cleaner, more responsive CRM experience at scale.

Questions, answered

## Dynamics 365 to Salesforce migration questions

How long does a Microsoft Dynamics 365 Sales to Salesforce migration take?

Small migrations with normalized data, fewer than 10 custom tables, and straightforward Account-Contact-Opportunity structures typically complete in three to five weeks. Larger migrations with 20+ custom tables, a full commercial document chain (Quotes, Orders, Invoices), activity histories exceeding 200,000 records, or a territory hierarchy requiring Territory2 setup move to eight to fourteen weeks. The sandbox validation phase alone adds one to two weeks to any migration scope because schema corrections must be validated in a non-production environment before production data moves.

Do Dynamics 365 workflows, Power Automate flows, and plugins migrate to Salesforce Flow?

No. Power Automate cloud flows, Dataverse plugins, and business rules are configured at the platform level and do not have a standard portable representation. We do not migrate them as code. We deliver a written Automation Inventory document listing every active Power Automate flow and plugin step with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce implementation partner rebuilds them post-migration as a separate engagement. Dynamics 365 business rules (field-level validation and visibility logic) are similarly not migrated.

Do we lose historical activities (emails, calls, meetings, tasks) during migration?

No. We migrate the full activity history through Salesforce's Bulk API 2.0 with WhoId and WhatId parent-record resolution. Emails land as Task records with TaskSubtype=Email and the body preserved in Description. Calls land as Task with TaskSubtype=Call and CallDurationInSeconds. Meetings land as Event records with StartDateTime and EndDateTime preserved. Tasks land as Task with Status, Priority, and ActivityDate. Activity timeline ordering is preserved by setting ActivityDate to the original Dynamics timestamp. SharePoint-stored attachment files migrate as Salesforce Files (ContentVersion/ContentDocumentLink) with the original filename and creation date preserved.

How do we handle Dynamics 365 option sets during migration?

Dynamics 365 option sets store integer values with a label defined in the entity metadata. These must be converted to Salesforce picklist string values during the ETL transformation phase. We extract the OptionSetMetadata for every Dynamics option set field during scoping, generate a picklist mapping table (value, label, isdefault), and apply it during transformation. The result is a Salesforce picklist with correctly labeled values. If a Dynamics option set uses a global option set shared across multiple fields, we create a global value set in Salesforce and assign it to each dependent picklist field during schema pre-creation.

Our Dynamics environment uses more than 15 custom tables on Professional tier. What do we do?

If the source environment has more than 15 custom tables, the Professional tier cap means tables 16 and above cannot be imported without either upgrading to Enterprise (unlimited custom tables) or simplifying the schema before migration. We present a Schema Simplification Options document during scoping listing every custom table above the threshold, the record counts in each, and the foreign-key relationships between them. Common approaches are merging related custom tables into one, mapping one custom table to a Salesforce standard object (for example, a custom Project table maps to Salesforce's native Opportunities with a record type), or archiving retired custom tables. We do not recommend upgrading the Dynamics license for the sole purpose of migrating additional custom tables if the destination already supports unlimited custom objects from Professional tier.

Can we migrate only specific business units or territories instead of the entire Dynamics environment?

Yes. We support partial-migration scoping by business unit, territory, owner, or record date range. We apply a Dataverse filter (ownerid in @teamMembers, territoryid in @targetTerritories, or createdon between @startDate and @endDate) during the extraction phase to pull only the relevant subset of records. The owner mapping, Account-Contact-Opportunity dependency chain, and custom table mapping remain the same. Partial migrations are appropriate when a subsidiary, regional team, or product line is moving to Salesforce while the rest of the organization remains on Dynamics 365. We flag any cross-referenced records from excluded business units so the customer can decide whether to include them or accept orphaned lookups.

What happens to our SharePoint-stored documents after migration?

Dynamics 365 documents stored in SharePoint Online are downloaded during migration and uploaded as Salesforce Files (ContentVersion/ContentDocument) linked to the parent CRM record. The original SharePoint location is preserved in a custom field (sharepoint\_url\_\_c) on the ContentDocument so that the migration admin can decide whether to maintain the SharePoint copy, migrate it to Salesforce Content, or leave it in place and update the SharePoint links post-migration. We do not delete the SharePoint documents; document deletion is outside migration scope. The customer controls whether the SharePoint site remains active post-migration.

## Related migrations

[![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) Migrate to **Salesforce** Every source we move into Salesforce, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

[Set up Salesforce and migrate into it as one engagement.](https://flitstack.ai/services/salesforce-implementation)

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Salesforce to Dynamics 365** The same pair in reverse](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/dynamics-365-sales) [**Snovio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/snovio/to/salesforce-sales-cloud) [**Clio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/clio/to/salesforce-sales-cloud) [**Dubsado to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dubsado/to/salesforce-sales-cloud) [**Aweber to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/aweber/to/salesforce-sales-cloud) [**LeadSimple to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/leadsimple/to/salesforce-sales-cloud) [**ServiceTitan to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/servicetitan/to/salesforce-sales-cloud) [**Dynamics 365 to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/freshsales) [**Dynamics 365 to monday CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/monday-crm) [**Dynamics 365 to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/zoho-crm)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
6. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
7. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)

Get a quote

## Moving from Dynamics 365 to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
