Microsoft CRM Dynamics 2013

We are on Microsoft CRM Dynamics 2013 ( 6.0.3.106) on-premise version and looking to upgrade to the latest stable version. Is there a migration tool available that will help us upgrade?
sunny-jAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Feridun KadirPrincipal ConsultantCommented:
If you are staying on the same hardware, then you don't need to migrate, you can run the CRM 2015 install which will upgrade the server and CRM database. Then you can run the CRM 2016 install which will again upgrade the server and CRM database. But of course your server OS and SQL Server OS must be supported for CRM 2013, 2015 and 2016.

If you are moving to new hardware again you don't a migration tool. You would install CRM 2016 on a new server (will you use a new SQL server?). If you use a new SQL server , you would restore your CRM 2013 database to the new SQL server and you can run the upgrade in Deployment Manager.

If you provide more details on what you are planning to do with regard to hardware, I'd be happy to provide more specific suggestions.
sunny-jAuthor Commented:
Thank you for your response Feridun,

This is our current hardware and software.
Windows Server 2008 R2 Standard. Service Pack 1.
Processor. Intel(r) Xeon(r) CPU E5-2630 v3 @ 2.40GHz 2.40 GHz
Intalled memory 29.3 GB. 64-bit.

SQL Server 2008 R2. Current size of database. 907143.44 MB.
Link to SharePoint (MOSS) for document store.
On a Virtual Machine at present.

Given database, i am presuming we need to use an upgraded SQL Server.

We have a standard version of SQL server 2014 ready and can place on new hardware with windows server 2012. Again as a VM.

Although we have always upgraded this ourselves, we are feeling this might be more challenging so any guidance greatly received.
Feridun KadirPrincipal ConsultantCommented:
You can use SQL Server 2014 for CRM 2015  and CRM 2016

I would set up a new server with Window Server 2012 for Dynamics CRM/365 and another server with SQL Server 2014, join them all to the same domain as the current CRM 2013.

Then install Dynamics CRM 2015 on the new CRM server.  This will create a new organization, it doesn't matter what you call it, because you will remove it later.

Then backup your CRM 2013 database and restore it to SQL Server 2014. Is your database really 907G?

Then in the new server with CRM 2015, in deployment manager, select to import the restored database. Deployment Manager will see that it is a CRM2013 database and upgrade it. This might take several hours depending on the size of the database.

Then disable and delete the organization that was created during the installation.

The next step is to install CRM 2016 on the new CRM server, the setup will see that CRM 2015 is installed and run an upgrade. The upgraded CRM 2013 database will be upgraded to CRM 2016 - again this could take a while.

And you are done.

You should perform all of this as a test before the final migration to make sure there are no issues within the CRM 2013 databse such as unsupported customizations and to double-check how long the process will take.

Another thing to check is the editions of SQL Server. If the SQL 2008 is Standard edition then you shouldn't have problems and the new one can be Standard or Enterprise.  if SQL 2008 is Enterprise Edition and the new one is Standard Edition then you have some extra work to do on the database to allow backup and restore.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OWASP: Threats Fundamentals

Learn the top ten threats that are present in modern web-application development and how to protect your business from them.

sunny-jAuthor Commented:
Thank you so much for taking the time to explain the process below.


You can use SQL Server 2014 for CRM 2015  and CRM 2016

I would set up a new server with Window Server 2012 for Dynamics CRM/365 and another server with SQL Server 2014, join them all to the same domain as the current CRM 2013.

Then install Dynamics CRM 2015 on the new CRM server.  This will create a new organization, it doesn't matter what you call it, because you will remove it later.

Then backup your CRM 2013 database and restore it to SQL Server 2014. Is your database really 907G? 

Yes! It really is.


Then in the new server with CRM 2015, in deployment manager, select to import the restored database. Deployment Manager will see that it is a CRM2013 database and upgrade it. This might take several hours depending on the size of the database.

Can the process so far be completed within the same domain rather than on a test platform. The new server of course will not be in use and it will be much better to view it within the current domain than creating a special test platform.  Once complete, is it possible to see a version of the CRM with our data within and the email link turned off so the current version continues to work. In essence is it possible to have both the new and old version running on our systems, until we are ready to switch over.

Of course, if you say all of this should be built on a completely remote system, then that is what we will do.


Then disable and delete the organization that was created during the installation.

The next step is to install CRM 2016 on the new CRM server, the setup will see that CRM 2015 is installed and run an upgrade. The upgraded CRM 2013 database will be upgraded to CRM 2016 - again this could take a while.

And you are done.  

You should perform all of this as a test before the final migration to make sure there are no issues within the CRM 2013 databse such as unsupported customizations and to double-check how long the process will take.

Another thing to check is the editions of SQL Server. If the SQL 2008 is Standard edition then you shouldn't have problems and the new one can be Standard or Enterprise.  if SQL 2008 is Enterprise Edition and the new one is Standard Edition then you have some extra work to do on the database to allow backup and restore.  

We should be ok. We have the standard version installed.

Thank you once again. I will speak to the IT chap that normally helps with this and will come back if any further questions.
Feridun KadirPrincipal ConsultantCommented:
With regard to domains, yes you should add the new servers to the current domain. In fact, it would complicate things not to do so.
sunny-jAuthor Commented:
Thank you for your really helpful guidance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Dynamics

From novice to tech pro — start learning today.