Skip to main content

Dynamics 365 Upgrades: Migration, Refactoring and Rewriting



Microsoft, like other cloud software providers, ensures that you will be using the latest version of software such as Microsoft Office 365 and Dynamics 365.  Enhancements are continuously released and major upgrades take place more frequently than they did when most organizations ran their software on their own servers.

Many of InfoStrat's government clients are at last moving their Dynamics 365 (formerly Dynamics CRM) solutions to the Microsoft cloud.  Moving them offers many choices for customers about their approach.  Here are some alternatives:

Lift and shift. Some organizations want to move their workloads to the cloud and decommission their servers and on premises computing facilities.  The least ambitious approach is to move from on premises hardware or virtual servers to cloud servers.  If you are already running virtual servers, the move is less dramatic.  If not, this effort will allow you to re-architect your server infrastructure and consider cloud service such as SQL Server rather than a one to one mapping of physical to virtual servers. For Dynamics 365, the lift and shift approach would allow you to keep whatever version of Dynamics you are using, but you would forgo the benefits of the latest version and be responsible on your own for all upgrades and bug fixes.

Migration. The next approach would be to move from Dynamics 365 on premises to the cloud version on the Microsoft commercial or government cloud.  You would be required to upgrade to the latest version in order to make this move, but then future upgrades would be handled by Microsoft.  Depending on your current version, the minimalist approach would entail replacing any code that no longer works on the current version of Dynamics.

Refactoring.  The move to the cloud allows you to improve performance of your solution by refactoring any elements that are not performing up to your goals.  Refactoring means creating a new coding approach to fulfill the original requirements.  This means that you do not need to involve users in the efforts or create new requirements documents or user stories.

Rewriting. The most ambitious approach is to use the migration as an opportunity to rewrite a solution.  This may be beneficial if the solution has fallen out of synch with user requirements, and you have a long backlog of enhancements.  Rewriting will involve significant work from a full implementation team in order to nail down requirements, design, develop and test the solution.  In the long run this may be the best way to improve user satisfaction and get your solution both stable and fully adopted. 

Whichever approach you choose, you should be clear on the boundaries of the effort and how your cloud migration fits with your budget and schedule.  For instance, rewriting may take nearly as long as your original implementation, while refactoring may be much faster.




Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

5 Best Things about the Unified Interface for Microsoft Dynamics 365

The latest version of Microsoft Dynamics 365 moves most of the core functionality of sales and customer service to a new user interface - The Unified Interface client.  This user interface is not completely new as it was gradually introduced for the Hub features such as the Customer Service Hub in recent versions of the product. The new interface is quite different from the previous interface which was used from Dynamics CRM 2013 to 2018 with a few incremental changes.  This is the Unified Interface, using a form from InfoStrat's Grants Manager Plus Solution. Here is the same record shown in the previous interface which Microsoft calls Classic. Here are the top 5 features that I like best about the Unified Interface: Better menus and navigation . The sitemap on the left is more helpful than the classic menus for larger, more complex solution. Lefthand menu shortcuts are a great use of space and help users access the most popular areas.  Better subgrids .  Sub