Microsoft Dynamics 365 for Finance and Operations is a strong ERP solution constructed entirely from the cloud. It enables companies to better manage their financials and operations via smart applications which are simple to tailor, expand, and integrate.
If you are operating on Dynamics AX 2012 R2 or R3, then there’s an update procedure which may be carried to transition into Dynamics 365 for Finance and Operations. Even though you aren’t required to update, mainstream support for Dynamics AX 2012 and AX 2012 R2 will be finishing in October 2018, whilst R3 finishes in October 2021. It’s thus suggested to initiate the preparation process for your update.
For different variations of AX, a re-implementation alternative is available to migrate the information and alterations you need to a fresh version of Dynamics 365 Finance and Operations.
The update procedure encompasses three stages :
Upgrading Dynamics AX 2012 Pt. 1: Analyze
The main aim of this analyze phase would be to estimate the work and resources necessary for the update to Dynamics 365 for Finance and Operations.
This will provide you access to this analysis tools which may be utilized to assess your present AX 2012 surroundings and custom code. The general public preview also enables you to deploy your personal presentation Finance and Operations surroundings. After enrolling in the LCS, then be certain that you choose the update methodology’update AX 2012 into Dynamics 365 for Finance and Operations’ to lead you through the update procedure and supply hyperlinks to all supporting files.
The next step is to conduct the update analyzer instrument from the AX 2012 environment. This tool will aid you in identifying information which may be cleaned up without sacrificing any functionality. Additionally, it reviews your current SQL configuration and urges optimization for performance development. Deprecated features which you’re using in AX is going to be emphasized to assist you find gaps in operation and options will be provided.
After getting reports from the update and code analysis tools, then you’re all set to set up a demonstration Dynamics 365 for Finance and Operations surroundings to assess new attributes and carry out a fundamental match gap analysis of conventional characteristics which might have changed in Finance and Operations.
The last step in the test phase would be to make a job plan utilizing the data gained from prior measures. A project plan template is given in the LCS update methodology.
Upgrading Dynamics AX 2012 Pt. 2: Execute
The aim of this execute phase would be to collect identified resources and implement the tasks planned throughout the test phase.
The very first step after buying Dynamics 365 for Finance and Operations is to change in the public preview endeavor to some LCS execution project. This is going to be the permanent LCS job for the subscription and it includes information about surroundings hosted in Azure and any related updates.
After performing pre-upgrade jobs, programmers must finish the code update jobs which were planned throughout the test phase and solve any code battles. Now, functional users will need to work together with the development group to create new alterations utilizing the info from the fit gap analysis that has been performed earlier.
The final step is to execute the information update on your development environment. Following the code update tasks are finished, you can update your AX 2012 database into Finance and Operations. You are going to want to utilize the development environment to execute this first update so any unanticipated issues are readily debugged and solved. The next illustration shows the information update procedure:
Upgrading Dynamics AX 2012 Pt. 3: Validate
Once your environment is prepared with updated custom code and information, you’re all set to kick off the confirm stage. The target of this stage is to perform testing and identification on the updated environment to make sure all company processes are functioning as desirable in prep for go-live.
The very first step would be to execute cutover testing and generate a cutover plan. The aim of cutover testing would be to practice the cutover procedure for go-live.
There are two Chief workstreams:
- Technical workstream – This workstream is the process of running the data upgrade. There will be a limit on the amount of downtime that is allowed. During this downtime, neither AX 2012 nor Finance and Operations will be available.
- Functional workstream – After the data upgrade, several configuration tasks will be required in the Finance and Operations environment. These tasks must be documented, quantified, and assigned to a resource, as they will need to fit within the business’ downtime limit along with the technical tasks.
After cutover testing, you will need to perform a thorough and extensive full functional test pass of all business processes, both old and new. Any code issues found during multiple iterations will be fixed and re-tested to ensure the downstream or upstream process is not affected by any change.
Finally, after successfully completing all business processes in the Sandbox or Acceptance environment, you are ready to finalize a go-live checklist for any configuration changes to be made after full functional testing. Once upgrading your production environment, you are ready to go-live.
Transition Smoothly with Sunbridge Software Services Pvt. Ltd
Here at Sunbridge Software Services we can assist you with your Dynamics AX 2012 upgrade. As a Microsoft Gold Partner, we’ve got the expertise, skills, and tools to smoothly upgrade your existing system with no downtime or impact on operations. Contact our Dynamics AX team for more information about updating to Dynamics 365 for Finance and Operations.