A company wants to upgrade their current AX 2009 system to Dynamics 365
You need to recommend a supported upgrade strategy for code and transactional data for the previous five years.
Which two options should you recommend? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.AC.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/data-migration-toolWhen upgrading from AX 2009 to Dynamics 365, it is essential to plan a supported upgrade strategy for both code and transactional data. The strategy should minimize the impact on the business processes and ensure that the upgrade is performed efficiently.
Option A: Use the Data migration tool (DMT) to move the data from AX 2009 to Dynamics 365.
This option involves using the Data migration tool (DMT) to migrate the transactional data from AX 2009 to Dynamics 365. The DMT is a free tool that is available for use with Dynamics 365 Finance and Operations. The tool can be used to migrate data from a variety of sources, including AX 2009. The DMT provides a simple and easy-to-use interface for data migration, which can be used to migrate the transactional data for the previous five years.
Option B: Use Lifecycle Services Code upgrade tool to directory upgrade the code base from AX 2009 to Dynamics 365.
This option involves using the Lifecycle Services (LCS) Code upgrade tool to upgrade the code base directly from AX 2009 to Dynamics 365. The LCS Code upgrade tool is a free tool that is available for use with Dynamics 365 Finance and Operations. The tool can be used to upgrade the code base from AX 2009 to Dynamics 365. The LCS Code upgrade tool provides a step-by-step approach to upgrading the code base, which can be used to ensure that the upgrade is performed efficiently.
Option C: Upgrade code from AX 2009 to AX 2012, and then AX 2012 to Dynamics 365.
This option involves upgrading the code from AX 2009 to AX 2012, and then upgrading from AX 2012 to Dynamics 365. This is a more complex upgrade strategy, as it involves two separate upgrades. However, this approach may be necessary if there are significant customizations or complex integrations that need to be addressed during the upgrade.
Option D: Use the Data Import/Export Framework to migrate the data from AX 2009 to Dynamics 365.
This option involves using the Data Import/Export Framework to migrate the transactional data from AX 2009 to Dynamics 365. The Data Import/Export Framework is a free tool that is available for use with Dynamics 365 Finance and Operations. The tool can be used to migrate data from a variety of sources, including AX 2009. The Data Import/Export Framework provides a flexible approach to data migration, which can be used to migrate the transactional data for the previous five years.
In summary, options A and B are the recommended upgrade strategies for code and transactional data for the previous five years. Option A involves using the Data migration tool (DMT) to migrate the transactional data, while option B involves using the Lifecycle Services Code upgrade tool to upgrade the code base directly from AX 2009 to Dynamics 365. Option C may be necessary in certain cases where there are significant customizations or complex integrations, while option D provides a flexible approach to data migration.