The 7 milestones of a Data Migration with Dynamics 365

In general, a data migration is a mass movement of data from a source to a destination. The data movement can be performed according to following approaches: the "big bang" approach and the “phase " approach.  The "Big Bang" approach means that the migration takes place only once and we know when it starts and when it ends. This approach requires, in principle, a ”shut down” of the system including the data source to be migrated. On the other hand, the phased approach, although it complicates the migration process because the data migrated to the destination has been modified in the original source, allows smaller pieces of data (and metadata) to be migrated. 

Purpose

The whitepaper explains a structured methodology for migrating data from Dynamics CRM 2011 (on-premises) to Dynamics 365 (on-premises, v8.2/9.0) using a big bang approach. It focuses on strategies, tools, and steps to ensure a successful migration under strict time and technical constraints.

Key Context

• Scenario: Migrating ~1.5 TB of data (including 1 TB of email templates) within 10–15 hours.
• Challenges:
  • Different data and metadata structures between CRM 2011 and D365.
  • Platform and version differences.
  • Security model changes, asynchronous vs synchronous service behaviors.
  • Performance and infrastructure constraints.

Migration Approach

• Selected Option: Database-to-database (Type A-3) with different structure, platform, and version.
• Tools Used:
  • SQL Server (SSIS, Profiler, Management Studio)
  • Dynamics 365 Deployment Manager
  • DotPeek (.NET decompiler)
  • Metadata Diagram Tool

The 7 Milestones

1. Create Basic Requirements
   • Prepare a D365 template database, import custom solutions, validate keys, and create backups.
2. Prepare Data
   • Clean and organize CRM security data (System User, Team, Business Unit).
3. Transfer CRM Security Data
   • Migrate security-related entities and update GUIDs.
4. Validate Security Data
   • Use SDK Deployment for user mapping and Active Directory sync; perform CRUD tests.
5. Transfer Business & System Data
   • Migrate remaining CRM entities, log changes, and generate reports.
6. Validate Migrated Data
   • Functional testing, retargeting, and adjusting migration code if needed.
7. Finalize Migration
   • Deploy indexes, keys, configurations, and custom code; perform final validations.

Iteration: If validation fails at milestones 4 or 6, return to previous steps.

The AI workspace that works for you. | Notion

A tool that connects everyday work into one space. It gives you and your teams AI tools—search, writing, note-taking—inside an all-in-one, flexible workspace.

Notion