Planning Your Upgrade from Dynamics AX 2009 to Dynamics 365 Finance and Operations
Your organization has determined it is time to explore an upgrade from Dynamics AX 2009 to Dynamics 365 for Finance and Operations, now what? From customizations and reports to business processes and the cloud vs. on-premises conundrum, the task of upgrading your system might seem daunting. In the recorded webinar we discuss navigating your upgrade path, including:
- Licensing
- Scoping
- Planning
- Execution
[button title="Register for our upcoming webinar" link="https://msdynamicsworld.webex.com/mw3200/mywebex/default.do?nomenu=true&siteurl=msdynamicsworld&service=6&rnd=0.2956528062168484&main_url=https%3A%2F%2Fmsdynamicsworld.webex.com%2Fec3200%2Feventcenter%2Fevent%2FeventAction.do%3FtheAction%3Ddetail%26%26%26EMK%3D4832534b00000004139f5781ece7c986736d857a3a8cedd08eedc8e027d57126b50ee9da744c646d%26siteurl%3Dmsdynamicsworld%26confViewID%3D91140181108751473%26SourceId%3Dstn%26encryptTicket%3DSDJTSwAAAASukTPM2xPv_01NqfUNSK95yrHRIFDr3efIYQalrHQXtA2%26" new_tab="yes"]
Or, watch the video to gain an understanding of the effort involved, the investment needed, and the best timeline to upgrade your system to Dynamics 365.
https://youtu.be/Tb3oQj7k0QU
Tips for Dynamics AX 2009 to Dynamics 365 Upgrade Execution
When upgrading from AX 2009 to D365 there are many things to keep in mind while you execute the upgrade. Here are just a few of them:
1. Development environment
Keep an AX 2009 development environment with production data available while going through the upgrade process. Testers and developers will frequently access this machine to reference how functionality and the data behaved in 2009.
2. Replacement processes
Identify replacement processes for deprecated features used in 2009. If deprecated processes are critical to your operations, get comfortable with the replacement processes in D376 before going live. You don't want to get caught in a tough situation.
3. Adopting new options
When possible, consider adopting new modules/ISVs/processes in D365 in a phase following the upgrade. If you add new processes into the mix while upgrading, you interject more change than is necessary at one time. If you run into an issue with the new modules, it is difficult to know whether the issue is with the software or migrated data or if it is due to a lack of understanding in the new process.
4. Migrating data
There is not a data upgrade path from 2009 to D365, the data must be migrated. Microsoft provides a tool/hotfix you install into your AX 2009 environment that extracts data to files. Another part of the tool is a setup form where you tell AX where, in Lifecycle Services (LCS) to push those files with your extracted data. Sort through what data you want to migrate and then get the tool installed in your 2009 environment so are familiar with it.
5. Review customizations
In your AX 2009 production environment navigate to Administration > Reports > System > Element usage log and run the report. The report tells you when each ISV, custom and customized form was last used. If you have customizations not being used, save some time and money and don’t recreate them in D365.
If you're interested in learning more about how to set up your organization for a successful upgrade from Dynamics AX 2009 to Dynamics 365, check out our fixed-price assessment offering.
[button title="Talk to Us About Your Upgrade" link="/contact-us/" new_tab="yes"]
Under the terms of this license, you are authorized to share and redistribute the content across various mediums, subject to adherence to the specified conditions: you must provide proper attribution to Stoneridge as the original creator in a manner that does not imply their endorsement of your use, the material is to be utilized solely for non-commercial purposes, and alterations, modifications, or derivative works based on the original material are strictly prohibited.
Responsibility rests with the licensee to ensure that their use of the material does not violate any other rights.