Skip to content
Get a quote

Migrate to Dynamics 365

Dynamics 365 Sales sits on top of Dataverse and the Power Platform, which means a migration is really five projects — schema modelling, security roles, server-side automation, client scripts, and an environment-promotion plan — running in parallel.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Dynamics 365 from 850+ CRMs, including Salesforce, Mailchimp, Zoho CRM, Odoo CRM. Every field is mapped to Dynamics 365's objects, history and associations come across, the Dynamics 365 setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationDynamics 365
SalesforceMailchimpZoho CRMOdoo CRMHubSpot
850+ sources mapped into Dynamics 365

What Dynamics 365 supports, and where its import tools stop

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
Bulk APIOAuth 2.0 via Microsoft Entra ID (formerly Azure AD)
Rate limitsPer-user and per-environment request limits enforced across Power Platform; exact limits vary by license tier and environment capacity
ObjectSupportNote
AccountsfullAccounts (called 'Companies' in some CRM products) is the core organizational record in Microsoft Dynamics 365 Sales . We map it 1:1 for most CRM migrations, preserving the primary contact association and industry classification fields. We flag duplicate account names during import scoping.
ContactsfullContacts store individual people linked to Accounts. We preserve the parent Account lookup, email addresses, phone numbers, and lifecycle stage fields. Contact ownership maps directly to Owner/User records in the destination CRM.
LeadsfullLeads are the top-of-funnel records with a distinct lifecycle from Opportunity. We preserve lead scoring, source attribution, and qualification status fields. If the destination CRM has no separate Lead object, we merge into Contacts and preserve Lead_Status as a custom property.
OpportunitiesfullOpportunities track deals tied to an Account and Contact with estimated close dates, amounts, and pipeline stage. We preserve the estimated revenue, probability, and stage-history timeline. Loss reasons and won-close dates map cleanly to standard destination fields.
Quotes, Orders, and InvoicesfullThese three entities form the commercial document chain: Quote converts to Order, Order invoices out. We preserve the parent Account and Opportunity lookups, line items with product references, and pricing after applying discount fields. The ordering of this chain is maintained during migration.
Products and Price ListsfullProducts are the sellable items with ID, name, and pricing. Price Lists define pricing tiers per product with quantity-based discounts. We map these as a pair and preserve the price-list assignment on Quotes, Orders, and Opportunities. Bundle relationships are preserved as sub-item references.
Activities (Tasks, Emails, Phone Calls, Appointments)mappedActivities are timestamped engagement records attached to any CRM entity. We preserve the activity type, subject, description, date, and owner. Outlook-email correlation requires matching on sender/recipient email addresses since Dynamics does not store a stable email GUID across migrations.
Custom Tables (Professional Tier Limit)mappedSales Professional caps custom tables at 15; Enterprise and Premium allow unlimited custom tables. We detect the current tier during scoping and flag any custom table above the 15-table threshold as requiring an Enterprise license at the destination or schema simplification before migration.
TerritoriesmappedTerritory management is available on Enterprise tier only. We map territory names and hierarchies but note that destination CRMs often model territories differently—as geographic fields, list values, or separate lookup tables. Field-level mapping is required per customer.
Users and OwnersfullUser records represent licensed individuals who own CRM records. We map Users to their corresponding Owner records in the destination, preserving full name, email, and business unit assignment. Inactive users require explicit handling: we flag records orphaned to inactive owners before migration.
Notes and AttachmentsmappedNotes are text annotations stored in Dataverse; Attachments are files in associated SharePoint locations or Dataverse. We extract notes as plain text and download attachments from SharePoint or blob storage for re-upload to the destination, handling any filename encoding issues along the way.
Workflows and Business RulesnoneBusiness rules (field-level validation and visibility logic) and Power Automate workflows are configured at the platform level and do not have a standard portable representation. These must be rebuilt manually or via a certified Microsoft partner at the destination. We document the active rules during scoping for customer reference.
Reports and DashboardsnoneReports built in Dynamics 365 use FetchXML or Power BI and are tied to specific entity contexts. These are not migrated. We export the list of active reports and dashboards during scoping so customers can rebuild them in the destination system.

The Dynamics 365 migration guide

Why teams migrate to Microsoft Dynamics 365 Sales

The four shapes a Dynamics 365 Sales migration takes, and what makes the platform harder — or easier — than the category average.

Microsoft Dynamics 365 Sales is the sales application inside Microsoft's broader Dynamics 365 business-applications suite, sitting alongside Customer Service, Field Service, Customer Insights and Finance & Operations. All of them store their data in Dataverse — the Microsoft-managed relational layer formerly called the Common Data Service — and run on top of the Power Platform111.

The typical Sales customer is a mid-market or enterprise revenue team that already lives inside Microsoft 365: Outlook for email, Teams for collaboration, SharePoint for documents, Azure AD for identity. Compared with Salesforce Sales Cloud, Dynamics 365 Sales positions on Microsoft-native integration and Copilot reach into Office; compared with HubSpot or Pipedrive, it positions on enterprise-grade extensibility through plug-ins and Power Automate flows5.

The shapes of migration that actually land on Dynamics 365 Sales tend to fall into four patterns. First, Salesforce exits, driven by total cost of ownership at the Enterprise tier and by teams that want their CRM closer to Microsoft 365 and Power BI. Second, on-premises Dynamics CRM cloud moves, where customers running Dynamics CRM 2015/2016 or Customer Engagement on-premises shift to the online Dataverse-backed product.

Third, consolidation projects: a business standardising on the Microsoft stack and replacing Pipedrive, HubSpot, Zoho or homegrown systems with Sales plus Customer Service plus Customer Insights on a single Dataverse. Fourth, M&A integration, where an acquirer pulls the acquired company off a different CRM onto its existing Dynamics environment. A Salesforce exit has rich automation that does not move as code; an on-prem Dynamics move has clean schema but old plug-ins that need rewriting against the current platform.

What makes migrating to Dynamics 365 Sales harder than the category average is the platform's extensibility surface. There are five places business logic can live — Business Process Flows, classic Workflows, server-side Plug-ins, Power Automate cloud flows, and client-side JavaScript — and a migration has to decide which layer rebuilds each piece of legacy logic.

Add Dataverse security roles, Business Units and Teams on top, and the schema is only half the project. The native Data Import Wizard caps individual files at 8 MB (32 MB for .zip) and Microsoft itself recommends limiting import jobs to 20,000 rows — anything bigger is supposed to go through SSIS, not the wizard1314.

What makes it easier is template-based imports straight from the system, mature duplicate-detection rules across Accounts, Contacts and Leads, and a Dataverse model that already speaks the standard CRM vocabulary — Lead, Account, Contact, Opportunity, Quote, Order, Invoice96. Teams that scope the five automation layers and the security model up front finish on time; teams that treat it as a CSV-shaped project do not.

Schema is half the project. Security roles, plug-ins, flows and Business Process Flows are the other half.

The Dataverse data model you need to map into

Tables, columns, relationships, and the alternate-key mechanics you will wire on every field — the destination schema decoded.

Dynamics 365 Sales does not have its own data layer. Every record lives in a Dataverse table (formerly called an entity), and Sales ships a curated set of standard tables that the application's forms, views and Business Process Flows are bound to111.

Before you can map a single column you need to know which Dataverse table the row belongs on, what columns are required, and which value will serve as the alternate key for upsert. The table below summarises the tables you will touch in a Sales migration.

