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

PowerApps 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 PowerApps Portal and shifted to the PowerApps 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. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …