We’re planning a migration from an on-premises Dynamics CRM to Dynamics 365 using an ETL process, without FastTrack. The main challenges we’re trying to sort out are:
1. Identifying which out-of-the-box entities must be included in the migration, especially those tied to transaction data (like emails, cases, activities, etc.). Missing the wrong ones could break data relationships.
2. Defining the best ETL approach and tooling for this type of migration. Should we lean toward SSIS with KingswaySoft, Azure Data Factory, or another option? How have others structured their pipelines to balance performance, data integrity, and complexity?
Looking for input from anyone who’s done this—especially lessons learned on entity dependencies and practical ETL strategies that worked (or didn’t).