ObjectWhat it storesRequiredTier
LeadUnqualified inquiry — pre-Opportunity recordTopic (subject); one of First Name + Last Name or CompanyAll Sales SKUs
AccountOrganisations — customers, prospects, partnersAccount Name (primary name)All Sales SKUs
ContactIndividual people associated with Accounts or LeadsLast NameAll Sales SKUs
OpportunityActive deal in pipeline; replaces Lead at qualifyTopic, Potential Customer (Account or Contact)All Sales SKUs
Quote / Order / InvoiceCustomer-facing pricing, sales orders, billed invoicesName, Price List, Opportunity (for Quote)Sales Enterprise+
Product / Price List ItemCatalogue of sellable items and tier pricingProduct Name, Unit Group, Default UnitSales Enterprise+
Activity (Phone Call, Email, Appointment, Task, Letter)Timeline events linked to Leads, Contacts, OpportunitiesSubject, Regarding, Activity TypeAll Sales SKUs
Annotation (Note)Free-text notes with optional file attachmentSubject, Regarding (Object Type Code + ID)All Sales SKUs
Custom tablesCustomer-defined records inside the same DataversePrimary name column; per-column requirementsAll SKUs (storage tier applies)

Every Dataverse record has a system-generated GUID (accountid, contactid, opportunityid) which is the canonical primary key. For migrations, the practical upsert key is an alternate key — a column you mark as unique on the table definition, then use as the entity reference when upserting.

Set up alternate keys on Account (often the legacy crm_source_id or website domain), Contact (legacy ID or email), and any custom table before the first row goes in — adding an alternate key after data exists requires Microsoft to build a unique index across what may now be a millions-of-rows table. The column catalogue below covers what you can model and the limits you need to plan around.

Field typeLimitNotes
Single Line of TextUp to 4,000 chars per columnEmail, phone, URL, ticker subtypes available
Multiple Lines of TextUp to 1,048,576 charsStored as nvarchar(max); Rich text is opt-in
Whole Number / Decimal / Float / CurrencyDecimal: 10 precision; Currency uses Exchange RateDecimal is exact, Float is approximate — pick deliberately53
Date and Time / Date OnlyUTC-stored; per-column behavior User Local vs Date OnlyBehavior cannot be changed after data exists in some cases
Choice (Option Set) / Choices (Multi-select)Global vs local; integer value per labelInternal integer value, not the label, is stored
LookupUp to 50 explicit lookups per table (practical guidance)Each lookup is a foreign key to a target table's primary ID
Calculated / RollupMax 10 unique calculated fields per table; max 10 rollups per tableCalculated runs at retrieve; rollup runs on schedule (hourly+)
Columns per table1,000 fields per entity online; 1,023 on legacy on-premCustom + system combined — model defensively from day one

Relationships in Dataverse come in three shapes. One-to-Many (parent-child, e.g. Account → Contact) supports configurable cascading behaviour: on delete, you can choose Cascade All, Cascade Active, Cascade User-Owned, Remove Link or Restrict45. Many-to-One is the inverse, exposed as a lookup column on the child. Many-to-Many is supported natively but stores the relationship in a hidden intersect table that is read-only to external loads — for editable many-to-many you create a manual junction table with two lookups43.

Custom tables participate in relationships the same way standard tables do, including the same cascade options and lookup mechanics. Microsoft Dataverse storage is consumed in three pools — Database (relational rows), File (attachments) and Log (audit) — and the tenant allowance scales with licensed users; teams importing legacy attachments need to size File storage explicitly because it is the pool that fills first.

Pre-migration prep — the work before you touch Dynamics 365 Sales

What must be true on the source, the destination, and across the team before the first row hits the Data Import Wizard.

The single best predictor of a clean Sales migration is how much work you do on the source side before the first import job is queued. Microsoft's own Dataverse guidance is explicit: skipped or rushed testing is one of the most common reasons migrations fail, and the fix is almost always pre-processing rather than post-cleanup.

Treat the source export as raw material that needs to be shaped to Dataverse's expectations — option-set integer values, alternate keys, owner-resolved-to-Azure-AD users, dates in ISO-8601, currencies aligned to the exchange rate.

Source-side prep

  • Audit and dedup the source database before export. Dynamics 365 publishes default duplicate-detection rules for Accounts, Contacts and Leads, but practitioner guidance is to dedup before import so the rules act as a safety net, not the first line of defence.
  • Resolve option-set values to integers, not labels. Every Choice column stores an integer; the label is for display. The wizard will accept some labels via auto-match but programmatic loads expect the integer and fail silently when the label is wrong-cased.
  • Stamp a stable external ID on every record in the source export — the source platform's primary key or a UUID — so you can wire an alternate key on the Dataverse table and re-runs are deterministic.
  • Normalise currencies and exchange rates. Dataverse stores an Exchange Rate per Transaction Currency record; if your source had multi-currency data without a rate column, decide whether you import in base currency or pre-create Transaction Currency rows with historical rates.
  • Decide what is in scope for historical activities. Phone Calls, Emails, Appointments, Tasks and Letters can be imported with a backdated Actual End timestamp, but each one carries the same write cost as a record create66.

Destination-side prep

  • Design the environment strategy — Default, Production, Sandbox, Developer — and pick which one is the data-migration environment. Microsoft explicitly recommends a dedicated data-migration environment because it is a disruptive task that cannot coexist with other testing activities34.
  • Provision users in Azure AD / Entra ID first, assign Dynamics 365 Sales licences, then map them into Dataverse security roles before importing. Owner assignment during import fails silently if the referenced user is not yet a Dataverse user.
  • Build security roles, Business Units and Teams before importing. Owner-based row security is enforced at retrieve, not at write — get this wrong and reps see records they should not, or miss records they should.
  • Pre-create every custom table and column with the correct data type, including alternate keys, calculated/rollup formulas, and Choice option sets with stable integer values.
  • Build the Solution. Wrap your customisations in an unmanaged Solution in the development environment, then export as managed and deploy to the migration and production environments — this is the ALM pattern Microsoft documents for Power Platform11.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 48 to 96 hours for mid-market — and communicate it to every department that touches the CRM. Train sales reps on the Sales Hub model-driven app, Business Process Flows and Outlook + Teams integration before go-live. Microsoft's own guidance pegs small-to-mid migrations at 8 to 12 weeks of elapsed time, with enterprise programmes running 6 to 12 months end-to-end.

Import mechanisms: Data Import Wizard and SSIS

The load paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

Dynamics 365 Sales exposes several load paths and the right one depends on row count, table mix, and whether the load needs to be re-runnable. The Data Import Wizard covers small-to-medium one-shot migrations under 20,000 rows per job. SSIS with KingswaySoft (or equivalent) and the Data Migration Framework sit on top and add transformation, staging and resume-on-failure semantics.

Data Import Wizard

The native import lives in the model-driven app under Settings → Data Management → Imports, or via Advanced Find → Import Data on supported entity grids13. Supported file formats: CSV (.csv), Text (.txt), Compressed (.zip), Excel Spreadsheet 2003 (.xml) and Excel Workbook (.xlsx). The maximum file size is 8 MB for individual files and 32 MB for .zip bundles1314. A .zip can include multiple CSV/XML/TXT files and an optional Attachments folder, all imported as a single job.

The wizard supports a Map Automatically mode that matches columns to table fields by header name, and an explicit Data Map mode that lets you save and reuse mappings across imports. Templates exported from Settings → Templates for Data Import give pre-built XML spreadsheets with the right columns for Accounts, Contacts, Leads and other standard tables. The right call: wizard for one-shot loads under 20,000 rows on standard tables.

SSIS, KingswaySoft, and the Data Migration Framework

For enterprise-scale loads, the most common stack is SQL Server Integration Services (SSIS) plus the KingswaySoft Dynamics 365 connector. SSIS handles transformation, staging tables and resume-on-failure; the connector wraps the Dataverse write path with batch-size tuning, error-row routing and built-in lookups150. The Data Migration Framework (DMF) inside Power Platform admin is the Microsoft-native ETL equivalent and handles configuration data and reference-data loads through entity maps that include concatenation, split and replace transformations14.

