Microsoft Dynamics 365 Activate

(1) Share

Report

Posted on by Travis South

177

Dynamics 365 Activate is starting with Salesforce-to-Dynamics 365 migration and is designed to surface source-system data, customizations, integrations, dependencies, and migration risks. One question I have is how teams plan to validate those findings before turning them into migration decisions.

For example, if Activate identifies a customization or dependency, what would you use to decide whether it should be preserved, simplified, redesigned, or retired in the target Dynamics 365 environment? I would be interested in how others are thinking about the handoff from automated discovery to solution architecture and migration planning.

Categories:

Microsoft Dynamics CRM