In this blog, we highlight a lesson learned when we used a Dynamics 365 Customer Engagement online data source connector, called Instance Web API, for Power BI reports.
Have you been considering a CRM reimplementation or upgrade, but aren’t sure which option is the best for your organization? If so, this blog is for you! While you may think that an upgrade and a reimplementation are similar, they are actually completely different, and deciding which option is best can be challenging. This series includes the following installments:
So without further ado, let’s dive in. First things first. What is the difference between a reimplementation and an upgrade?
Reimplementation: If you decide to go with a reimplementation that means you’ll be starting with a fresh instance of a new CRM org. PowerObjects can assist you with your re-implementation process. For example, you may need to re-configure the following:
Lastly, you will need to complete a data migration to move the data from your old CRM system to your new CRM system. With data migrations it is important to consider the cleanliness and quality of your data.
Upgrade: With an upgrade, you take whatever you currently have in your CRM, and then you follow an upgrade path to go from one version to the next version of CRM. For example, if you’re upgrading from CRM version 2011 to 2015 you’ll need to upgrade to CRM 2013 before going to version 2015. When working with PowerObjects, we evaluate your existing customizations and configurations for capability with the latest version of CRM. A critical part of the upgrade process is testing all of your customizations, processes, and reports to ensure that they work correctly in the newer version of CRM. As part of the Microsoft CRM upgrade process, most of your configurations and workflows should upgrade without re-configuration.
Sometimes you may want to add enhancements to your CRM system along with your upgrade. Enhancements are great, however, we suggest a two-phased approach: focus on the upgrade first and then have a separate project afterwards for the enhancements. You want to make sure your system is settled and running smoothly before you add in new functionality. Think of it from a troubleshooting standpoint, working on the upgrade and enhancements unnecessarily complicates the project.
Choosing the Right Option for You
If you are using an older version of CRM, such as 4.0 or 2011, you might want to upgrade to the current 2015 version to take advantage of all the new features and benefits that come with it. However, you may be wondering if you are better off choosing a reimplementation so that you can start off fresh with a new instance and then migrate over your existing data. “How do I know which one to choose?” We get asked this question all the time. These are a few reasons why you may want to opt for a reimplementation:
Generally speaking, upgrades are less expensive, because when you opt for a reimplementation, you need to reevaluate all your processes and requirements, build out the system, and then migrate the data over.
Here are a few reasons for upgrading:
To summarize, consider a reimplementation if you want/need to start with a fresh instance in a new CRM org. An upgrade is typically better if you don’t have a need for imperative configuration changes and if you don’t have a major data quality issue. Feeling a little overwhelmed? PowerObjects offers free upgrade evaluations. Reach out to us with any questions or concerns so we can help you get on the right track. Also make sure you check out our webinar, “Upgrading CRM: Powerful New Features to Make Your Work Easier” to learn about all of the great new features that you can take advantage of just by upgrading your CRM system. Stay tuned next week for the next installment in our Upgrading CRM series.
Until then, happy CRM’ing!