Upgrading CRM 4.0 to 2013 RRS feed

  • Question

  • Hi all,
    We are currently in the process of upgrading CRM 4.0 to 2013
    I am aware that there is no direct upgrade from 4.0 to 2013.
    Currently we are working on all customisation fixes and re development of code in 2013. We have 2011 but we are NOT doing any development on it. So this our plan for the upgrade:
    1.      Backup CRM 4.0 database and restore it on the SQL server where it will hold the 2011 database
    2.      On the 2011 sever which has already been installed open Deployment Manager and import the CRM 4.0 database
    3.      Once the upgrade has been done install the latest Rollup for CRM 2011
    4.      Backup CRM 2011 database and restore it on the SQL server where it will hold the 2013 database
    5.      On the 2013 sever which has already been installed open Deployment Manager and import the CRM 2011 database
    6.      Apply all code fixes and customizations on the newly converted 2013 database
    As you can see we only have 2011 database as the intermediate step in the upgrade. We do not wish to do any development work in 2011 as this will increase or workload and we would rather do all changes in 2013 and test and compare it with 4.0 to see if all functionality works as expected.
    Is this a supported method of upgrade? I noticed that this is a different approached compared to this following article  http://community.dynamics.com/crm/f/117/t/114804.aspx
    which is what most consultants would advise?

    Monday, June 2, 2014 11:14 AM

All replies

  • From a CRM Admin point of view, this is ok but note my concern in #3 below.  This is also just off the top of my head.  Someone else may have additional input on something I may have missed.

    1.  You will likely have jscript that would not be supported in CRM 2013.  There were some changes made in CRM 2011 to give cross browser support.  This may cause errors when the pages load.  You may want to disable the jscript in the 4.0 environment prior to backing up the database.  Last thing you really want to see as soon as you log into CRM 2013 is errors when the forms load.

    2.  I also assume that plugins and sdk workflows are being redeveloped.  Make sure they or any other custom code is not attempting to use a deprecated rest point.

    3. Care should also be taken with the customizations if they are being recreated in a 2013 dev environment since you don't have the upgraded org at this point.  Schema names should match the original source and the column names are case sensitive.  If you make any typo's while recreating these (note that they are case sensitive also), you will get errors during the import of the solution, and you would then have to manually edit the xml.  It really is best to do development on an organization that is sourced directly from the upgraded original environment.

    Jason Peterson

    Monday, June 2, 2014 1:42 PM
  • Hi Jason,

    Thanks for the reply. For our DEV environment we actually have an organisation upgraded all the way from 4.0 to 2013 and we are developing straight off this organisation. So all schema names are the same as 4.0. So I guess it should be ok?

    Tuesday, June 3, 2014 1:47 AM
  • You should be good then.

    Jason Peterson

    Tuesday, June 3, 2014 1:15 PM