MS CRM 2011 to 2015 upgrade using a new SQL Server Instance
We recommend this option for upgrading from Microsoft Dynamics CRMCRM 2011(On-Premise) to Microsoft Dynamics CRM 2015.
Although this option requires a different servers for Microsoft Dynamics CRM
2015 Server and a different instance of SQL Server, it provides the least
amount of potential downtime for Microsoft Dynamics CRM users because the
Microsoft Dynamics CRM 2011(On-Premise) deployment can
remain functioning until the upgrade is completed and verified.
The following diagram illustrates the high-level overview of the process required to upgrade a Microsoft Dynamics CRM 2011 implementation to Microsoft Dynamics CRM 2015.
This process would be performed in the development environment and in principle in other environments (test, pre-production, and production), while in the latter you would likely combine with the change management process to deploy refactored customization and code.

1. Create a brand new CRM 2013 environment. Since the CRM 2013 deployment is only temporary, the CRM 2013 deployment can be created as a virtual machine. CRM 2013 trial product key can be used, as this is a temporary setup.
We recommend this option for upgrading from Microsoft Dynamics CRM
The following diagram illustrates the high-level overview of the process required to upgrade a Microsoft Dynamics CRM 2011 implementation to Microsoft Dynamics CRM 2015.
This process would be performed in the development environment and in principle in other environments (test, pre-production, and production), while in the latter you would likely combine with the change management process to deploy refactored customization and code.

1. Create a brand new CRM 2013 environment. Since the CRM 2013 deployment is only temporary, the CRM 2013 deployment can be created as a virtual machine. CRM 2013 trial product key can be used, as this is a temporary setup.
2. Create a brand new CRM
2015 Deployment.
3. Take the Microsoft
Dynamics CRM 2011 production deployment offline
4. Export the organization
database backup from the CRM 2011 environment.
5. Restore the database in
the CRM 2013 environment, using the sql server utility.
6. Import the organization
on the CRM 2013 using the deployment manager.
7. Verify the upgraded CRM
2013 organization.
8. Export the organization
database backup from the CRM 2013 environment.
9. Restore the database in
the CRM 2015 environment, using the sql server utility.
10. Import the organization
on the CRM 2015 using the deployment manager.
11. Verify the upgraded CRM
2015 organization.
12. Import the
solutions with refactored code.
13. Perform validation to
ensure the system is working as expected.
--
Happy CRM'img
Gopinath
--
Happy CRM'img
Gopinath