Upgrade, Migrate or Re-implement from Microsoft Dynamics AX to Microsoft Dynamics 365

With the recent introduction of Microsoft Dynamics 365, many of us are left in question of where we should start in our move from Dynamics AX 4.0, AX 2009 or AX 2012.

 

The good news…you are not alone!

 

To better understand what is the best path forward for you in your quest to Microsoft Dynamics 365, it is important to first understand the difference between upgrading, migrating and reimplementing:

  • This brings the code and data forward

  • Code needs refactored

  • This uses a Microsoft toolset imported into AX09 to massage data forward to D365

  • Code and data structures need to be created in the target environment

  • This is standing up a new D365 environment and implementing using methods such as export/import of data from a legacy environment (ex AX2009 or AS400), manual setups/configurations, etc.

  • Code and data structures need to be created in the target environment

The path forward to Microsoft Dynamics 365 is an exciting one and can be better explained with one of the many scenarios outlined below:

 

The path from Dynamics AX 2012 to Dynamics 365

 

 

When moving from Dynamics AX 2012 you have three options:

 

Path 1: Reimplement

 

You can always reimplement your system.

 

Some of the reasons you may want to consider this option:

  • You have many customization’s that you don’t want to bring forward

  • You need a “clean start” or have significantly changed the way you do business and want to change this in your system

  • Unsupported ISVs

Path 2: Upgrade

 

At the time of writing this, Dynamics AX 2012 R3 is the only supported direct upgrade path.

 

If you are running Dynamics AX 2012 RTM or Dynamics AX R2; this is currently on Microsoft’s roadmap for a direct upgrade.

 

This option is if you want to bring your system forward in its entirety.

The path from Dynamics AX 2009 to Dynamics 365

 

 

When moving from Dynamics AX 2009 you have three options:

 

Path 1: Reimplement

 

You can always reimplement your system.

 

Some of the reasons you may want to consider this option:

  • You have many customization’s that you don’t want to bring forward

  • You need a “clean start” or have significantly changed the way you do business and want to change this in your system

  • Unsupported ISVs

Path 2: Migrate

 

Migrating your data using the Microsoft toolset is the generally recommended path. It allows you to bring forward select data:

  • You have many customization’s that you don’t want to bring forward

  • You need a “clean start” or have significantly changed the way you do business and want to change this in your system

  • Unsupported ISVs

  • You have many customization’s that you don’t want to bring forward

  • Master data like customers, vendors, projects, and accounts

  • Balances from ledgers, stock, and prices

  • Open documents like pending invoices, PO’s, SO’s, etc.

  • System configuration; Number sequences, users, user groups, security, etc.

  • Anything represented as entities

Path 3: Double Upgrade

 

If you need your code and data in their entirety, you could double upgrade. First to AX 2012 R3, then to Dynamics 365 for Finance and Operations, Enterprise Edition. This could give you a potentially more complete set of code and data.

The path from Dynamics AX 4.0 to Dynamics 365

 

 

When moving from Dynamics AX 4.0 you have three options:

 

Path 1: Reimplement

 

You can always reimplement your system.

 

Dynamics AX 4.0 is a very old system, so there is a good chance your business may have fundamentally changed where reimplementing makes the most sense. Some of the reasons you may want to consider this option:

  • You have many customization’s that you don’t want to bring forward

  • You need a “clean start” or have significantly changed the way you do business and want to change this in your system

  • Unsupported ISVs

Path 2: Upgrade then Migrate

 

A very interesting option for Dynamics AX 4.0 users is upgrading to AX 2009, then migrating data to Dynamics 365 for Finance and Operations, Enterprise Edition. The effort to get to AX 2009 from 4.0 could be low enough that it will still produce savings on a data upgrade. The goal would be purely to use the AX 2009 migration toolset, so upgrade corners could safely be cut, such as skipping form and report upgrade efforts and focusing on schema objects.

 

Path 3: Double Upgrade

 

If you need your code and data in their entirety, you could double upgrade. First to AX 2012 R3, then to Dynamics 365 for Finance and Operations, Enterprise Edition. This could give you a potentially more complete set of code and data. This could be considered higher risk though, coming from a very old system and running data through two sets of upgrade scripts.

As your Partner of Record, or Digital Partner of Record, Avantiico is committed to providing you with tailored guidance to fit your organization’s individual need and a roadmap that keeps your team in the know and on track.We offer full upgrading, migrating and implementing of Dynamics as well as any ISV’s your team currently utilizes. Our services team enables you the peace of mind to always know when updated versions are coming up as well as avoiding time spent learning various paths forward.

 

Whether you’d like to learn more or are ready to get started on your path forward to Dynamics 365 our team of experts are standing by to assist:

Let Us Help Today!