Development environment

Keep associate AX 2009 development environment
with production information obtainable whereas hunting the upgrade method. Testers and developers can ofttimes access this machine to reference however practicality and therefore the information behaved in 2009.

Replacement processes

Identify replacement processes for deprecated options utilized in 2009. If deprecated processes square measure essential to your operations, get snug with the replacement processes in Microsoft Dynamic 365 before going live. You don’t need to urge caught in an exceedingly robust scenario.

Adopting new choices

When attainable, take into account adopting new modules/ISVs/processes in D365 in an exceedingly section following the upgrade. If you add new processes into the combo whereas upgrading, you come in a lot of modification than is important at only once. If you run into a difficulty with the new modules, it's tough to understand whether or not the problem is with the code or migrated information or if it's because of a scarcity of understanding within the new method.

Migrating information

There is not a knowledge upgrade path from 2009 to D365, the info should be migrated. Microsoft provides a tool/hotfix you put in into your AX 2009 setting that extracts information to files. Another a part of the tool may be a setup type wherever you tell AX wherever, in Lifecycle Services (LCS) to push those files along with your extracted information. type through what information you wish to migrate so} get the tool put in in your 2009 setting so square measure acquainted with it.

Review customizations

In your AX 2009 production setting navigate to Administration > Reports > System > part usage log and run the report. The report tells you once every ISV, custom and customised type was last used. If you've got customizations not getting used, avoid wasting time and cash and don’t recreate them in D365.
https://sunbridgeglobal.com