A migration assessment is the first step to help you understand the value of and steps to cloud migration<\/p>\n<\/div>
OBJECTIVES<\/b><\/h3>\n
A migration assessment is the first step on your cloud journey, which will help to:<\/p>\n
\u2022 Understand the benefits of moving from an older on-premises solution to the cloud<\/p>\n
\u2022 Identify business objectives and tie these into the functionality of Dynamics 365<\/p>\n
\u2022 Learn how to optimize the migration process with a focus on reducing effort and costs<\/p>\n
\u2022 Determine your next steps toward cloud transformation<\/p>\n
<\/h3>\n<\/div>ASSESSMENT WORKSHOPS MAIN COMPONENTS:<\/h3>\n1. Functional \/ business assessment<\/h4>\n
This component examines your current business processes and assesses how you may be able to benefit from new capabilities and enhancements by moving to the cloud. This assessment includes:<\/p>\n
\u2022 High-level business process and functional review:<\/strong> Understand your current business processes that are being managed in your on-premises version of Dynamics AX and map that to the capabilities of Dynamics 365<\/p>\n\u2022 Customization, ISV and interface assessment:<\/strong> High level assessment of Dynamics AX customizations and ISV-implemented solutions in your current environment. The primary goal of this step is to assess the expected effort and identify the business dependencies involved when migrating to Dynamics 365<\/p>\n\u2022 Dynamics 365 system review:<\/strong> Get a summary and high level roadmap of new Dynamics 365 functionality<\/p>\n<\/h3>\n<\/div>2. Technical assessment and tools<\/h4>\n
Customer estimated time commitment: About one hour<\/strong><\/p>\nTo initiate the technical assessment, you simply permit our migration assessor AX system access to help them identify your current technical architecture. This information will then be used to develop an analysis of your current code and determine how it can best be leveraged in Dynamics 365. Microsoft will not access \u2013 nor should you provide access \u2013 to Peronally Identifiable Information (PII) that is housed within your current Dynamics AX On-Premises solution.<\/p>\n
Examples from Dynamics AX 2012 technical assessment reports<\/strong><\/p>\n<\/h3>\n<\/div>![](\"https:\/\/etg-it.ca\/wp-content\/uploads\/2021\/05\/figure-2-5.jpg\" "\\"figure")
<\/span><\/div><\/div><\/div>
ASSESSMENT WORKSHOPS MAIN COMPONENTS:<\/h3>\n1. Functional \/ business assessment<\/h4>\n
This component examines your current business processes and assesses how you may be able to benefit from new capabilities and enhancements by moving to the cloud. This assessment includes:<\/p>\n
\u2022 High-level business process and functional review:<\/strong> Understand your current business processes that are being managed in your on-premises version of Dynamics AX and map that to the capabilities of Dynamics 365<\/p>\n \u2022 Customization, ISV and interface assessment:<\/strong> High level assessment of Dynamics AX customizations and ISV-implemented solutions in your current environment. The primary goal of this step is to assess the expected effort and identify the business dependencies involved when migrating to Dynamics 365<\/p>\n \u2022 Dynamics 365 system review:<\/strong> Get a summary and high level roadmap of new Dynamics 365 functionality<\/p>\n Customer estimated time commitment: About one hour<\/strong><\/p>\n To initiate the technical assessment, you simply permit our migration assessor AX system access to help them identify your current technical architecture. This information will then be used to develop an analysis of your current code and determine how it can best be leveraged in Dynamics 365. Microsoft will not access \u2013 nor should you provide access \u2013 to Peronally Identifiable Information (PII) that is housed within your current Dynamics AX On-Premises solution.<\/p>\n Examples from Dynamics AX 2012 technical assessment reports<\/strong><\/p>\n<\/h3>\n<\/div>
2. Technical assessment and tools<\/h4>\n
<\/h3>\n<\/div>
<\/span><\/div>