How-To - Sucessful Data Migration
This white paper provides an overview and a detailed view of pitfalls making painful a data migration (Dynamics 365). Native and custom items could delay the process. Those items should be categorized into: data context, platform context, functional context, code context, architecture context.
Purpose
The guide provides a structured methodology for orchestrating data migration in Dynamics 365 (D365), particularly for on-premises environments. It focuses on avoiding common pitfalls and ensuring a smooth migration process.
Key Points
- Migration Context & Options
- Two main scenarios: DB-to-DB (on-prem to on-prem) and DB-to-Service (on-prem to online).
- Pitfalls include security model complexity, shared data, denormalization, logs, and large data volumes.
- Core Problem
How to orchestrate the data model: grouping entities, defining execution sequences, prioritizing, and excluding unnecessary entities. - Requirements
- Create three databases: source, target, and a CRM Tool for mapping, logging, and reporting.
- Prepare SQL objects, stored procedures, and reference tables.
- Data Preparation
- Initialize logging, backups, and reporting.
- Update CRM security model and disable indexes before migration.
- Orchestration Strategy
Migration is divided into 7 waves and 16 sequences, each handling specific entity groups:- Core Model (security, users, roles)
- Product Model
- Customer Model (accounts, contacts)
- Core Business Model (opportunities, quotes, orders)
- Activity Model (emails, tasks, attachments)
- Internal System Processes (audit, logs)
- Custom/System Entities & Finalization (rebuild indexes, full backup)
- Validation Process
After each wave, perform deployment checks and functional tests before proceeding.
Conclusion
The guide emphasizes planning, sequencing, and validation to ensure accurate and efficient data migration. It advocates a repeatable methodology adaptable to both on-prem and cloud targets.