Microsoft has expanded Dynamics 365 Activate beyond CRM migration, bringing its agentic implementation experience into ERP projects. The Salesforce-to-Dynamics 365 CRM migration experience is now generally available, while the new ERP experience—including SAP ECC discovery, requirements analysis, configuration and data migration capabilities—is in private preview. The distinction matters: buyers can evaluate the CRM migration path as a released capability, but should treat the ERP experience as an early-access programme rather than a production-ready migration service.
Announced at Microsoft Ignite on 19 November 2026, Dynamics 365 Activate is designed to help customers and implementation partners assess an existing business application environment, decide what should move forward and carry approved decisions through implementation. Microsoft positions it as an agentic experience built on its FastTrack and Success by Design implementation practices.
What is changing in Dynamics 365 Activate?
The latest announcement establishes two different availability milestones:
- Salesforce CRM migration: generally available. The experience helps assess Salesforce environments and migrate relevant configuration and data to Dynamics 365 Sales, Dynamics 365 Customer Service and Microsoft Dataverse.
- ERP migration experience: private preview. The initial focus is SAP ECC discovery, with requirements analysis, configuration and data migration capabilities also described as private-preview experiences.
Microsoft’s release information says the ERP capabilities will roll out over the coming weeks. Private-preview features are not intended for production use and may have restricted functionality. Organisations should confirm eligibility and access directly with Microsoft before planning project dependencies around them.
How the ERP migration experience is intended to work
1. Discover the current SAP ECC environment
Dynamics 365 Activate can analyse configuration settings, customizations, integrations, dependencies and business processes across areas such as finance, procurement, manufacturing, inventory and supply chain. The purpose is to create a more evidence-based starting point for scope, complexity and migration planning.
For example, an organisation may have custom pricing logic, intercompany transactions or production scheduling rules that have accumulated over many years. Discovery can help teams identify which elements remain essential, which could be redesigned around standard capabilities and which may no longer be needed. The assessment is intended to inform decisions; it does not determine the future-state design automatically.
2. Translate findings into business requirements
Microsoft says discovery findings can feed requirements analysis, helping teams translate current processes and workshop input into requirements aligned with the Microsoft Business Process Catalog. This gives customers and partners a structured way to assess where standard Dynamics 365 functionality fits and where process or solution design decisions are still required.
3. Propose and review configuration
The experience is designed to propose configuration in a planned sequence, with prerequisites and implementation guidance. Project teams review and approve proposals before they are applied. Approved changes are described as versioned and auditable, supporting a controlled implementation rather than an unchecked one-to-one recreation of the legacy system.
4. Map, migrate and validate data
Dynamics 365 Activate is also intended to help map master and transactional data to Dynamics 365 data entities, transform and migrate records, and validate the results. Microsoft describes checks for data gaps and posting errors as part of the workflow. Buyers should still establish their own reconciliation criteria, data-retention rules, cutover controls and business sign-off process.
What is generally available for Salesforce CRM migration?
The CRM migration experience has moved from public preview to general availability. Microsoft describes a workflow that inventories Salesforce objects, fields, flows, custom Apex code and integrations; explains custom code; and provides complexity and effort guidance. AI-assisted mapping matches Salesforce data to Dataverse tables and columns, while the migration process supports records, files and attachments, trial runs, incremental deltas, resumable loads, monitoring and record-count reconciliation.
Microsoft says early CRM engagements have processed more than seven billion records. This is a vendor-reported figure and should not be interpreted as a guarantee of migration speed, completeness or outcomes for an individual project. Actual effort depends on data quality, custom code, integration dependencies, security design, process changes and testing requirements.
Implications for ERP buyers and implementation partners
The announcement could change the early stages of ERP transformation by reducing some manual discovery and documentation work. If the tools mature as described, customers and partners may spend less time collecting system facts and more time deciding how the future business should operate.
- Better discovery inputs: a structured view of configurations, customizations and dependencies can improve initial scope discussions.
- More explicit transformation decisions: teams can assess what to retain, simplify, redesign or retire instead of treating every legacy customization as a requirement.
- Partner effort shifts: implementation partners may have more time for process design, solution architecture, change management, testing and adoption—but those activities still require experienced people and customer decisions.
- Preview risk remains: private-preview ERP features should not be assumed to have production support, complete functionality or final commercial terms.
Questions to ask before selecting a migration approach
- Which parts of the legacy ERP estate can the assessment actually inspect, including custom code, integrations, reports and external dependencies?
- How will the project validate the discovered configuration and process inventory with business owners?
- Which customizations should be retired or replaced by standard processes, and who approves those decisions?
- What data entities, history, attachments and transaction types are in scope for migration?
- How will trial loads, incremental changes, reconciliation, cutover and rollback be tested?
- Which capabilities are generally available, private preview or dependent on a separate Microsoft programme?
- What remains the responsibility of the customer and implementation partner, including security, controls, testing and change management?
How this affects the ERP implementation partner market
Automation of discovery and migration preparation does not eliminate the need for a capable implementation partner. It makes partner judgement more important in areas where business context cannot be inferred from system metadata: process redesign, regulatory requirements, operating-model changes, data ownership, exception handling and user adoption.
Buyers should ask prospective partners to show how they will validate automated findings, document transformation decisions and prove data quality before cutover. They should also request a clear responsibility matrix covering Microsoft tooling, partner delivery, customer approvals and post-go-live support.
For a broader architecture perspective, see SeerOmega’s guide to Dynamics 365 data ownership and its practical overview of CRM–ERP integration and duplicate-data risks. These topics become especially important when migration changes which system owns customer, product, finance or operational records.
What organisations should do now
For Salesforce CRM projects, review the generally available Activate experience against the organisation’s actual Salesforce complexity, migration scope and target Dynamics 365 applications. For SAP ECC and other ERP modernisation programmes, use the announcement as a reason to prepare a reliable current-state inventory and define the questions a discovery exercise must answer—but do not build a production plan that assumes private-preview functionality is ready for general use.
SeerOmega view: Dynamics 365 Activate points toward a more AI-assisted implementation lifecycle, but migration quality will still depend on the decisions made by customers and their partners. The strongest programmes will use automation to improve evidence and consistency while retaining human accountability for scope, process design, data validation and go-live approval.
Read Microsoft’s Dynamics 365 Activate announcement for the full availability statement and capability details, alongside its Ignite 2026 Book of News.
