Microsoft has been busy migrating its thousands of Microsoft Dynamics CRM Online customers to the new 2013 version. How is it going so far? Jason Gumpert, editor at MSDynamicsWorld.com, reports this month that so far, the process appears to be relatively smooth and free of major problems.
Microsoft Dynamics CRM consultant David Kohar is quoted as seeing “very little drama,” with only minor issues to deal with after the migration. Jukka Niiranen, another Microsoft Dynamics CRM consultant and a Microsoft MVP, says, “Apart from a few minor configurations that needed manual adjustments, no issues appeared.”
Of course, by this point, the first organizations migrated have been those with simpler, lower-risk systems. Those with more customizations, and more complex customizations, such as custom reporting, will be migrated last. Some of them are pushing back their upgrade dates to develop and test their upgrade processes.
Microsoft has a number of tools for identifying potentially problematic items in an upgrade:
- Legacy Feature Check tool.
- Custom code validation tool to check for unsupported client-side code.
- Environmental diagnostic wizard (EDW) that determines if it is safe to upgrade for an organization. It can detect unsupported code or API usage.
According to Microsoft, if your Microsoft Dynamics CRM 2011 customization was built according to their established rules and recommendations, the upgrade will go smoothly, and your CRM will work like it did in CRM 2011, but with the fancier look of CRM 2013.