A Fast, Trouble-Free Upgrade to AX 2012

Every new version of Dynamics AX comes with a range of attractive features that you might be missing out on simply because you’re worried about how demanding the upgrade process will be. In this article we want to describe how to minimize the time and cost needed to upgrade from AX 2009 to AX 2012.

There are two approaches to upgrading to AX 2012: in-place and source-to-target. Only the latter is suitable for large-scale upgrades.

The goal of the whole Dynamics AX upgrade process is to carry it out quickly, without unnecessary cost or risk, and as transparently as possible for the user. In other words, a user finishes work on Friday in the existing version of Dynamics AX and, on Monday, picks up right where they left off in the new version. In this new version the user will find their settings and data unchanged.

A successful Dynamics AX upgrade can be achieved with two approaches: in-place – the upgrade happens within a single environment that transforms from Dynamics AX 2009 into Dynamics AX 2012 (Microsoft doesn’t recommend this for large upgrades) – and source-to-target – a copy of the Dynamics AX 2009 environment is prepared for the upgrade, Dynamics AX 2012 is installed alongside it, and code and data are then transferred across.

In theory, the upgrade process works as follows: a tool first transfers the code (custom modifications), and developers then resolve any conflicts that arise. On upgrade day, the tool automatically transfers data from the production Dynamics AX 2009 environment into the pre-prepared Dynamics AX 2012 environment.

In practice, neither of the steps above goes entirely smoothly, and plenty of issues need to be worked through. The upgrade needs to be rehearsed as a “dry run” again and again until it goes off without a hitch (essential for completing the upgrade within the agreed timeframe).

Code transfer deserves a chapter of its own. Ideally, you consolidate all customizations in Dynamics AX 2009 into a single layer (not strictly necessary, but it saves time). Unfortunately, the tool can’t transfer changes to certain objects at all (these need to be rebuilt from scratch), and Microsoft’s documentation isn’t complete here either (though the right provider has the know-how to fill the gaps). Conflicts then need to be resolved in the target environment (their number can be reduced by preparing the code in Dynamics AX 2009 beforehand). Depending on how customized objects changed within the SYS layer, the end of the process can also call for further analysis and development work.

Microsoft’s documentation for code transfer isn’t complete, which is why only an experienced provider can pull off a successful upgrade.

After the code transfer comes the data transfer. Ideally, the data transfer happens fully automatically. In reality, though, the tool can’t cope on its own with database inconsistencies, incorrect configuration, and other data irregularities. Developers can resolve some of these issues; others need to be discussed with the customer (business data). Unlike code, the data transfer can’t be done ahead of time – it can only be rehearsed as a dry run. The whole process can only begin once the customer takes their system offline. During the upgrade you’ll face a number of challenges, for example:

• Upgrading a system in an utterly dilapidated state (uncompiled custom modifications across every layer, plus an inconsistent database)
• Solving snags that even Microsoft doesn’t know about
• Having to build your own tools specifically for the upgrade (for example, a tool for reducing conflicts by preparing the code in Dynamics AX 2009 ahead of time)

Before long, upgrading to Dynamics AX 7 will become an important topic in its own right. Although the ERP system Dynamics AX 7 hasn’t been released yet, it’s likely (based on information from Microsoft’s community site) that a direct upgrade from Dynamics AX 2009 (or earlier versions) to Dynamics AX 7 won’t be supported. Upgrading any older version to Dynamics AX 7 will probably only be possible by first upgrading to Dynamics AX 2012 R3 – the only version from which an upgrade to the newest release will be possible. We’ve already mastered the first step; we’ll learn the second the moment Dynamics AX 7 ships.