Microsoft Dynamics 365 Activate gives organizations another way to understand a Salesforce environment before planning a move to Dynamics 365. That could make discovery more structured, especially in environments where years of customization have made it difficult to see which data, integrations, workflows, and dependencies still matter.
The first public preview focuses on Salesforce-to-Dynamics 365 migration. Microsoft describes Activate as an artificial intelligence (AI)-powered implementation experience that can analyze the source environment, identify dependencies and migration risks, generate recommendations, and automate parts of migration execution. For implementation teams, the interesting part may be what happens after that analysis.
Discovery Is Only the Beginning
Migration discovery has always required more than an inventory of tables and fields. Teams need to understand why a customization exists, who depends on it, what integrations it supports, and whether the original requirement still applies. That can be difficult in a mature customer relationship management (CRM) system.
A field that appears unused may feed an integration. A workflow that looks redundant may support a regional sales process. An old customization may still exist because the business process around it was never revisited.
Dynamics 365 Activate can help surface more of that context earlier. Microsoft also separates Activate discovery from migration execution in its partner guidance. Findings from discovery feed later decisions about what should move, change, or be left behind. That distinction matters because identifying something in the source environment does not automatically mean it belongs in Dynamics 365.
The Source Environment Should Be Questioned, Not Recreated
A mature Salesforce environment contains both business knowledge and historical baggage. Some customizations represent important requirements. Others may have been created years ago to work around platform limitations, support an old process, or solve a problem that no longer exists.
Consider a Salesforce organization with 200 custom opportunity fields. Dynamics 365 Activate may help identify those fields and their dependencies. The implementation team still needs to determine which ones support the future sales process, which requirements can move to native Dynamics 365 capabilities, and which fields should disappear altogether. That is where migration becomes an architecture decision rather than an inventory exercise.
A source CRM system is evidence of how the business evolved, not a specification to copy.
A Carry-Forward Test for Dynamics 365 Activate
When Dynamics 365 Activate surfaces a customization, integration, workflow, or data dependency, New Dynamic uses five questions to decide whether it belongs in the target environment.
1. Which existing processes are still strategically important?
Longevity alone does not prove that a customization still deserves to exist.
2. Which requirements can move back to native Dynamics 365 Customer Engagement capabilities?
Years of platform-specific workarounds may no longer be necessary in the Microsoft environment.
3. Which integrations should survive the migration?
A migration creates an opportunity to question system boundaries rather than automatically reconnect every dependency.
4. Where can Microsoft Power Platform replace legacy customization?
Configuration, Power Automate, Dataverse, and other native capabilities may simplify logic that was custom-built on the source platform.
5. Is the target Dynamics 365 architecture ready to scale?
The data model, security, business units, solutions, integrations, ownership model, and application lifecycle management need to support the organization after migration, not only at go-live.
The principle behind all five questions is simple:
Every legacy component should earn its place in the target environment.
What Activate Changes About the Salesforce-to-Dynamics 365 Decision
One challenge in a CRM platform evaluation is that leadership may know the current environment is complicated without knowing where that complexity is concentrated. A renewal, increasing platform costs, an upgrade decision, or accumulated customization debt can create a natural point to reconsider the current CRM system. Better discovery can make that conversation more specific.
Instead of asking whether a Salesforce migration is simply too complex, teams can ask which integrations create risk, which customizations still serve the business, and where redesign would provide more value than recreation. Organizations already using Microsoft 365, Azure, Power Platform, Fabric, or Copilot should also consider ecosystem fit.
That evaluation still needs to account for the organization’s actual architecture, business processes, governance requirements, and long-term operating model. Dynamics 365 Activate adds another source of evidence to that decision. It does not make the platform decision on the organization’s behalf.
What I Would Watch as Activate Develops
Dynamics 365 Activate is still in public preview, so I would avoid assuming specific time or cost savings until organizations can validate them in their own environments. The more useful early questions are practical ones.
Does Activate expose dependencies that teams previously missed? Does it improve the quality of migration planning? Does discovery context carry forward cleanly into architecture, testing, and deployment? Does it help teams distinguish requirements worth preserving from technical debt worth leaving behind?
Those answers will matter more than how quickly the source environment can be inventoried. Dynamics 365 Activate changes the starting point of the migration conversation by giving teams more context earlier. The value of that context will depend on the decisions made after discovery.
Knowing what you have is not the same as knowing what you should take with you.
For additional context, Microsoft has published its Dynamics 365 Activate announcement and Dynamics 365 implementation guidance.
Originally published by New Dynamic: https://www.newdynamicllc.com/microsoft-dynamics-365-activate-crm-migration
