Microsoft says the Salesforce CRM migration path inside Dynamics 365 Activate is now generally available, after a public preview that began in September. The ERP half of the product, aimed at SAP ECC and other legacy systems, is still in private preview.
What Microsoft announced
Dynamics 365 Activate is described in a Microsoft Dynamics 365 blog post dated November 19 as an agentic experience that helps customers and partners move from legacy ERP and CRM systems, such as Salesforce and SAP ECC, to Dynamics 365. Swamy Narayana, Vice President of Customer Success and Experience for Dynamics 365, wrote the post. The tool shows how the current system is configured and used, helps teams decide what to keep, and carries those decisions through the migration. Microsoft says it builds on FastTrack for Dynamics 365 and Success by Design.
Microsoft also gave one usage figure: in early CRM engagements, Dynamics 365 Activate has already processed more than seven billion records. It did not say how many customers or projects that covers, and it did not mention pricing or incentives.
What the Salesforce path covers
The CRM side runs in three stages, with Dynamics 365 Sales, Dynamics 365 Customer Service and Microsoft Dataverse as the targets.
- Assessment. The tool inventories Salesforce objects, fields, flows, custom Apex code and integrations. It explains custom code in plain language, rates complexity and effort, and produces a shareable readiness report.
- Mapping. AI-assisted mapping matches Salesforce data to Dataverse tables and columns, with prebuilt mappings for common records such as accounts and contacts. It also maps security roles and business units and deploys the schema after approval.
- Data migration. The tool moves records, files and attachments. It supports trial runs, incremental deltas and resumable loads, and includes real-time monitoring and automated record-count reconciliation.
The ERP experience follows the same shape for SAP ECC and similar systems: discovery of configuration, customizations and integrations, requirements mapped to the Microsoft Business Process Catalog, proposed configuration that teams review before it is applied, and data mapping with checks for gaps and posting errors. Microsoft says that part is in private preview, and preview features are not intended for production use.
Where each piece stands
- Salesforce CRM migration: generally available.
- ERP experience, including SAP ECC: private preview.
The split matters to anyone planning a CRM move now. Only the Salesforce path is cleared for production use, according to Microsoft’s own availability note.
What partners say
The post carries comments from four implementation partners and customers. Kevin Blott, Director, Delivery at Argano, said discovery surfaces scope and sizing inputs that used to take weeks, adding: “Now our first conversations don’t have to start with assumptions” and can start with what customers are actually running. John Scandar, SVP Microsoft Practice at Alithya, said: “Dynamics 365 Activate lets our consultants spend less time on setup and more time on transformation.”
Nauman Choudhry, Chief Information Officer at SpringTide Holdings (Flomatic), described the ERP side, saying agentic capabilities that apply proven best practices create “an opportunity to make this process more reliable and consistent.” Abi Sridhar of Avanade’s Global Customer Engagement go-to-market team said migrating years of customer and operational data is often a major hurdle.
What a live pipeline needs from a migration
The data-migration stage lists trial runs, incremental deltas, resumable loads and automated record-count reconciliation. Those are the features a team that cannot stop working its pipeline will look at first. A trial run shows what breaks before cutover, a delta load picks up the records reps changed in the meantime, and reconciliation gives an admin a count to check against the old system. Microsoft does not say how long a typical cutover takes or how many Salesforce orgs have gone through one, so buyers should ask a partner for both numbers.
The mapping stage also covers security roles and business units. For a sales organization with territory, team and manager-visibility rules built into Salesforce, that is the part of a move most likely to cause an argument, because those rules decide who sees which account. Microsoft says the schema deploys only after approval, which leaves the review with the customer.
What it means for the sales leader
Microsoft’s pitch gives the sales organization a document before it gets a project plan. The readiness report lists the objects, fields, flows and Apex code a team has built up in Salesforce, with complexity and effort ratings. Whether or not a company ever moves, that inventory shows how much of its pipeline process lives in custom code that only one admin understands.
In our reading, the first question for a RevOps leader is which customizations still earn their keep. The tool asks teams to decide what to keep before it migrates anything, so the decision lands with sales leadership and not only with the implementation partner.
The timing also lines up with other vendors pitching shorter moves. We reported earlier on ServiceNow’s claim that AI discovery can cut CRM migrations to weeks, and on Salesforce and Microsoft’s Copilotforce partnership, which put Salesforce sales workflows inside Copilot. Microsoft is now selling a path off Salesforce while Salesforce is working with Microsoft on the other side of the same buyer relationship.
What to do with it
Teams considering a move can request the readiness assessment and compare its effort ratings against their own estimate before talking to a partner. Teams staying on Salesforce can use the same inventory logic internally: list every flow and Apex class, name an owner for each, and retire the ones nobody can explain. Microsoft lists sign-up and overview links, and a partner or FastTrack eligibility check, as the ways to start.
Source: Microsoft Dynamics 365 blog

