Upgrade from AX 2012 - Prepare for go-live
This feature is currently available by invitation only. To nominate your organization to participate, please complete this survey.
Upgrade is currently supported from either Dynamics AX 2012 R2 or AX 2012 R3 only.
As the go-live date approaches, it's important that you implement this series of steps to help guarantee that the source Microsoft Dynamics AX 2012 system and the upgrade process both remain stable and consistent for go-live.
As part of this process, you must lock down any further code changes or application setup changes before you run the final cutover test.
All code changes in the AX 2012 environment should be frozen. Implement an escalation process to handle any critical issues that appear in AX 2012. By default, any new code changes that are required should be implemented only in the new system, not in the AX 2012 environment. Implementation of proposed code changes in the AX 2012 environment should be discussed at the management level. If a code change is made in AX 2012, the same change must be made in the new system. In that case, another iteration of cutover testing and functional testing might be required.
Application configuration freeze
All application configuration changes should be frozen in the AX 2012 environment, because these changes could affect how the new system behaves or how the data upgrade scripts behave. Configuration changes are changes in the AX 2012 application that are related to the configuration of system functionality. By freezing these changes, you help guarantee the stability of the data upgrade process.
Because configuration changes are typically controlled by the AX 2012 system administrator or a small group of trusted super users, we don't recommend that you enforce the freeze by changing security access. Instead, implement the freeze through a business process that is communicated to those users. Changes to security access might require a code change (changes to the role definitions themselves) or a configuration change (reassignment of users), and these changes could affect the upgrade process.
Running the final cutover test
After no further code or setup changes will occur, run a final cutover test to make sure that all data and code upgrade tasks still run as expected.
You must complete this step even if you freeze code and setup changes at the beginning of the upgrade project, because the data itself changes every day. This final cutover test also validates that the current data is upgraded successfully.
Make sure that functional testing is performed against this last upgraded copy.
At this point in the upgrade project, we recommend that you categorize any bugs that are found:
Blocking – The upgrade project can't proceed until every bug of this type is fixed. The upgrade must be postponed, and can proceed only after the bug is remediated and the cutover test is run again. For a bug to be classified as blocking, it must meet these conditions:
- It prevents a critical business process from being completed.
- No workaround or mitigation is available for it.
Non-blocking – The upgrade project can proceed. Bugs of this type can be fixed in the upgraded system.