Read Before You Migrate from Microsoft Dynamics AX to Dynamics 365
Migrating from one Software to another is never easy because you have to change your usual practices and open up for the new features. But, a good migration plan which consists of a well-thought out structure on how the migration will happen, challenges that you might face, and finally the benefits that you will reap will make it easy for you to migrate. The Plan: If you are migrating from Microsoft Dynamics AX to Dynamics 365, the plan can help you in numerous ways. First, include the details of how the change will roll out and how many phases will it roll out in (e.g., immediate effect vs. gradually within a time frame). Second, outline the challenges that you or your team might face (e.g., new features might require you to get acquainted with a new technology). And third, the overall impact of embracing the change (e.g., how the work will be streamlined). Almost all the steps are subjective to your organization’s strength and nature of business. However, identifying the challenges can be treated as a generic aspect. Move on to the next section to familiarize yourself with the challenges. The Challenges:
MorphX and X++ to Visual Studio and Built-In Languages: Both MorphX and Visual Studio (VS) are integrated development environment (IDE). Similarly, X++ is the programming language for MorphX and Visual Studio has many built-in languages like C, C++, etc. Visual Studio is not a new offering and therefore a lot of developers are already adept at using it. But, if your team is not familiar with it, then you will need workshops or training because Visual Studio is a little complicated initially. The benefit of Visual Studio is its existing popularity which makes it easy to find related professionals. On-Premise to Cloud-Based Solution: Dynamics AX is an on-premise enterprise resource planning solution (ERP) whereas Dynamics 365 is a cloud-based and onpremise ERP and customer relationship management (CRM) solution. There are many exclusive features for Dynamics 365 online users and therefore many companies who are transitioning from Dynamics AX to 365 choose the online version. As an organization, you will have to outgrow the fear of putting information on cloud before opting for the online version. It is believed that in the coming time, cloud-based version will be the only offering of Dynamics 365 and Microsoft will slowly stop the on-premise version. The Back-End Framework: This includes quite a few things. Dynamics AX worked with layers but Dynamics 365 uses deployment packages. In Dynamics AX, making changes to ISV code was a tedious task whereas in Dynamics 365, a developer can make use of extension and only modify a part or whole sys if required. Additionally, Dynamics 365 also varies on the functioning of calling APIs and it would require sometime to getting used to. Another not so major change is setting up a form pattern in Dynamics 365, although this does not differ a lot from the Dynamics AX, you will get compile errors if you want to proceed without specifying the form pattern in Dynamics 365. The Implementation: Based on the above challenges, you would already know what you need to be prepared for while signing up for Dynamics 365 development. As an organization, you would have professionals who can take care of the migration. Here are just a few tips and tricks to help you facilitate change. 

Give a Heads Up to Your Team: Most of the time the decisions are made by top management and the people who are actually involved in the process are not informed about crucial decisions that will impact their daily work till the time the implementation phase arrives. It is a good practice to share the plans with your team and keep them updated on the progress. Identify the Training Needs: When you inform your team about the change, a good idea is to involve them by taking up initiatives. Assign a team member who can interview teammates to identify the training gaps, another team

member can work on how to fill those gaps. These initiatives will involve your team and lessen your workload. Blend Learning and Working: As an enterprise, you need to keep working. You can practically not afford to organize a month of training without work. An idea that can work well in this case is to design the training in a way where team members can practice their learning while working on actual projects. This would not hamper the day to day learning.
The challenges and tips should help you migrate easily from Dynamics AX to Dynamics 365 and enjoy all the perks that technology gives. Share your experiences and knowledge with the world by commenting below. This Article is originally Posted on:https://onmogul.com/stories/read-before-you-migrate-from-microsoft-dynamics-axto-dynamics-365