Workato, Fivetran, Azure Data Factory and Power Automate are also commonly used in two ways: reverse-ETL where the source platform is staged into Azure SQL or Synapse, transformed in T-SQL, then synced into Dataverse; and ongoing-sync where the tool takes over once the one-time migration is complete.

Mapping your data into Dynamics 365 Sales

The longest section — because field mapping is where almost every migration that fails actually breaks.

Mapping is where every migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether reports work on day two, whether Business Process Flows fire correctly on day five, and whether your sales team trusts the data on day thirty.

Work table by table, top to bottom of the import order: Transaction Currencies first, then Users and Teams, then Accounts (so Contacts and Opportunities can point at them), then Contacts, then Leads, then Opportunities, then Activities, then Annotations and attachments, then custom tables, then Quote/Order/Invoice if in scope150.

Accounts

Common source → Dynamics 365 Sales Account mapping
SourceDestinationNote
company_namename (primary name)Required; max 160 chars on the standard column
website / domainwebsiteurlPlain URL; not used by default duplicate-detection but recommended for an alternate key
owner / account_ownerownerid (lookup to systemuser)Pre-resolve to Azure AD user; assigned to the Business Unit of that user
industryindustrycodeChoice — store the integer, not the label
annual_revenuerevenueCurrency type; respects transactioncurrencyid + exchangerate
parent accountparentaccountid (lookup to account)Second-pass update after all accounts are loaded
legacy_idCustom alternate-key column (e.g. crm_legacy_id)Mark the column unique; this is your re-run upsert key

Contacts and Leads

Sales treats Lead and Contact as distinct tables, not a single dual-status record. A Lead represents an unqualified inquiry; on qualify, the Lead can be converted into an Account, Contact and Opportunity together106146. Decide before mapping whether your source's lead-stage records become Dataverse Leads or Contacts — most migrations split on a Stage = Qualified flag.

Common source → Dataverse Contact mapping
SourceDestinationNote
first_name / last_namefirstname / lastnamelastname is required; firstname optional
emailemailaddress1Lowercase; default Contact duplicate-detection rule keys on this
phonetelephone1E.164 recommended; column is single line of text
account_idparentcustomerid (customer lookup)Polymorphic — lookups both Account and Contact tables
ownerowneridUser or Team reference; resolve against Azure AD email

Opportunities and the Business Process Flow

Opportunities in Sales are not just a record — they are a record bound to a Business Process Flow (BPF) with stages such as Qualify, Develop, Propose and Close106149. The BPF is the visible pipeline-stage indicator on every Opportunity form. When you import an Opportunity you set its statecode (Open / Won / Lost) and statuscode (sub-status), and separately set its position on the BPF via the processid and stageid columns.

If you skip the BPF columns the Opportunity loads but appears at stage 1 of whatever the default Lead-to-Opportunity Sales Process is. For multi-pipeline source systems (Pipedrive, Salesforce, HubSpot), recreate each pipeline as its own custom BPF in Dataverse first, then map source-stage → BPF-stage as part of the Opportunity load.

Common source → Dataverse Opportunity mapping
SourceDestinationNote
deal_name / opportunity_namename (Topic)Required
amount / valueestimatedvalueCurrency type; pair with transactioncurrencyid
close_dateestimatedclosedateDate Only behaviour by default; UTC-stored
stagestageid + statuscodestageid points at a BPF stage row; do not import label text
account / companyparentaccountidRequired for forecasting roll-up
primary contactparentcontactidOptional but recommended for activity timeline
won/loststatecode + statuscodeWon = 1/3, Lost = 2/4 by default; check your environment's options

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the columns used by an active process or report in the last 12 months. Dataverse caps tables at roughly 1,000 columns combined system + custom; once a table is past 600–700 columns the form load times degrade noticeably, and reports built on Dataverse views start hitting the 50-column projection limit.

For Choice columns whose source values do not match, either extend the destination option set with the missing integer values, collapse adjacent values during transform, or introduce a parallel custom column that holds the legacy value verbatim. Calculated and Rollup fields do not import data — Dataverse recomputes them on retrieve or on schedule. Source formulas rebuild as Dataverse calculated fields, and rollup values worth preserving go into a Legacy Rollup number column at import time59.

Historical activities — Phone Calls, Emails, Appointments, Tasks

All five Activity types accept backdated timestamps via the actualend (completed activities) or scheduledend (planned) columns. The visible Timeline date on a Contact or Opportunity reads from modifiedon, not actualend, which catches most teams — the import stamps modifiedon to today and the historical activity appears at the top of the timeline rather than at its true date84.

The fix is to explicitly set modifiedon during import (it is overridable with a privileged service principal) and set overriddencreatedon to the original create date — Dataverse documents this column specifically for backdated migrations66. Activity rows also need an activitypartylist payload to attach the From/To/Cc parties; that party list references either a contact, lead, account or systemuser, and missing references silently drop the activity reference from the timeline.

Files and attachments — Annotations and SharePoint

Attachments in Sales live in the Annotation (note) table — each Note has an optional documentbody (base64 binary), filename, mimetype and filesize. Annotations are associated to a parent record via the objectid + objecttypecode columns. The Data Import Wizard accepts Notes inside a .zip with an /Attachments subfolder; the wizard reads the binary and creates the Annotation row in one pass.

For estates above a few gigabytes the supported pattern is SharePoint integration: enable SharePoint document management in Settings → Document Management, point it at a SharePoint Online site, and store attachments as SharePoint files linked to the Dataverse record rather than as Annotation documentbody blobs. This pushes the storage cost off the Dataverse File pool and onto Microsoft 365 file storage. Tools like Inogic Attach2Dynamics handle bulk-migration of historical Annotations to SharePoint or Azure Blob in one pass.

Audit trail, ownership and original timestamps

Dataverse stamps createdon, createdby, modifiedon and modifiedby on every row. These are overridable on import under specific conditions: the calling identity must have the prvOverrideCreatedOnCreatedBy privilege, and you set the overriddencreatedon column rather than createdon directly83. Standard non-privileged imports get today's timestamp and the importing user as createdby, which silently breaks reports filtered by Created Date.

Owner assignment during import works only if the referenced user or team exists in Dataverse at the moment of write. Rows whose owner cannot be resolved are imported with the importing user as owner, which silently leaks records to anyone whose security role includes that owner's Business Unit85.

Account-level audit logging is enabled per-table under Settings → Auditing; once on, the audit table records every Create, Update and Delete with previous and new values88. Audit data counts against the Log storage pool, which is separate from Database and File storage but still tier-bound — heavy backfill of historical audit rows is not recommended; capture the source-system audit trail into custom Legacy Audit columns instead.

CRM-specific: duplicate detection, sequences, server-side sync

Dynamics 365 ships default duplicate-detection rules for Account (name), Contact (email) and Lead (name + email domain) and lets you author custom rules under Settings → Data Management → Duplicate Detection Rules96100. Microsoft's recommendation during import is to disable duplicate detection on the load and re-enable after, because each duplicate check is a synchronous query that throttles bulk-load throughput badly13.

Sequences (the cadence tool inside Sales Insights) do not have an import mechanism — recreate the structure manually and apply to active leads/opportunities post-cutover. Lead-scoring models likewise do not import; rebuild as predictive lead scoring inside Sales Insights or as a custom Dataverse score column111.

Server-side synchronisation with Exchange Online for email and calendar is configured per user under Settings → Email Configuration → Mailboxes, and should be enabled after the historical activity import, not during — otherwise the connector backfills against the same Activities you just loaded and creates duplicates144.

The pitfalls that derail Dynamics 365 Sales migrations

