Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We are working with one of the existing Dynamics AX 2009 customer and they are planning to upgrade from AX 2009 to AX 2012 R3.
As per few articles circulated in the market by different source, they states that a existing Dynamics AX 2009 customer can’t upgrade to AX 2012 R3 and they can only be upgraded to Dynamics 365.
Could any clarify me on the above query.
It is feasible:
Please check theses, the 1st one is the guide on how to do it:
The upgrade to AX 2012 R3 is indeed possible from AX 2009, and even 4.0 version for existing customers with an active software maintenance contract. Only the license purchases are discontinued for AX 2012 on new implementations, fresh licenses are now only sold for Dynamics 365 for Operations - maybe this was your confusion.
Please read the articles covered in the MSDN documentation for the steps involved:
You are links are referring to 2014 information, but i am referring to latest news spreading in the market about upgrade.
You have the latest news from us. New licenses are not sold for AX 2012 implenetation, but upgrade is possible with an active customer Business Ready Enhancement Plan, using the methodology described on the links above.
If you have any other details, please quote your sources.
The easiest way to verify this is to turn to your Microsoft Partner Account Manager to clarify.
the reason that the general consensus 2 years back was that this is not feasible are mainly due to these changes.
1. Will the new COA take advantage of the extra financial dimensions, if so then how will you map those line by line on legacy transactions (even on opening balances its a chunk of work - its easy to aggregate 5+5 to make 10 but on what basis do you split 10 into two or more new dimension fields? - will you reconcile prior period month ends?)
2, Will you use the new WMS , for long time Microsoft indicated that this would be the only option, but it introduces new inventory dimensions so how will that reflect on your legacy transactions - it means a change to the model group on posted transactions?
There are other potential complexities such as rec ids, global address book, refactoring etc. So given such challenges you have to decide whether the time and effort is better spent on converting the past or just reimplementing with fewer constraints and investing the time saved in the future.
Business Applications communities