Migrate your Microsoft Dynamics 365 Sales data

Accounts (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.

Contacts 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.

Leads 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.

Opportunities 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.

These 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 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 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.

Sales 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.

Territory 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.

User 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 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.

Business 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 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.