Nine specific failure modes — ranked by impact, each tied to the exact Dataverse mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and users being allowed in. Microsoft's FastTrack guidance recommends three stages: a 10 percent test load into a sandbox with stakeholder spot-checks, the full load into the migration environment with real-time monitoring of record counts and relationship integrity, and a 30-day post-migration data-quality audit driven by the audit table142. Have department reps verify their own records — they know what right looks like.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

  • Total Accounts imported vs source — minus deliberately excluded rows (test accounts, soft-deleted records, opt-outs).
  • Total Contacts imported vs source, with a count of Contacts where parentcustomerid is null — those are unassociated and should match an explicit list.
  • Total Opportunities per pipeline + BPF stage, plus sum of estimatedvalue per pipeline — a non-trivial currency variance signals a stage-mapping error or a missing Transaction Currency Exchange Rate.
  • Total Activities per type (Phone Call, Email, Appointment, Task, Letter) imported vs source — and a date-bucketed comparison against overriddencreatedon to confirm backdating round-tripped.
  • Relationship counts — Contact→Account, Opportunity→Account, Activity→Regarding by object-type-code — checked against source-derived expected counts.
  • Owner distribution — GROUP BY ownerid and confirm no record landed under the migration service principal that should not have.
  • Alternate-key integrity — count distinct values on each custom alternate-key column; any duplicates indicate the dedup transform missed cases.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across tables and verify each field against the source UI. Pick five high-value Opportunities and trace the full graph — Account, Contacts, Quote, Activities, Annotations. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by their alternate-key column.

Dynamics 365 supports a partial rollback on imports: under Settings → Data Management → Imports, each import job appears as a row with a Delete option that lets you delete only the records created by that import, leaving everything else intact114. This is the closest thing to native bulk-undo, but it is import-job-scoped — deletes only the records that job created, and only if they have not been modified since.

The real rollback strategy remains: export everything to Azure Blob or SharePoint before the import starts, stamp every imported row with an Import Batch ID custom column, and if catastrophe strikes, bulk-delete by that batch ID via Advanced Find or a Power Automate flow and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the dry-run window; (3) delta is imported via the Data Import Wizard or SSIS; (4) reconciliation runs; (5) users get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

Migration partners and tools

Microsoft Solutions Partners, ETL connectors, specialist Dataverse shops — what each is good for and how to choose.

The Microsoft Solutions Partner programme tiers partners by capability and customer count, with a specialisation badge for Business Applications that signals Dynamics 365 depth123. For Sales migrations specifically, partners with explicit Salesforce-to-Dynamics, on-prem-to-online, or HubSpot-to-Dynamics practices tend to ship cleaner than generalist implementation shops.

Cobalt, Rand Group, Arctic IT, Encore Business Solutions, ProServeIT, SingleStone and Veelead are commonly named in the migration corner of the market and each offers fixed-scope migration packages alongside ongoing managed services. Microsoft also runs its in-house FastTrack for Dynamics 365 service which provides architecture guidance and remediation support at no cost for qualifying customers — useful for tenant-to-tenant moves and large enterprise programmes123.

On the ETL and iPaaS side, KingswaySoft's SSIS Dynamics 365 connector is the de facto standard for enterprise migrations150. Fivetran, Workato, Azure Data Factory, Power Automate and Microsoft's own Data Migration Framework all have Dataverse connectors that handle staging, transformation and ongoing sync. Their role is rarely the migration itself — it is the staging layer that lands source data into Azure SQL or Synapse, and the ongoing-sync layer once the one-time load is done.

Managed-migration cost ranges vary widely with scope. A small-business Sales Professional implementation with 10 users, minimal customisation and a one-time CSV import of Accounts and Contacts lands around $4,000–$8,000 in published practitioner estimates131. Mid-market and enterprise Dynamics 365 CRM implementations — Sales plus historical data, Power Platform automation and Office 365 integration — run $25,000 to over $250,000, driven by record count, custom-table complexity and integration rebuild surface.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Dynamics 365 Sales migrations and handles the Dataverse schema modelling, alternate-key design, option-set integer conversion, BPF stage mapping, server-side privilege configuration for overriddencreatedon, and the reconciliation work described in Sections 5 and 7. Pricing is fixed-fee, scoped by record count and source platform, with separate line items for custom tables, historical Activity depth and SharePoint attachment volume so scope is transparent.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Solutions Partner with industry depth, a Microsoft FastTrack engagement, an SSIS-led iPaaS approach, or a specialist migration vendor. [Explore FlitStack →](/contact)

Dynamics 365 migration checklist

An exhaustive, phased punch list for moving sales data into Microsoft Dynamics 365 Sales on Dataverse, covering scope, schema, transform, sandbox test, cutover, and validation. Typical timeline: 8–20 weeks.

0. Decide & Plan9 tasks
  • Define which Dataverse tables are in scope. List every standard Sales table (Account, Contact, Lead, Opportunity, Quote, Order, Invoice, Product, Price List, Competitor) and every custom table that must move. Mark any source object that maps to none of these as out of scope.If skipped: Undeclared tables surface mid-cutover and force unplanned schema work in the production environment.
  • Define historical-data scope by table. Decide how many years of closed Opportunities, completed Activities, fulfilled Orders, and posted Invoices to migrate. Note whether emails, phone calls, appointments, tasks, and Annotations are in or out.If skipped: An 'everything' scope inflates storage costs against Dataverse capacity entitlement and stretches the cutover window past the planned freeze.
  • Confirm tenant and environment strategy. Decide whether the destination is a brand-new Microsoft 365 tenant or an existing one. Plan separate Dev, Sandbox, and Production environments in the Power Platform admin center.If skipped: Tenant-to-tenant moves of Dynamics 365 Sales cannot be self-served and require a FastTrack engagement that adds weeks of lead time.
  • Confirm Sales SKU per user. Decide the mix of Sales Professional, Sales Enterprise, Sales Premium, and Team Member licenses needed at go-live. Some forecasting and Sales Insights features require the Enterprise or Premium tier.
  • Document data-residency and compliance constraints. Record the Dataverse geography the production environment must sit in, plus any GDPR, HIPAA, SOC2, or industry-regulatory obligations that gate the cutover.If skipped: Provisioning the environment in the wrong geography requires a full environment rebuild — there is no in-place region change.
  • Assign one accountable migration owner. Name a single DRI with authority to make trade-off calls. List business sponsors, the system administrator, the integration owner, and the security-role owner alongside.
  • Write the success criteria. State the falsifiable conditions that declare the migration done — record-count parity per table, pipeline-value parity, no critical defects open, sign-off from the named sponsor.If skipped: Without written criteria, 'done' becomes a moving target and the project never formally closes.
  • Set the freeze date and cutover window. Pick the source-system freeze timestamp and the cutover weekend. Reserve a roll-back window inside it. Communicate both to sales leadership.
  • List explicit out-of-scope items. Write down what is not moving — legacy custom objects, archived attachments older than N years, abandoned automations. Get the sponsor to initial it.If skipped: Items not declared out of scope become implicit in-scope items that surface as defects during validation.
