Microsoft Introduces Dynamics 365 Activate: What It Means for CRM Migration Projects

Microsoft has introduced Dynamics 365 Activate, an AI-powered tool designed to help organizations move to Dynamics 365 with less manual effort and greater visibility throughout the implementation process.

 

The first capabilities are now available in public preview for organizations migrating from Salesforce to Dynamics 365. Microsoft says Activate can analyze an existing Salesforce environment, identify data, business processes, customizations and dependencies, and use that information to support migration planning and execution.

 

For organizations considering a CRM migration, the announcement raises a more practical question: what does AI-assisted migration actually change for the project?

 

Why CRM Migrations Are More than Moving Data

 

A CRM migration rarely starts with a clean system.

 

Years of customization can leave organizations with complex data structures, workflows, integrations, business rules and processes that are difficult to map from one platform to another. Data quality can vary across departments, while some customizations may no longer reflect how the business operates today.

 

There is also a business side to the migration. Employees need to adapt to new processes and ways of working, making adoption and change management part of the project from the beginning.

 

This makes discovery one of the most important stages of a migration project.

 

Before deciding what to migrate, teams need to understand what they already have and, equally importantly, what they actually need going forward.

 

How Dynamics 365 Activate Aims to Help

 

Activate is designed to bring AI into this part of the implementation process.

 

According to Microsoft, the Salesforce migration capabilities can analyze the existing CRM environment, profile data and entities, identify relationships and dependencies, and surface customizations that require attention. The resulting context can help teams assess migration scope and identify potential issues earlier.

 

The objective is not simply to reproduce the existing Salesforce environment inside Dynamics 365.

 

The information gathered during discovery can help customers and implementation teams decide what to preserve, what to simplify and what to redesign before migration begins.

 

That distinction matters. A successful migration should move the business forward, rather than simply recreate years of accumulated complexity in a new system.

 

What Could this Mean for Customers?

 

For organizations already evaluating a Salesforce-to-Dynamics 365 migration, Activate is particularly relevant during the assessment and planning stages.

 

Its potential value is in making the existing environment easier to understand before major migration decisions are made. That can mean less manual discovery work, better visibility into migration scope and earlier identification of dependencies or potential risks.

 

Does that make Salesforce migration easier? Potentially, particularly where the existing environment is complex. But Activate does not remove the decisions involved in determining what the future CRM should look like. The benefit comes from giving teams better information to make those decisions.

 

It is also not limited conceptually to new Dynamics 365 customers. Microsoft’s broader vision for Activate includes existing Dynamics 365 customers that want to expand into new applications, processes, geographies or business units. For these organizations, the goal is to build on existing business context rather than repeat lengthy discovery for every new implementation.

 

The current public preview, however, is specifically focused on Salesforce-to-Dynamics 365 migration. Microsoft has indicated that additional CRM and ERP migration scenarios will follow, with ERP capabilities planned later in 2026.

 

What Happens to the Implementation Partner?

 

AI-assisted migration does not make implementation expertise less relevant. It changes where that expertise can have the greatest impact.

 

If AI can accelerate discovery and analysis, implementation teams can spend less time reconstructing the legacy environment and more time applying business and industry knowledge to the future one.

 

That includes business process design, solution architecture, data strategy, integrations, testing, governance and change management.

 

For customers, this distinction matters. The technology can help answer what exists and identify potential migration considerations. Experienced implementation teams are still needed to determine what should change and how those changes should work in the context of the business.

 

That is ultimately the significance of Dynamics 365 Activate. It is not simply another migration utility. It reflects a broader shift toward AI-assisted implementation, where more of the analysis can be automated while the decisions shaping the future business environment remain collaborative and human-led.

 

For organizations considering a move to Dynamics 365, the question is becoming less about how much of the old system can be moved, and more about what is worth taking forward.

Extending Standard Data Entity with Fields Coming From a View

When working with Microsoft Dynamics AX, we often encounter with situations where a standard table needs to be extended with more fields that come from a view, when the relation to the view is through RecId.

 

When using the table for data export and import the data management framework can not find the related record coming from the view, so this needs to be set manually in the findEntityDataSource method of the entity, which is used for the import export.

 

Because the scenario involves a standard table and a standard entity, we need to use an extensible solution and in addition of extending data entity we need to add an event handler method that is subscribed onFoundEntityDataSource event.

 

We all know that in our Microsoft Dynamics community we have a lot of challenges with extending the Data management framework, which is the reason for writing this blog post, simply because we wanted to share this findings and try to help and save some time to someone that encounters a similar scenario. 

 

In our case, we were extending the TSTimesheetLine table with fields from the ResourceCategoryView view.

 

 

Next, we were extending the TSTimesheetLineEntity data entity and its staging table. On the TSTimesheetLineEntity we have also added the ResourceCategoryView as a data source and we added CategoryId field to the field list.

 

 

 

 

The AXMResourceCategoryField is not included in the staging table, because it’s the RecId relation field to the ResourceCategoryView and it is set to private in the data entity.

 

The logic that we added here, that is nowhere to be found in the standard Microsoft Dynamics AX, for finding related record of the view in the method that subscribes to the onFoundEntityDataSource event for finding and setting the related view record is as follows: