A client of ours is currently looking to upgrade CRM 4.0 to CRM 2013. I understand there is no direct upgrade path for CRM 4.0 to CRM 2013. We are yet to access the complexity of the CRM 4.0 implementation. My initial thought is to upgrade CRM 4.0 to CRM 2011 using the Upgrade Tool, and then upgrade CRM 2011 to CRM 2013 using the CRM Upgrade tool. Of course, this is easier said than done, and a lot depends on the complexity of CRM 4.0 that has been currently implemented.
Has anyone upgraded a CRM 4.0 system to a CRM 2013 system? If yes, what has been your approach? What are the aspects of upgrade that my team needs to be wary of? What about the potential timeframe to implement such an upgrade?
Any inputs are highly appreciated.
LinkedIn Profile | Rockstar 365 Profile | Blog
Please don't forget to consider the extra component upgrade as well! I have talked to many clients and whether they are upgrading from CRM 4 or CRM 2011 to the new CRM 2013, many are not aware that other components like Email Router, CRM for Outlook, Reporting Extensions etc also need to be upgraded. Added to that would be the question of whether current hardware/software meet the CRM 2013 requirements? The CRM 2013 Implementation Guide is your friend here. :)
Another more difficult aspect of an upgrade is the question of whether any existing business logic in CRM 4 can be rewritten using new CRM 2013 functionalities like business processes? Obviously it would require understanding of your client's business logics/rules and make a decision on whether to stick with old techniques (like async workflows or plugins) or to take the plunge and go for CRM 2013 options.
Hope that helps.
My suggestion is for you to set up a virtual environment and simulate the process:
Blog: QuantusDynamics Twitter: @QuantusDynamics
I would recommend you to:
- Update your CRM 4.0 Server with the latest upadte rollup i.e. Update Rollup 21
- Take a backup of your CRM 4.0 database and import it on a CRM 2011 environment first and test. Check if the customizations and scripts you need, function properly with UR 12 as well as UR 15 of CRM 2011
- Once all you customizations are tested on the latest UR of CRM 2011 take a backup of that organization database and import it on the CRM 2013 environment.
All the Best :)
Thanks Priscilla, Nuno and Sneha. You have provided some valuable comments and I'm currently making an inventory of them. :)
Will wait until the end of this week for people to comment, and then close this thread as verified.
We are planning to upgrade from CRM 4.0 to CRM 2013. We upgraded successfully to CRM 2011, but when trying to upgrade to CRM 2013 we get plugin errors.
We have a few custom created plugins such as "IntActionNow".
LegacyFeatureCheck gives following:
<Message>Assembly "IntActionNow" with version '220.127.116.11' references the CRM 4.0 SDK.</Message>
any chance you can report back on how it went? What kind of issues did you hit and how you resovled them?
We're still running CRM 4.0 here and I want to push us right up to 2013SP1 if I can, but want to know what I'm getting into. And yes, we have some minor customisations, but also a 3rd Party add-in, which we're hoping to migrate away from in the process...
I know this is an old thread but thought I would post and answer incase someone else needs the information. As of CRM 2013 the CRM 4.0 SDK is no longer supported. In this case it means that the plugins will need to be recompiled with the references changed from the CRM 4.0 SDK dll's to the CRM 2013 SDK dll's. Recompile and reload the new ones and the problem so be gone.
Hope this helps someone else.