1. Pre-Migration Prep28 tasks
  • Capture baseline record counts per source object. Export a single-page summary: Accounts, Contacts, Leads, Opportunities, Quotes, Orders, Invoices, Activities, Notes, Files. This is the parity yardstick for Phase 6.If skipped: Without a baseline, you cannot prove the migration moved everything it was supposed to move.
  • Run a dedup pass on source Contacts using email as the match key. Resolve every flagged duplicate at the source before export. Document the survivors so downstream relationship reassignment is unambiguous.If skipped: Duplicates that survive into Dataverse trigger downstream duplicate-detection blocks on subsequent imports and pollute Copilot relationship analytics.
  • Run a dedup pass on source Accounts using name plus website. Merge legal-entity duplicates before they each spawn a separate Account in Dataverse.
  • Standardize phone numbers and country codes at the source. Convert to E.164 format if downstream Power Automate flows or Teams dialer integration will rely on it.
  • Standardize email casing and trim whitespace. Dataverse string comparisons are case-insensitive on equality but case-sensitive on display; clean once at source so dedup rules behave deterministically.
  • Resolve missing required-field values at the source. For every record missing a value in a Dataverse-required column (Account name, Contact full name, Opportunity name, Opportunity customer), patch the source or stage a default.If skipped: Records with null required fields fail row-by-row in the Import Data Wizard and partially during batch loads.
  • Inventory all source custom fields. Pull a field list per object: name, data type, length, picklist values, formula expression, and whether the field is referenced by any source automation or report.
  • Inventory source automations and integrations. List every workflow, sequence, plug-in, and third-party integration touching in-scope data. Mark each as: rebuild in destination, retire, or keep paused.If skipped: Active source automations firing during export create a moving target; active destination automations firing during import generate notification spam and bad downstream sends.
  • Provision Production, Sandbox, and Dev environments. Use the Power Platform admin center. Set type, region, and currency. Enable Dataverse on each. Reserve at least one Sandbox for data-migration use only.If skipped: Sharing one Sandbox between migration loads and configuration testing causes data collisions that invalidate both efforts.
  • Install the Dynamics 365 Sales application in each environment. From the admin center, deploy the Sales app and any optional modules (Sales Premium, Sales Insights) you licensed in Phase 0.
  • Set base currency, fiscal year, and time zone in System Settings. These values are write-once at the org level and cannot be changed after data is loaded.If skipped: Changing base currency after Opportunity records exist requires environment rebuild; all multi-currency historical conversions get re-derived against the new base.
  • Configure Business Units to mirror the org's security boundaries. Map source territories, regions, or business segments to Dataverse Business Units. Every user and every record will own a Business Unit assignment.
  • Create security roles and Teams. Build or clone roles for sellers, managers, sales ops, and the data-migration service user. Create Teams where ownership is shared.
  • Provision the migration service user with elevated privileges. Grant System Administrator plus the prvOverrideCreatedOnCreatedBy privilege so the user can set overriddencreatedon on imported records.If skipped: Without prvOverrideCreatedOnCreatedBy, every imported record stamps createdon at import time and original history is lost.
  • Provision end-user accounts and assign Sales licenses. Sync users from Microsoft Entra ID, assign Sales SKUs, and place each user into the correct Business Unit and security role.
  • Build an unmanaged Solution to hold all migration customizations. Create a publisher with a unique prefix, then a single unmanaged Solution that owns every custom column, custom table, and modified form. Source-control the exported solution zip.If skipped: Customizations made outside a Solution cannot be moved cleanly from Dev to Sandbox to Production and force manual rebuild in each environment.
  • Add every required custom column to its Dataverse table inside the Solution. Match data type, max length, and decimal precision from the Phase 1a field inventory. Importing into a column that does not yet exist silently drops the data.If skipped: Each in-scope source field that has no destination column at import time results in lost source data that is hard to detect post-load.
  • Watch the 1,000-column-per-table ceiling. Dataverse caps custom + system columns at roughly 1,000 per table. Trim unused source fields, or split into a related custom table, before approaching the cap.
  • Define all Choice column values up front. Each Choice option has an integer value plus a label. Lock the integers now — labels are renamable but the integer is the upsert key downstream.If skipped: Changing a Choice integer after data is loaded breaks every downstream view, chart, Power Automate flow, and report filter that referenced the old integer.
  • Stay under the 10 calculated and 10 rollup field caps per table. Dataverse limits calculated and rollup fields to 10 each per table. If the source has more, decide which become real columns populated at import and which become post-load Power Automate flows.
  • Define Alternate Keys on every table that needs upsert. Create Alternate Keys on a unique combination of columns (typically a sourcesystemid custom column) for Account, Contact, Lead, Opportunity, Product, and every custom table. This is the Dataverse equivalent of an external ID.If skipped: Without Alternate Keys, upserts cannot match existing rows and re-runs of failed batches create duplicate GUIDs.
  • Stage the Sales Process flows you intend to run on imported Opportunities. Configure the out-of-box Opportunity Sales Process or a custom Business Process Flow. Decide whether to activate it on imported records or load them in a pre-process state and progress them after.If skipped: Activating a Business Process Flow against bulk-imported Opportunities can stamp every record at the first stage and lose the original stage history.
  • Disable all Power Automate flows and classic workflows that fire on Create or Update for in-scope tables. Pause notifications, lead-routing, scoring, and any flow that emails customers. Keep them paused through the end of Phase 5.If skipped: Flows firing during import spam customers, mis-route ownership, and double-count metrics — sometimes irrecoverably.
  • Decide on SharePoint document management vs Annotation attachments. Enable SharePoint integration if attachments will live in document libraries, or keep blobs inside Annotation.documentbody if they must stay in Dataverse storage. The choice drives Phase 2 export packaging.If skipped: Switching the choice after files are loaded means re-uploading every attachment via the other path.
  • Set duplicate-detection rules for Account, Contact, and Lead. Decide whether default rules stay enabled during bulk import. Many teams disable duplicate detection during load and re-enable after Phase 6 reconciliation.If skipped: Default duplicate detection blocks legitimate same-email imports across Contact and Lead and silently drops rows from the import job.
  • Announce the source-system freeze to all users. Send a calendar invite for the freeze window. Pin the announcement in the source CRM.
  • Schedule baseline Dynamics 365 Sales training. Cover Sales Hub navigation, the Opportunity Sales Process, Timeline, and Copilot summaries. Segment training by role — sellers, managers, sales ops.
  • Designate first-responder admins for the 48 hours post-cutover. Name two system admins on call. Publish their Teams channel and direct number.
2. Source Export15 tasks
  • Export Accounts with every standard and custom column. Include owner, parent account, primary contact, and the source primary key — that primary key becomes the sourcesystemid for the Dataverse Alternate Key.
  • Export Contacts with every standard and custom column. Include parent account reference, owner, and source primary key.
  • Export Leads with status, source, qualification timestamps, and disqualification reason. Capture the lead-to-opportunity conversion link if the source records it; you will rebuild that relationship on the Lead row in Dataverse.
  • Export Opportunities with stage, close date, revenue, owner, parent account, and primary contact. Capture estimatedclosedate, actualclosedate, statecode, statuscode, and the full custom-field set.If skipped: Closed Opportunities re-imported without statecode set return as Open in Dataverse and skew pipeline reports.
  • Export Opportunity Products (line items). Each Opportunity Product references both the Opportunity and a Product or write-in product. Export the link table separately from the Opportunity header.
  • Export Quotes, Orders, and Invoices with their line items. Export header and line rows in separate files. Preserve the parent-child key so the relationship can be rebuilt at load time.
  • Export Product catalog, Price Lists, and Price List Items. Without these in place at load time, Opportunity Product imports fall back to write-in product and lose the catalog link.If skipped: Loading Opportunity Products before the Product and Price List records exist orphans every line item.
  • Export Activities — emails, phone calls, appointments, tasks — as separate files. Each activity type has its own schema. Include the regarding (parent) record reference, the activity party list, and the createdon timestamp.If skipped: Activities loaded without their regarding reference detach from the parent Account, Contact, or Opportunity and become orphaned in Timeline.
  • Export Notes (Annotations) separately from activities. Capture subject, notetext, objectid (the regarding record), objecttypecode, and any attached file binaries.
  • Export file attachments and their metadata. For each file, capture the filename, MIME type, the parent record id, and the binary itself. Decide whether the destination is SharePoint or Annotation.documentbody per Phase 1b.
  • Export the user list with roles, manager, and Business Unit assignment. Map every source owner to a destination Entra ID user before loading any record they own.
  • Export Competitor, Sales Literature, and Goal records if in scope.
  • Export every active source pipeline stage definition. Capture stage name, order, probability, and any stage-required fields. These map to Business Process Flow stages in Phase 3d.
  • Screenshot or export every source dashboard and report. Dashboards do not migrate — they will be rebuilt in Phase 7. Capture filter logic, chart type, and source-of-truth fields.
  • Stamp every export file with the exact export timestamp in UTC. This timestamp is the delta watermark for the Phase 5 final-pull export.If skipped: Without a watermark, the delta-pull duplicates records and a manual diff costs hours of cutover-window time.
