This blog is a continuation of my last blog Dynamics CRM Upgrade from On-premise to Online (Part 1). In Part 1, we discussed the steps for Dynamics CRM upgrade. There are a lot of other areas or surprises which need to be looked into during upgrade like:
- Export Security Roles from Child Business Units: In some scenarios where organizations do not have proper Dynamics CRM administrator, you will end up finding a lot of issues. One such example is Security roles created under child business units. Security roles created specifically under a child BU cannot be added to a solution, hence migrating the same becomes a challenge. But if the upgrade is from Dynamics CRM On-premise to Online, this situation can be managed. My blog entry CRM Upgrade – Export Security Roles from Child Business Units explains how to manage this situation.
- Migrating Reports: Reports created from report wizard mostly do not cause any problems, but there can be issues with reports created using SQL as these are not supported in Dynamics CRM Online. These reports need to be re-written using Fetch XML. Following free online tool can help in converting SQL statements to fetch XML: SQL2FetchXML.
Apart from SQL-based reports, one more factor can be a problem if your customer’s users have created a lot of individual reports and want migration of these individual reports as well. There is no direct way of adding “Individual” reports to a CRM solution, but there is a workaround which can be done, however, this requires some effort. The way you can achieve this is to edit each report one by one and convert them to “Organization” reports. By doing this, you will be able to add them to the solution, hence you’ll be able to export and import them. Once imported, these reports and can be re-edited back to individual reports.
- Issues with data import: Data import is a quick way of importing data to Dynamics CRM and can also be used as a daily integration tool. It is quite easy for business users to use data import, but if your customer is using data template in XML format from Dynamics CRM 4.0 or CRM 2011 to create an import file, then you might be in trouble. The notion of these files is that when you are importing an XML file and it has the record GUID, Dynamics CRM uses it to update the record. But with CRM 2015 Update came the Excel import functionality, hence update of a record doesn’t work with older data template-based XML data imports. You can read more about it in the article 2015 Update 1: Export to Excel Redesigned.
If your customer is using these features, then you may want to look at how that process should work after the upgrade.
- Issues with the upstream/downstream system: Since the Dynamics CRM SDK is changing continuously, there is a need to really look into integrations. Any system using 2007 CRM endpoint should be upgraded to work with CRM Online. Also, there has been a lot of performance improvement, and a lot of SDK changes have been made to support that, like optimistic concurrency. There are endless changes beyond the scope of this blog post, but the idea is that it makes real sense to re-look at the integrations points.
I hope this will help those doing Dynamics CRM upgrade from CRM On-premise to CRM Online. In my next blog post, we will see some of the other issues or blockers with data migration and how to resolve them.