[Rudra Kumar]

Hi All,

We are running with AX 2009 version with a good amount of customisation and we would like to upgrade our AX 2009 to the latest version AX 7(Microsoft Dynamics AX) . Since we do not have any announcement from Microsoft about the Upgrade path to AX 7 from AX 2009, could you please help us if anyone has some information about the Upgrade path.

I heard that upgrade should happen through AX 2009 –> AX 2012 R3 –> AX 7, Do we have any latest update about upgrade directly to AX 7 from AX 2009.

I also would like to know when Microsoft has planned to release the AX 7 installer for general availability.

Looking forward for all your valuable inputs…

——————————
Happy DAXing !!!
Many Thanks,
Rudra

——————————

[Johan van Veldhuizen]

Hi Rudra,

A code migration is possible in the way you describe. Personally I would drop all the customizations from AX 2009 and re implement it in ax 7. It’s a totally different application and data model, so it’s wasted time to migrate it. Of course some things will be similar but there is a new warehouse management solution, global address book, global products, different dimension setup, different ledger setup and way more. It’s a new application.

But you can of course migrate your data from ax 2009 to AX7. The standard tools have a lot of limitations and require a lot of development. We have tools to help you to migrate financial history and all other data to AX7 (using ODBC directly) and works with configuration, so it doesn’t require developers to do it.. That will save you a lot of time and risk.

Have a good day,

Johan

——————————
Johan van Veldhuizen
Product Manager of Business Integration Solutions
To-Increase
Veenendaal
——————————
——————————————-

[Rolf van Rijn]

At the AXUG conference an upgrade path was announced from 2009 -> AX7/365 operations. If I recall correctly it was Data only.
any customization would have to be addressed individually.

——————————
Rolf van Rijn
VP, Information Technology
RED DIAMOND INC.
MOODY AL
——————————
——————————————-

[Kelly (Kane) Gustafson]

That is correct, the upgrade path was for data only. However, it would be beneficial to set up a demo environment of the newest version to make sure that some of your business’s needs that have been covered by customizations haven’t already been met. A lot has changed in the product since 2009 and there might be something that addresses your business need for customization in the base product now.

Best of luck on your upgrade journey!

——————————
Kelly Kane
Information Systems Specialist
Algood Food Company
Louisville KY
AXUG Kentucky Chapter Leader
http://www.axug.com/lexington
http://www.axsoup.com
——————————
——————————————-

[Rudra Kumar]

Hi Rolf/Kelly/Oliver,

Thanks for all your valuable responses !!!

It concludes that code migration/upgradation is not possible from AX 2009 –> Dynamics AX7/365 and all the customization has to be recreated in AX7/365.

In Data migration/upgradation, I could see only a Master data and configurations were possible is not acceptable because we have plenty of data’s(transaction) in our AX 2009 and we need all this data. How should we bring this data’s(transaction) into AX7/365 ? MSFT will bring any data migration tool for migrating all the transactions?

——————————
Happy DAXing !!!
Many Thanks,
Rudra
——————————
——————————————-

[Clark Walliser]

Migrating historical transaction data is usually not advised due to the rules and data related to transaction data.
One solution is to implement a data warehouse for reporting purposes.
Migrate your historical and new ERP data  to the data warehouse,
Then run a script to combine the two data sets into one view and do your reporting from that view. 

——————————
Clark Walliser
Business System Analyst
Gigamon Inc.
Santa Clara CA
——————————
——————————————-

[Robert Menschel]

What do you consider historical data?  If we are live on our AX 2009 system on Friday, and key an invoice with 90 day terms, and we migrate to the new system any time during those 90 days, we need to migrate that open invoice so that we can pay our vendor. If we make a sale early in a quarter and collect sales tax, and we migrate to the new system any time during that quarter, we need to migrate that sale so that we can accurately report, file, and pay our sales taxes to the government. More, we need to have that detailed data available for years so that when the government auditors come to us and say they want to review that transaction, we can give them the information showing that we correctly collected and paid the sales tax on that transaction.

Moving from our previous systems to AX we had to leave a lot of our transactional data behind, and we have those previous systems still running on obsolete servers so that we can inquire against that transactional data. If we need to migrate from one version of AX to another every 3-5 years, we cannot afford to lose transactional data each and every time. That is too much of a disruption, and it greatly increases the cost of the ERP.  There has to be a way to bring the data forward.

——————————
Robert Menschel
Lead Systems Engineer
HD Supply Repair & Remodel
Roseville CA
——————————
——————————————-

[Clark Walliser]

Good point. By “historical data” I did not mean the open transactions, only closed.
On other ERP system upgrades from one type to another, we usually ended up manually entering the open transactions. It was a pain, but less of a pain than trying to migrate, then validate it.

And there were cases where even upgrading to a later version of the same ERP required this since the architecture had changed so much.

I’m relatively new to AX, but it looks like each version change involves a major change of architecture.
One listed benefit to the Dynamics 365 SAAS model. It is regularly updated so your data structure stays current

——————————
Clark Walliser
Business System Analyst
Gigamon Inc.
Santa Clara CA
——————————
——————————————-

[Oliver Strutt]

Further to this the current path from AX 2009 is advertised as a “migration”, not an “upgrade” which means that only master data and configuration is brought over (not transactions).

——————————
Oliver Strutt

——————————
——————————————-