Skip to main content

Top Six Mistakes in Dynamics CRM Upgrades

Every two years or so, Microsoft releases a new version of Dynamics CRM, packed with features and performance enhancements.  To take advantage of this technological progress, you have to upgrade your Dynamics CRM solution.



Here are the top six Dynamics CRM upgrade mistakes to avoid:

1. Stay one version behind.  Ten years ago customers would intentionally lag behind a version or two.  This approach is no longer viable, so if you upgrade be sure to bring your system to the current version.
2. Keep only one CRM environment.  Whether you are deploying your solution on premise or in Microsoft cloud, you need development and test environments as well as production environments.  Microsoft includes non-production environments for CRM Online if you have enough user subscriptions, or you may purchase them a la carte. 
3. Not using new features.  Each version comes with many additional features (usability, configuration, workflow and process management and developer extensions). Applying new features typically leads to a significant reduction in custom coding and making your system perform better and easier to manage. An upgrade is a prime opportunity to add new features and improve the user experience, so aim higher than reproducing what you already have.  
4. Skip versions. The upgrade path supported by Microsoft does not allow you to skip versions, so in most cases you should step through the versions until your system is current.
5. Skip reading the manual.  Microsoft provides thorough documentation on each upgrade, so be sure to study it.  Pay particular attention to the features from older versions which are no longer supported. 
6. Ignore testing and training.  Upgrades are an iterative process, so you have to test each time you attempt an upgrade before it is released to production. Microsoft fundamentally changed the user experience of Dynamics CRM in the 2013 upgrade, and users will benefit from learning the powerful new ways they can interact with the system with fewer clicks and pop-ups.  Without training, they may reject a system just because it is new.  Besides, how may end users really have sufficient training?

InfoStrat can help you successfully complete your upgrade. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

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

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