Dynamics 365 Activate Converts Salesforce—ERP Automation Comes Later

Microsoft’s September 9 launch announcement introduced Dynamics 365 Activate with Salesforce-to-Dynamics 365 migration in public preview. The service can analyze a Salesforce environment, produce recommendations and automate parts of migration execution, but it does not make the business decisions required to redesign or approve the destination system.

The Register’s September 10 report independently identifies Salesforce conversion as the scenario available in public preview and places additional CRM and ERP migrations later on the roadmap. Enterprises therefore cannot treat Activate as a generally available converter for arbitrary CRM or ERP platforms.

What the Salesforce preview can automate now

Activate begins by examining the source Salesforce environment. Its discovery functions profile data and entities, identify relationships and dependencies, and surface business processes and customizations that may require attention. That context feeds migration recommendations and helps implementation teams identify potential problems before execution.

The available workflow also includes automated migration execution with built-in guardrails in a Microsoft-hosted experience. The product description covers requirements analysis, configuration generation and data migration, although it does not provide a component-by-component compatibility list showing which Salesforce packages, custom code or third-party integrations can be converted automatically.

This is broader than exporting and reimporting records. Activate carries discovery context into solution design, configuration, migration, testing and deployment, so teams do not have to reconstruct the same source-system relationships at every stage. Carrying context forward, however, is not equivalent to approving the resulting design.

The migration-stage matrix

The current division between product automation and customer responsibility is clearest when the migration is separated into stages. Microsoft’s Dynamics 365 Partner Tools guidance describes discovery inputs and outputs, automated execution, testing context and the approved decisions required from project teams; it also allows partners to sign up for a limited public preview.

• Discovery: Activate analyzes Salesforce data, entities, processes, customizations and dependencies. Selecting the environments, business units and historical records within project scope remains a project decision.
• Dependency analysis: The service identifies relationships and dependencies and highlights customizations requiring attention. It does not determine whether every detected dependency is still needed in the future operating model.
• Configuration generation: Requirements and source context can be used to generate Dynamics 365 configurations. The published material does not transfer approval of the target process, permissions model or operating design to the service.
• Data movement: Activate supports automated execution and produces migrated Dynamics 365 data alongside recommendations and execution results. Retention policy, reconciliation criteria, exception acceptance and cutover authorization are not presented as autonomous product decisions.
• Guardrails: Execution takes place with built-in controls and Microsoft hosting. Those controls are not described as replacements for an organization’s security, privacy, compliance or production-approval procedures.
• Validation: Discovery context and execution results support testing and can expose issues earlier. Business owners and implementation teams still have to verify that records, workflows, permissions, reports and downstream integrations behave as intended.
• Preserve, simplify or redesign: The assessment supplies evidence about the existing environment. Customers and partners decide what should move unchanged, be simplified, be redesigned or be left behind.

The matrix also exposes what has not been promised. Public descriptions do not define a universal acceptance threshold, guarantee that every customization will be converted, or state that a migrated environment can enter production without customer review.

Process redesign remains human-led

Dependency detection answers what is connected; it does not answer what the future business process should be. A discovered custom object or workflow may reflect an essential requirement, an obsolete workaround or a policy that must be implemented differently in Dynamics 365. That distinction depends on business and architectural judgment.

Consider a detected external integration as a conditional example. Activate may carry the relationship into its assessment and migration plan, but the available descriptions do not establish that it can decide whether to retain the connection, replace it with a native Dynamics 365 capability or remove it entirely.

Validation has the same boundary. Technical outputs can establish that data moved and generated components exist, while operational acceptance requires people to test business rules, access rights, reports and dependent applications. The preview accelerates evidence gathering and execution; it does not turn organizational approval into an automated result.

Access is limited, and ERP support is still prospective

Organizations moving from Salesforce can seek access to the public preview, while the partner route is explicitly described as limited. Public preview status is distinct from general availability: the available pages do not provide final pricing, a general-availability date or an exhaustive compatibility list for Salesforce products, marketplace packages and bespoke integrations.

Salesforce is the first named migration scenario. Additional CRM and ERP migration scenarios are planned, with ERP capabilities expected later in 2026, but no complete list of source platforms or release sequence has been published. Finance, supply-chain and other ERP estates should therefore be treated as future scope rather than capabilities inside the current Salesforce preview.

The longer-term vision extends beyond migrations to new Dynamics 365 implementations and changes to existing Dynamics environments. As of September 13, the testable proposition is narrower: Salesforce discovery, recommendations, configuration and migration assistance, subject to human design, validation and deployment decisions. Compatibility details, commercial terms and support for other CRM and ERP sources remain unresolved.

Also read:

• Nine Financial Decisions to Revisit—And Why an Extended Warranty Comes Last
• Your Logo Comes Later: 11 Branding Strategies Startups Need First
• Boston Dynamics Builds Atlas; Hyundai’s Factory Rollout Comes in Stages