3. Transform & Map28 tasks
  • Build a master mapping sheet per Dataverse table. Columns: source field, source type, destination table, destination column, destination type, transformation rule, required-on-import flag, sample value, target Alternate Key flag.
  • Resolve every picklist value mismatch into the destination Choice integer. If the source has 'Won-Closed' and the destination's Opportunity statuscode reads 'Won', map the source string to the destination integer in the transform layer.If skipped: Loading the source label as a string into a Choice column drops the row with a type-mismatch error.
  • Designate the upsert key per table. Email for Contacts, name+domain for Accounts, sourcesystemid for everything else. Confirm each matches a Dataverse Alternate Key created in Phase 1b.
  • Decide handling for source fields with no destination column. Per field, choose: drop, concatenate into a Notes append, or create a new custom column (and add it to the Solution).
  • Identify every required Dataverse column with no source equivalent. For Opportunity, customerid is required; for Contact, fullname is computed; for Account, name is required. Pre-stage a default value or a derivation rule per column.If skipped: A required Dataverse column with no source value blocks the entire row at import; partial loads must be re-run from scratch.
  • Convert all dates to ISO-8601 with timezone. Dataverse stores datetime in UTC; convert source local times explicitly so historical timestamps land where you expect.
  • Normalize currency values and stamp transactioncurrencyid. Every money column on every row needs an associated currency reference. For multi-currency sources, also stamp exchangerate at the historical close date.If skipped: A money column without transactioncurrencyid defaults to base currency and silently mis-states multi-currency historical revenue.
  • Truncate string values that exceed destination column length. Document every truncation. Long Notes append or split into multiple Annotations rather than silent truncation.
  • Re-encode all text files as UTF-8 (no BOM). The Import Data Wizard mis-parses non-UTF-8 source files with diacritics and ideographic characters.
  • Escape commas, quotes, and newlines inside CSV fields. Long-form Notes and email body fields commonly contain newlines; double-quote and escape inner quotes per RFC 4180.If skipped: Unescaped newlines split a single source row into multiple destination rows mid-load.
  • Strip HTML from email Description if Rich Text is not enabled in Timeline. Email bodies arrive with full HTML markup. If Rich Text Notes is disabled on the destination, the markup renders raw.
  • Convert source GUIDs to a dedicated sourcesystemid column. Do not attempt to write source GUIDs into the Dataverse primary-key column — that field is system-managed. Store the source ID in the Alternate Key column instead.
  • Decide and implement the historical-timestamp strategy. Either set overriddencreatedon on every imported row (requires prvOverrideCreatedOnCreatedBy on the migration user) or capture the original created date in a custom 'Original Created On' column and let createdon stamp at import time.If skipped: Skipping this decision is the single biggest cause of post-migration confusion when sellers see 'created last Tuesday' on a five-year-old Opportunity.
  • Decide the record-ownership strategy. Best-match owner by email to the destination user, fall back to a single 'Data Migration' service user, or always assign to the source primary contact's manager. Document the rule per table.
  • Decide attachment migration approach. Re-upload binaries into Annotation.documentbody (Dataverse storage cost applies) or rehost in SharePoint and link via the SharePoint integration (cheaper for large libraries).
  • Plan the load order against relationship dependencies. Users → Business Units → Teams → Product catalog → Price Lists → Accounts → Contacts → Leads → Opportunities → Opportunity Products → Quotes/Orders/Invoices → Activities → Notes → Attachments → N:N junction records.If skipped: Loading children before parents either fails with reference errors or silently nulls the lookup.
  • Map source pipeline stages to Business Process Flow stages. Dynamics 365 Sales pipelines run on Business Process Flows. Decide which BPF activates per imported Opportunity and at which stage. Stage progression is recorded as a separate BPF instance record.If skipped: Skipping BPF planning means imported Opportunities show no current stage and sellers cannot use Sales Hub's pipeline view.
  • Rebuild every source automation as a Power Automate cloud flow. Source workflows, sequences, and triggers do not migrate. Recreate each one targeting the Dataverse trigger schema. Keep all flows in draft until Phase 5 re-enable.
  • Recreate classic Workflows and Plug-ins inside the Solution. If the destination must mirror server-side logic from a prior Dynamics environment, register Workflows and Plug-ins through the Plugin Registration Tool and include them in the unmanaged Solution.
  • Verify Alternate Key uniqueness across every batch file. Dataverse Alternate Keys enforce uniqueness; two rows with the same sourcesystemid in one $batch are both rejected.If skipped: Duplicate Alternate Key values cause the entire batch to fail with HTTP 412 — diagnosis requires parsing the full multipart response body.
  • Pre-compute Choice integer values for every multi-select and option-set column. MultiSelectPicklist values are stored as a semicolon-delimited list of integers, not labels. Build the lookup table during transform and emit integers in the load file.If skipped: Sending labels to a MultiSelectPicklist column either errors or silently writes the label into a separate text column if one accidentally exists with the same name.
  • Pre-stage all customer Lookup references as $expand-safe references. Opportunity.customerid is a customer lookup that points to either Account or Contact. Each value must carry an @odata.bind reference like 'accounts(<guid>)' or 'contacts(<guid>)'.If skipped: A customer lookup populated as a plain string drops the row at parse time with a validation error.
  • Pre-derive lead scores if Predictive Lead Scoring is licensed. Sales Premium re-derives lead scores from model training on destination data — historical source scores will not transfer. Capture the source score in a custom column for reference, not in the system score column.
  • Reconfirm calculated-field caps for every in-scope table. If transformation discovered more than 10 fields that would be calculated, redesign the excess as standard columns populated by Power Automate flows after import.
  • Plan how N:N junction rows will be loaded. Many-to-many records cannot be created in a single write to the parent — they require a separate associate step per pair. Build the junction load as its own job after both sides of the relationship are loaded.If skipped: Attempting to embed N:N relationships in the parent create call is one of the most common reasons bulk loads fail silently with the relationship missing.
  • Map source territories to Business Units or to Territory records. Dynamics 365 Sales has both Business Units (security scope) and Territory (sales-coverage scope). Decide which one source territories map to and stamp ownership accordingly.
  • Rebuild duplicate-detection rules with deferred enable. Build all required duplicate-detection rules in the Solution but keep them unpublished until Phase 7. Disable Power Platform duplicate detection if the org plans to rely on Sales-specific lead dedup.
  • Stage Opportunity Sales Process closure status correctly. A closed-won Opportunity needs statecode=Won, statuscode=Won, plus actualrevenue, actualclosedate, and a closeopportunity child record. Closed-lost needs the symmetric trio.If skipped: Setting only statecode without statuscode leaves Sales Hub showing the Opportunity as in an inconsistent state that is not queryable from default views.
