Upgrading from Dynamics AX 2009 and AX 2012 to Dynamics 365 for Operations brings significant new features and capabilities. Operations is available in three deployment scenarios and three types of user. This article aims to clarify the upgrade process and options.
Support for Dynamics AX continues as follows:
1. Do I have to upgrade to Dynamics 365 in the cloud?
No. There are three deployment scenarios (see no. 2). The cloud-hosted option offers additional benefits and features.
2. What are the deployment scenarios?
D365O deployment is extremely flexible. There are three deployment options: cloud-hosted, on-premises (“local business data”) and hybrid (“cloud + edge”). It is possible to start on one scenario and move to another, in either direction. There are different subscription and infrastructure costs for each scenario.
3. What happens to my existing customisations?
Generally, the older your version of Microsoft Dynamics AX, the more iterations it has undergone, and the more likely the customisations will have to be re-developed for Dynamics 365 for Operations. Custom coding is now done via extensions instead of over-layering. Microsoft has made it a priority to provide code upgrade tools to simplify the migration of custom code.
The code upgrade tools in Lifecycle Services (LCS) assist in evaluating the effort for upgrade before making the commitment, automatically migrate code to the current version, and also streamline the process by providing automated merging and documenting where manual merging needs to be performed.
As Dynamics AX 2012 R3 has a similar data structure to D365 there will be less refactoring required than older versions; and some customisations may now be covered by standard functionality and will not have to be migrated or re-coded.
4. What happens to my existing reports and BI content?
As with custom code, the upgrade process of reports and BI content is a three-stage approach: analyse, execute and validate. Microsoft’s upgrade tools may migrate some SSRS reports and BI cubes from AX 2012 R3, however, content from older versions will need more re-development.
5. What happens to my existing third-party interfaces?
The interface technology has evolved significantly since AX 2009, so the older your version of AX the more likely the interfaces will require re-development. Transition needs to be assessed on a case-by-case basis.
6. What happens to my existing Dynamics AX licences?
Dynamics 365 for Operations is licenced on a monthly subscription per user or per device. The on-premise version may be licenced by monthly subscription or annual perpetual licence.
For existing customers that are active on a Dynamics AX maintenance plan Microsoft is offering a 40% discount on the standard cloud-hosted Dynamics 365 pricing. There are two transition-to-cloud options:
- From SA – allows you to drop your existing maintenance payments at renewal and move fully to the cloud service.
- Cloud Add-on – allows you to continue paying your Dynamics AX maintenance and add the Dynamics 365 SKUs on top of this at any time.
Active maintenance (SA or Enhancement Plan) will be a requirement for on-premises D365 (‘local business data’). On-premises subscriptions will be 55% of cloud pricing.
There are four user types in D365O: Full user/Activity/Team member/Device. Our consultants will be happy to provide more details on how your current users will map to the new user types and which options may be most cost effective for your organisation.
7. What is the upgrade process?
The costs and effort of upgrade are fully evaluated before making the commitment.
8. How long will the upgrade process take?
The following are very general estimates:
- Mostly standard functionality with minimal change to business processes – 2 to 3 months
- Customisations that require re-development – 3 to 6 months
- Customisations and significant re-engineering of business processes – 6 to 9 months
9. Will our staff need to be retrained?
No. Most of the business logic in Dynamics AX is carried forward to D365O, yet the user interface has been greatly improved to provide a more fluid and intuitive experience.
Upgrading from AX 2009 may require more user training – where necessary, this can be supplied throughout the upgrade process to ensure maximum uptake of new functionality and full onboarding at cutover. Additionally, the Task Recorder tool within D365O has been greatly enhanced to provide task guides with step-by-step instructions for completing business processes.
10. Will the upgrade disrupt our operations
No. Whether on-premises or in cloud, D365O is deployed through LCS. New builds are deployed first to test environments.
How much will the upgrade cost?
Our experts will carry out a code and data assessment, including BI and reporting content, interfaces and, if required, business processes, then offer a fixed price to upgrade your system to the latest on-premises or cloud version, including converting and migrating data.
Programming in Dynamics 365 for Operations
A native of London and a graduate in economics, Simon began his marketing and PR career in the music and film industries. Simon is fascinated by the compelling ideas that shape our future and communicates them with passion.