Your company has determined it’s time to explore an upgrade from Dynamics AX 2009 to Dynamics 365 for Finance and Operations, now what? By customizations and reports on business procedures and the cloud on-premises conundrum, the task of updating your system may seem daunting. From the recorded webinar we discuss navigating your upgrade path, such as:
- Licensing
- Scoping
- Planning
- Execution
Or, see the movie to gain an understanding of the effort involved, the investment needed, and the best timeline to upgrade your system to Dynamics 365.

Tips for Dynamics AX 2009 into Dynamics 365 Upgrade Execution
When updating from AX 2009 to D365 there are lots of things to keep in mind while you execute the upgrade. Here are just a few of them:
1. Development environment
Keep an AX 2009 growth environment with production data available whilst going through the update process. Testers and developers will frequently access this machine to reference how functionality and the data gleaned from 2009.
2. Replacement processes
Identify replacement procedures for deprecated features used in 2009. You don’t want to get trapped in a tough situation.
3. Adopting new Choices
When possible, think about adopting new modules/ISVs/processes in D365 in a stage following the update. If you put in new procedures into the mix whilst updating, you interject greater change than is required at one time. If you encounter an issue using all the new modules, it is hard to know whether the matter is using the applications or migrated data or if it is because of a lack of comprehension in the new procedure.
4. Migrating data
There’s not a data update path from 2009 to D365, the data have to be migrated. Microsoft supplies a tool/hotfix you put in into your AX 2009 surroundings that extracts information to documents. Another part of the tool is a setup form where you inform AX where, in Lifecycle Services (LCS) to push those documents with your extracted data. Type through what information you would like to migrate then get the tool set up in your 2009 surroundings are familiar with it.
5. Review customizations
In your AX 2009 production environment browse to Administration > Reports > System > Element usage log and run the report. The report tells you when every ISV, custom and customized form was used. In case you have customizations not used, save a little time and money and do not recreate them in D365.
If you’re interested in knowing more about how to set up your organization for a successful upgrade from Dynamics AX 2009 into Dynamics 365, have a look at our fixed-price evaluation offering.