4. Sandbox Test Migration13 tasks
  • Pick a representative 1–5% sample per in-scope table. Bias the sample toward records that exercise edge cases — Opportunities with line items, Contacts with attachments, Accounts with parent-child hierarchy.
  • Choose the import method per table. Use the Import Data Wizard only for tables under 20,000 rows total. Document the chosen method per table for everything larger.If skipped: Microsoft's documented recommendation is to limit Import Data Wizard imports to 20,000 rows; pushing more into the wizard exhausts memory and the job hangs.
  • Load the sample in the Sandbox via the chosen method. Start small — work through the first few batches deliberately, then scale up once errors are clean.
  • Use update-only semantics on every batch update to prevent accidental insert. Force update-only behavior on writes so missing-record errors surface instead of silently creating a row with the bogus GUID.If skipped: Without update-only semantics, source GUIDs that have no Alternate Key match get created as new Dataverse rows with the source GUID, polluting the table.
  • Spot-check 10 random Sandbox records per table against the source. Walk every column, every linked record, every Note, every attachment. Have a sales-ops domain expert do the spot-check.
  • Test long strings, special characters, and unicode. Load deliberately ugly rows — Cyrillic names, emoji, em-dashes, embedded newlines in Notes. Confirm Dataverse stores and renders them.
  • Test the historical-timestamp override. Pick a row, set overriddencreatedon, load it, then open it in Sales Hub Timeline. Confirm the original created date displays — not the import date.If skipped: Test failures here are easy to fix; production failures here are expensive to fix because every row must be re-stamped.
  • Test parent-child relationships end-to-end. Walk Account → Contacts → Opportunities → Opportunity Products → Quotes. Confirm every link resolves in both directions.
  • Test N:N junction loads after both sides exist. Send Associate requests for a small sample. Verify the junction shows in both parents' related-records grid.
  • Test attachment upload at the chosen storage tier. If SharePoint, confirm the document library auto-creates and the file opens from the record. If Annotation, confirm documentbody decodes without corruption.
  • Run a full-volume rehearsal. Load the full dataset into Sandbox. Measure wall-clock time for each table. Multiply by any safety factor and confirm the cutover window fits.If skipped: A first-time full-volume run in Production is the single most common reason cutover windows blow past their planned end time.
  • Validate Business Process Flow assignment on a sample Opportunity batch. Confirm each imported Opportunity carries an active BPF instance at the intended stage and that progressing the stage in Sales Hub does not throw.
  • Get written Sandbox sign-off from the migration sponsor and a sales-ops lead. Email is fine; signature is the gate to Phase 5. List defects deferred to post-cutover.If skipped: Proceeding to Production without sign-off leaves the team with no shared definition of 'tested' when a defect surfaces later.
5. Production Cutover15 tasks
  • Confirm source freeze and verify zero writes in the last hour. Run a source-side query for any updatedat newer than the freeze timestamp. If hits, escalate and reset the freeze.If skipped: Writes during cutover create a delta that is impossible to fully reconcile after Phase 6.
  • Take the final delta export of every in-scope table. Pull rows changed since the Phase 2 watermark. Stamp this export with a new watermark — it is the source of truth for cutover.
  • Verify Power Automate flows and classic Workflows remain disabled in Production. Spot-check the flow list. Any flow accidentally re-enabled between Phase 4 and now must go back to draft before the first record loads.
  • Verify SharePoint integration is configured and the migration user has site access. If attachments target SharePoint, the document libraries must exist or auto-create privileges must be granted before the load.
  • Load Users, Business Units, and Teams first. Every owned record needs a valid owner GUID. Users must exist before any record they own loads.
  • Load Product catalog, Unit Groups, and Price Lists. Catalog records are referenced by Opportunity Products, Quote Products, and Order Products. Load them next.
  • Load Accounts with Alternate Key upsert. Capture the request ID, row count, and error log per batch.If skipped: A failed batch without a captured request ID cannot be diagnosed against the trace log.
  • Load Contacts with Alternate Key upsert and stamp parentaccountid via @odata.bind.
  • Load Leads, Opportunities, Quotes, Orders, Invoices, and their line items in order. Header tables first, then line tables. Use @odata.bind to set parent references explicitly.
  • Load Activities — emails, phone calls, appointments, tasks — with regardingobjectid set per record. Each activity needs a regarding lookup to its parent. Set statecode on completed activities so they land in the right Timeline bucket.
  • Load Annotations (Notes) and re-upload attachment binaries. If SharePoint is the target, push files to the document library and let the integration create the metadata; if Annotation, base64-encode and POST documentbody.
  • Load N:N junction associations in a final dedicated pass. Send Associate requests in batches. Confirm both sides of the relationship are loaded before each request.
  • Cross-check destination row counts against source row counts at every step. If any table is off by more than the documented tolerance, stop and diagnose — do not push through with partial data.If skipped: Pushing past a row-count miss compounds the defect and makes root-cause analysis multiple orders of magnitude harder.
  • Re-enable Power Automate flows, Workflows, and Plug-ins only after all loads complete. Toggle in the documented order — internal-routing flows first, customer-facing flows last. Watch the run history for the first 30 minutes.
  • Stamp a 'cutover complete' marker record. Create one row in a Cutover Log custom table with the timestamp, the migration user, and the final row counts. This anchors Phase 6 reconciliation.
6. Validate21 tasks
  • Compare row counts per Dataverse table against the source. Use Advanced Find or FetchXML for the destination side. Match the Phase 2 baseline plus the Phase 5 delta. Investigate any variance.If skipped: Even a 1% row variance can hide a 100% loss on a specific Business Unit, owner, or date range. Slice the comparison by every dimension you reported on in the source.
  • Compare total pipeline value per stage. Sum estimatedvalue for open Opportunities by Business Process Flow stage. Compare to the source. A delta here usually means missing rows or missing transactioncurrencyid.
  • Compare won and lost Opportunity counts and revenue by close month. Group by actualclosedate month and statecode. Variance by month usually points to date-format or timezone errors.
  • Compare Lead counts by source, status, and owner.
  • Spot-check 25 random records per table field-by-field. Pick random source rows; open the corresponding destination row in Sales Hub; walk every column. Log any difference.
  • Spot-check 25 random custom-column values per table. Custom columns are where silent drops most often happen. Confirm sample values arrived intact.If skipped: A custom column that imports as null on every row indicates the column was not in the Solution at load time and every row needs re-import.
  • Verify Contact → Account parent links on a 50-record sample.
  • Verify Opportunity → Account and Opportunity → Contact lookups.
  • Verify Opportunity Product line items roll up to the right Opportunity header.
  • Verify Activities attach to the right regarding record. Open a sample Opportunity, scroll Timeline, confirm the historical emails and phone calls show. Repeat for Contact and Account.If skipped: Orphaned Activities are invisible in the parent's Timeline and seller adoption drops the day they notice.
  • Verify file attachments open from the record. Sample 20 files across SharePoint and Annotation paths. Open each. Confirm the rendered file matches the source.
  • Verify N:N junction associations show on both sides.
  • Confirm overriddencreatedon worked on a 25-record sample. Open each record and check the Timeline header date. If it shows the import date instead of the original, escalate before users log in.
  • Enable Dataverse Auditing on the in-scope tables post-load. Configure Audit Settings to start audit on the production tables now that the migration write storm is over. Audit during the load itself bloats Audit storage.
  • Pull a data-residency confirmation from the Power Platform admin center. Screenshot the environment region. Attach to the compliance evidence file alongside the relevant GDPR or HIPAA controls referenced in Phase 0.
  • Confirm Business Process Flow stages display correctly on imported Opportunities. Sample 20 Opportunities. Open each in Sales Hub. Confirm the BPF bar shows the right stage and the next-stage button works.
  • Have five power-user sellers validate their own pipeline end-to-end. Each opens their My Open Opportunities view, opens three Opportunities, walks the Timeline, edits a field, saves. Capture every defect.
  • Have two sales managers validate forecast and pipeline rollups. Open the forecast view. Compare to the source forecast for the same week. Variance flags missing rows or wrong stage.
  • Have a sales-ops lead spot-check Quote, Order, and Invoice line totals.
  • Log every UAT defect with severity and an owner. Triage critical defects before sign-off; defer cosmetic ones to Phase 7.
  • Get written sign-off from the migration sponsor. Email confirming all critical defects closed, parity reports attached, sponsor approves go-live. This is the gate to Phase 7.If skipped: Skipping sign-off leaves no defensible position when a defect surfaces post-cutover and someone asks why the team launched.
