AX Upgrade path opinions

(0) Share

Report

Posted on by DPerko

417

All -

Not sure where best to post this but I am looking for some opinions. I am working with a company that has three manufacturing warehouses. One is live on an HIGHLY customized AX2009 instance and the other two are on their original legacy system. They would like to get all three locations live on AX but I am struggling with the best approach to suggest.

My first reaction was to bring the two locations from Legacy to AX2012R3 using as much standard logic as possible and then upgrade/move the 2009 data to 2012.

Option two would be to upgrade the 2009 location and then bring the other two up.

Option three would be based on the assumption that the functionality in AX7 will be the same or similar to 2012. We could do the process mapping, AS IS and TO BE in 2012 knowing that we were going to go to AX7.

Does anyone have any opinion on the best approach here? I am struggling since I normally go for the latest and greatest especially knowing that they are just starting this journey. But with 7 on premise not being available until late this year I am not as sure of my answer.

Thanks

Dan

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Sort by

André Arnaud de Cal... 306,118 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi DPerko,

The first option is not possible. First you need to upgrade data from an older version, then you can add new data. This is related to scripts which are highly depending on unique record-IDs.

You are correct that the private cloud/on premise will be only available later this year. Currently there is no data upgrade supported for the new Dynamics AX, but that will be part of the next release, thus also when on-premise is supported.

You can either wait for theon-premise or now go for AX2012R3. If you want to move to a new version, probably waiting could be worth it, as you are on the latest technology and version then.

Was this reply helpful? Yes No
Konrad U 804 on at

Like
a
(0)

Report
Copy link

Link copied!

Conversion of AX 2009 data to AX 2012 is not for the faint of heart (if it works). The holes in AX 2009 that allowed copious bad data to exist and a restrictive conversion to AX 2012 forced us to re-implement. Unless you absolutely need a 2012 feature I would recommend waiting for AX7. It would be jarring to force users through two major changes in UI in a short period of time. I do agree that AX 2012 would have to be vanilla due to the cost of code conversion.

Was this reply helpful? Yes No
Brandon Wiese 17,790 on at

Like
a
(0)

Report
Copy link

Link copied!

Without knowing any more than what you've provided to us, I would prefer to migrate the legacy systems into AX 2009, which will likely take some time, at which point the path from AX 2009 to AX 7 will be more mature, and you can then upgrade all 3 live companies in AX together.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

As you said the AX2009 is highly customized, upgrade to 2012 won't be an easy one. Data upgrade to AX2012 will need lot's of custom scripts from your side to get all the legacy data inside.

I would suggest to take up AX7. The new data management in AX7 will help you a lot better than AX2012 in getting the legacy data imported into the system. I wouldn't bother much about hosting in Azure as it is cost effective too

Was this reply helpful? Yes No