AX Code Upgrade steps are valid or how to go about it?

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 6 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #20591

    John
    Participant

    Requirement for Upgrading AX 3.0 to AX 2012

    Upgrade Steps:
    1. Code Upgrade from AX 3.0 to AX 2009
    2. Data Upgrade from AX 3.0 to AX 2009
    3. Code upgrade from AX 2009 to AX 2012 R2.
    4. Data Upgrade from AX 3.0 to AX 2012 R2.
    5. Repeat the data upgrade steps for AX 3.0 to AX 2009 to bring the delta data after cutover.
    6. Repeat the data upgrade steps for AX 2009 to AX 2012 R2 to bring the delta data after cutover.

    At this stage we are concerned about the data upgrade steps that we are going to perform for the delta data. By this we will be having a longer cutover period and we have to pre-process the data again starting from AX 3.0.We think it is a pain factor for the Customers and Partners.

    So, Could anyone please let us know if the above steps are valid or how to go about it?

    #20921

    Locus IT
    Participant

    Hello John,

    The upgrade code provided by Microsoft does not allow you to have any delta period when going from AX 3.0 to AX 2012 R2 – the only option for any type of delta period is if you actually go live on AX 4.0 or AX 2009 for a period of time prior to doing the upgrade to AX 2012 R2, but that is not an option that is very realistic.

    The recommendations from a Microsoft perspective on making the jump from AX 3.0 to AX 2012 R2 would be to seriously consider the approach of implementing a new AX 2012 R2 install and using a tool such as the Data Import Export Framework or other integration tool to migrate in beginning balances, master data, etc. and to setup your business to take advantage of the new features of AX 2012 rather than to try and push all the data from 3.0 in its same format into AX 2012. This would require keeping alive either a virtualized or reporting environment for your 3.0 historical data.

    If you do want to bring forward all data – the recommended way to do that from Microsoft is to upgrade to AX 4.0 as your intermediate step rather than AX 2009, but you have to basically have your system down during the entire timeframe of going from AX3 to AX 4 to AX 2012 which can be unrealistic for many customers with any sizeable amount of data. The main reasons for going to AX 4 in between are to avoid having to activate multi-site in AX 2009 between the two steps and also to avoid an intermediate data conversion for address records that was done with AX 2009.

    There is no level of delta processing in the built in tools that can be done to accomplish your steps 5 and 6 above when upgrading from AX 3.

    #20593

    Abigail Donovan
    Participant

    Hi John,

    Data Upgrade from AX2009 will have 2 major stages,

    one is data pre-processing which happens in the source system. Here the data is converted to shadow tables which has same schema as the target tables. Downtime is required only for a short period here while the data is copied to the shadow tables.

    second is Data upgrade in the target system, where the data is copied from Source to target. You need to have downtime during this stage

    You can plan for 2 days of downtime for completing a data upgrade from AX2009 to AX2012 R2 or R3

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar