Microsoft’s Salesforce Converter Is Public—but It Starts With Discovery

On September 9, 2026, Microsoft introduced Dynamics 365 Activate in public preview for organizations moving from Salesforce to Dynamics 365. The AI-assisted service can analyze a Salesforce CRM environment, recommend migration actions and automate parts of migration execution with built-in guardrails in a Microsoft-hosted experience.

The preview is public, but it is not a generally available, end-to-end converter. The Register’s September 10 coverage identifies Salesforce as the first supported migration scenario and discovery as the process that gives implementation teams a blueprint for deciding what should move, change or be redesigned.

Discovery is the preview’s clearest capability

Dynamics 365 Activate starts by building a structured view of the source CRM environment. It profiles data and entities, identifies relationships and dependencies, examines business processes and surfaces customizations that require attention. Published product imagery also shows assessment categories for Salesforce objects, workflows, code, integrations and related components.

That analysis matters because a CRM estate is not merely a collection of records. Its data model can reflect years of operating decisions, while workflows, custom code and integrations may depend on one another in ways that make isolated conversion unsafe. Activate is intended to expose those connections before implementation teams decide what belongs in the destination.

The resulting blueprint is an input to migration planning, not the completed migration. Context established during discovery can carry into business-process decisions, solution design, configuration, migration, testing and deployment, reducing the need to reconstruct the same information as work passes between teams.

The migration map combines automation and assistance

The announced scope covers a broad implementation path, but no field-by-field compatibility matrix or guarantee of automatic conversion for every Salesforce component has been published. The work therefore separates into stages with different levels of tool support:

• Discovery: Activate profiles the source environment’s data, entities, processes, customizations and dependencies.
• Dependency analysis: It identifies relationships and potential issues so connected components are not assessed in isolation.
• Solution design and configuration: The announced capabilities include requirements analysis and configuration generation. The available description does not enumerate every supported configuration type or the manual refinement each output may require.
• Data movement: Automated migration execution with guardrails is part of the preview. Data selection, cleansing, reconciliation and acceptance are not presented as fully automated responsibilities.
• Validation and testing: Discovery context can inform testing and deployment. Agentic mapping and test sampling are planned capabilities, so they should not be treated as guarantees of the current preview.
• Cutover: Activate may provide migration results and retained context, but production sequencing, release approval and retirement of the Salesforce environment remain outside the defined automation scope.

“Automated migration execution” consequently describes one capability within a larger transformation. It does not establish that a particular company’s objects, permissions, integrations, custom logic and historical data can all move without intervention.

Redesign and validation remain human work

The objective extends beyond recreating an existing CRM in Dynamics 365. For each significant customization, customer and partner teams still have to decide whether to preserve its behavior, replace it with a native Dynamics capability, redesign the underlying process or leave it behind. Activate can supply evidence about the current environment, but those choices depend on business requirements and ownership decisions.

The boundary is reinforced by CIO’s analysis of the preview, which identifies poor data, complex integrations, custom business logic, regulatory requirements and organizational change as continuing migration challenges. The analyst assessment characterizes Activate as an accelerator rather than an autopilot.

Validation is therefore more than a final sign-off. Implementation teams still need to determine whether migrated records reconcile with the source, security roles and retention requirements work as intended, integrations behave correctly and redesigned processes meet their owners’ requirements. The preview promises greater visibility and earlier risk identification, not automatic acceptance of those outcomes.

Change management lies beyond the converter

A successful technical transfer does not make sales, service and operations teams ready for a new system. Process ownership, training, support arrangements, role changes and adoption remain part of the implementation. The product’s human-led model leaves partners responsible for methodology, industry expertise, solution architecture and change management.

Cutover governance likewise remains with the customer and its implementation partners. They must determine whether users move together or in waves, how overlapping Salesforce and Dynamics 365 operations will be controlled, what triggers rollback and when the source platform can be decommissioned. Retained implementation context can support those decisions, but it does not supply operational authority.

Salesforce is the starting scope

The confirmed preview scenario is migration from Salesforce to Dynamics 365. The broader product vision includes new Dynamics implementations, extensions to existing Dynamics environments and migrations from other CRM and ERP products. ERP capabilities are expected later in 2026, while additional source-platform scenarios remain forthcoming.

General-availability timing, pricing, regional coverage, preview capacity and a detailed inventory of supported Salesforce components have not been specified. Until those details and fuller technical documentation appear, Dynamics 365 Activate is best understood as a discovery-led migration accelerator with some automated execution—not evidence that a Salesforce estate is ready for complete, unattended conversion.

Also read:

• Salesforce Release Management Now Starts in Source Control, Not a Sandbox
• Bitcoin’s HODL Era Is Fraying, but the Data Does Not Show a Great Purge
• Internet Banking Skips the Branch Visit—but Not the Security Work