7. Post-Migration Cleanup13 tasks
  • Announce go-live to all end users. Include the Sales Hub URL, the Microsoft Entra sign-in instructions, and the first-responder Teams channel.
  • Run role-specific training sessions. Sellers — Timeline, Sales Process, Copilot. Managers — forecasts, pipeline analytics. Sales ops — Solutions, security roles, duplicate detection.
  • Set the source system to read-only. Lock the source on the announced date. Pin a notice in the source CRM directing users to Sales Hub.
  • Rebuild dashboards in Dynamics 365 Sales. Use the Phase 2 dashboard screenshots as the spec. Build interactive dashboards in the Sales Hub or model-driven Power Apps as appropriate.
  • Activate Power Automate flows in their final intended state. Walk the flow list; promote each from draft to active per the Phase 1a inventory. Watch run history for the first 24 hours.
  • Re-establish integrations to email, calendar, Teams, and BI tools. Enable server-side sync for Exchange Online. Configure Teams chat for Dynamics 365. Repoint Power BI datasets to the new environment.
  • Publish duplicate-detection rules. Toggle the rules built in Phase 1b from unpublished to published. Run a one-time duplicate-detection job to surface any cross-record duplicates created during load.
  • Enable Copilot and predictive scoring on a delay. Wait 30 days for data-entry patterns to stabilize before enabling Copilot summaries and predictive lead/opportunity scoring; both train on destination behavior.
  • Export the unmanaged Solution as a managed Solution and source-control it. The managed export is the deployable artifact for future environment promotions. Tag the version with the cutover date.
  • Schedule a 30-day post-migration retrospective. Capture what worked, what bit the team, and what the next migration cohort should change.
  • Archive every export, mapping spreadsheet, and run log to long-term storage. Keep them at least as long as the compliance retention window from Phase 0 requires.If skipped: Without archived run logs, any future forensic question about a specific record's lineage is unanswerable.
  • Set the source-system decommission date. Typically 90 days after cutover, after the final data-retention window closes. Communicate the date to finance, legal, and IT.
  • Close the migration project formally. Final status report, lessons-learned doc, sponsor sign-off on closure. Free the team to move on.

Questions, answered

Migrating to Dynamics 365: questions

How long does migration to Dynamics 365 Sales take?

Small-to-mid migrations with under 50,000 records and standard tables typically run 8 to 12 weeks end-to-end. Enterprise programmes covering Sales plus Customer Service plus historical data and Power Platform automation run 6 to 12 months. Add 4 to 8 weeks if a tenant-to-tenant move is in scope.

Can I migrate from Salesforce to Dynamics 365 Sales?

Yes — Salesforce is the most common migration source. Standard objects map cleanly to Dataverse tables, but Apex code, Flows, Process Builder and Reports do not transfer and need to be rebuilt as Power Automate flows, Plug-ins or Business Process Flows. Watch picklist-to-Choice-integer conversion and case-sensitive Salesforce Record IDs.

Can I migrate from Pipedrive or HubSpot to Dynamics 365 Sales?

Yes — both are common sources. Pipedrive's People, Organisations, Deals and Activities map to Contacts, Accounts, Opportunities and Activities. HubSpot's Contacts, Companies and Deals map similarly. The biggest schema shifts are HubSpot's enumeration internal values into Dataverse Choice integers, and Pipedrive's per-pipeline stages into Business Process Flow stage rows.

Does Dynamics 365 preserve original timestamps on import?

Partially. The `overriddencreatedon` column lets a privileged service principal set the original create date, and audit-enabled tables track the override. Activity `actualend` accepts backdated timestamps. But `modifiedon` is not overridable by default, which makes the Timeline sort by import date unless you explicitly configure the override path.

Can I migrate custom tables to Dynamics 365 Sales?

Yes — custom tables are first-class Dataverse citizens with the same lookup, alternate-key and cascade-behaviour semantics as standard tables. Create the custom table, its columns, alternate keys and relationships inside an unmanaged Solution first, deploy as managed to the target environment, then load records via the wizard or SSIS.

What happens to Opportunity stages and Business Process Flows during migration?

Recreate every Business Process Flow and stage in the target environment before importing Opportunities — rows targeting non-existent BPF stages load but appear at stage one of the default Lead-to-Opportunity process. Map source-stage to BPF stage ID, then write to the `stageid` and `processid` columns explicitly during the Opportunity load.

Is there an undo or rollback for Dynamics 365 imports?

Yes — Settings → Data Management → Imports lists every job and offers a Delete option that removes only the records that job created, leaving untouched rows intact. It is not a bulk-rollback button. Best practice: stamp every imported row with an Import Batch ID custom column for granular post-cutover cleanup.

Sources

  1. Microsoft Dynamics 365 Sales — Wikipedia
  2. Microsoft Dynamics 365 Sales vs Salesforce Sales Cloud — Gartner Peer Insights
  3. Dynamics 365 environment strategy — Microsoft Learn
  4. Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
  5. Import data (all record types) — Power Platform | Microsoft Learn
  6. Execute Batch Operations on Dataverse — Microsoft Learn
  7. Batch/Bulk operation when upsert is disabled — Dynamics 365 Community
  8. Service protection limits (Microsoft Dataverse)
  9. Extensibility Guide for Dynamics 365 Sales — Microsoft Learn
  10. Get guidance for your Dynamics 365 environment strategy — Microsoft Learn
  11. How to create junction object between two entities — Dynamics 365 Community
  12. Entity relationship behavior — Microsoft Learn
  13. Migration of Dynamics 365 Sales from tenant to new tenant — Dynamics 365 Community
  14. Types of fields and field data in Dynamics 365 — Microsoft Learn
  15. Create a calculated field in Dynamics 365 — Microsoft Learn
  16. Migrating Historical Activities to a new CRM Instance — Dynamics 365 Community
  17. Import accounts, leads, and more into Dynamics 365 Customer Engagement (on-premises)
  18. Override created on date for bulk note import migration — Dynamics 365 Community
  19. Bulk change of owner and record update on filtered accounts — Dynamics 365 Community
  20. audit EntityType (Microsoft.Dynamics.CRM) — Microsoft Learn
  21. Enable duplicate lead detection — Microsoft Learn
  22. Create duplicate detection rules in Dynamics 365 — Microsoft Learn
  23. Dataverse capacity-based storage details — Microsoft Learn
  24. Understand the sales process — Microsoft Learn (Dynamics 365 Sales)
  25. Dynamics 365 Sales documentation — Microsoft Learn
  26. How to roll-back a re-import of accounts — Dynamics 365 Community
  27. Dynamics 365 Partners — Microsoft Dynamics 365
  28. D365 Sales Implementation Costs — r/Dynamics365
  29. Dynamics 365 in Germany and local German regions — Microsoft Learn
  30. Manage configuration and migration data for Dynamics 365 projects — Microsoft Learn
  31. Use server-side synchronization with Sales agent — Microsoft Learn
  32. Contact Deduplication Agent in Dynamics 365 Sales — Microsoft Learn
  33. Key considerations for migrating to Dynamics 365 Sales — Microsoft Learn
  34. How to migrate records from Pipedrive to D365 Sales? — Dynamics 365 Community

Get a quote

Moving to Dynamics 365?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Dynamics 365 setup with you, then send a quote.

Get a quote