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?
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?