This article outlines a process and the resources you need to prepare for a successful upgrade to Microsoft Dynamics 365.
Originally published in Q3 2017 D365UG/AXUG Magazine
Upgrading to Microsoft Dynamics 365, as with any upgrade, takes preparation and planning. Let’s break it down into four components: Documentation, Investigation, Regroup, and Testing. (See what I did there? DIRT.)
Documentation – Gather the Following
Microsoft Releases
There are cumulative documents, as well as version-specific documents and documents on specific features. Here are a few links to get you started:
- Microsoft Dynamics AX 2012 Cumulative Document
- Documents by Microsoft Dynamics AX 2012 version
- What’s new in Microsoft Dynamics 365
- Microsoft has also introduced a wiki help site
Business Process
This can be in the form of flow diagrams or narratives. It is important to document the steps, with particular notation to processes within Microsoft Dynamics AX.
Customizations
Create a list of all custom development from your implementation Partner, ISVs, and those done internally. You’ll want to keep these in mind when you review the Microsoft release documentation.
Investigation – Research, Compare, and Experiment
Review the Microsoft release documentation to see if there are any new features, changes, or bug fixes that might affect your business process flows. Create functional regression test scripts using your business process documentation, and include validation steps for all customizations and integrations.
Bring up a Dynamics 365 environment. Review standard functionality, particularly those areas where you have customized. You may find there are customizations that are no longer needed.
Regroup – Convene Your Project Team
If you can regroup your original implementation team, that can help with synergy. A fresh team can provide some new insights. Either way, the team should be made up of your company’s subject matter experts as well as those who use the application on a regular basis. Contact your ISVs and implementation Partners to get compatible Dynamics 365 models. If you are going to use any third party resources, start discussing availability so that you can begin to build a project timeline.
Testing – Plan for Unit Testing, Regression Testing, and
Upgrade Script Testing
When planning your project, you should include several different types of testing. There is an entire upgrade process that needs to occur that will likely include upgrades to various layers of the infrastructure (including database, AOS, BI, and report servers). This will need to be tested from a technical perspective. Once the technical team feels they have built the Dynamics 365 environment, the functional team needs to test.
Obviously you need to test anything that is changing – but what do you do when it feels like everything is changing?
Start with reviewing unit testing basic functions, customizations, and point-to-point integrations. Check with the technical team on what to test due to infrastructure changes. For example, if you are using remote desktop services, you should add to your testing regimen scenarios where Microsoft Dynamics AX reaches out to another application or service to complete an operation. Exporting to Microsoft Excel and printing are two simple examples. Your IT DBA will be your best resource to determine what should be added.
Then plan to use the functional regression test scripts built per your business processes, adding any specifics due to infrastructure changes. Plan to run through your functional regression test scripts after each of the technical upgrades is completed. Also plan for multiple correction cycles and retesting. There will be retesting after code updates as well as with technical upgrade script changes.
Develop your overall project plan, pull your project team together, and get started!