locked
Migration from CRM 3.0 to CRM 2011 RRS feed

  • Question

  • Hi,

    I am using CRM 2011 for most of my projects. But few projects are still in CRM 3.0. I want to move them to CRM 2011.

    In 3.0, I have 21 custom entities, customised workflows, callouts, javascripts, custom .NET pages.

    I want to move all the above to CRM 2011.

    1.How should I do it?

    2.How long will it take?

    3.What percent of data can I move?

    4.Is it better to move the project from 3.0 to 2011 'or' should I develop the entire project in CRM 2011(as a new project from the scratch) ? Which is easier ?

    5.What tools should I download?

    Please help me on this.

    Thanks.

    Thursday, April 5, 2012 3:45 AM

Answers

  • All your data can be upgraded. To upgrade from 3.0 to 2011 you must upgrade to 4.0 first.

    Any customizations that you did in 3.0 that are supported will upgrade. However, you may want to consider re-doing the workflows, callouts, javascripts and custom .net pages from scratch to save wasting time on troubleshooting upgrade issues and take advantage of new features and ways of doing things in 2011.  But the data and custom entities will be fine for an upgrade.

    You need to run the 4.0 server install on your 3.0 server to upgrade the 3.0 database to 4.0. Then you can copy the 4.0 SQL database to the SQL server that is running your 2011 organizations. Then import the 4.0 organization into CRM 2011 using the deployment manager. You do not need to upgrade the 4.0 server to 2011 to get the database upgraded because the 2011 Deployment Manager will upgrade a 4.0 database.

    For the CRM 4.0 install you can use the 90-day trial key available from www.microsoft.com/downloads

    Thursday, April 5, 2012 8:25 AM
    Moderator

All replies

  • Thursday, April 5, 2012 4:56 AM
    Answerer
  • All your data can be upgraded. To upgrade from 3.0 to 2011 you must upgrade to 4.0 first.

    Any customizations that you did in 3.0 that are supported will upgrade. However, you may want to consider re-doing the workflows, callouts, javascripts and custom .net pages from scratch to save wasting time on troubleshooting upgrade issues and take advantage of new features and ways of doing things in 2011.  But the data and custom entities will be fine for an upgrade.

    You need to run the 4.0 server install on your 3.0 server to upgrade the 3.0 database to 4.0. Then you can copy the 4.0 SQL database to the SQL server that is running your 2011 organizations. Then import the 4.0 organization into CRM 2011 using the deployment manager. You do not need to upgrade the 4.0 server to 2011 to get the database upgraded because the 2011 Deployment Manager will upgrade a 4.0 database.

    For the CRM 4.0 install you can use the 90-day trial key available from www.microsoft.com/downloads

    Thursday, April 5, 2012 8:25 AM
    Moderator
  • Hi Feridun,

    The project is already in CRM 4.0 running on Windows Server 2003 and SQL Server 2005. Now I want to move it to CRM 2011 running on different machine.

    We use virtual machine Hyper-V.

    I have a seperate Virtual Hard Disk with CRM 2011 and SQL server 2008 installed on Windows server 2008 R2.

    You have mentioned that I should copy the 4.0 SQL database to the SQL server that is running your 2011 organizations. Then import the 4.0 organization into CRM 2011 using the deployment manager.

    Is it possible to copy database from different Virtual Hard disk? If so, how?

    Is it possible to import organization from different Virtual Hard Disk? If so, how?

    If the Workflows,javascripts, plug-ins are working fine in CRM 4.0, how do it use the same in CRM 2011 ? 

    Please help me on this.

    Thank You.

    Tuesday, April 10, 2012 4:04 AM
  • CRM 2011 is on the Exchange 2007 box (Server 2008 64 bit) and SSRS is on the SQL 2008 and Report server box along with the Email Router (Server 2008 64 bit). Report services is configured and available via http and Rollup 6 is installed on both the CRM Server and the SSRS and Email Router server. The database is created in SQL during the install but deployment manager shows the organization as failed and trying to look at the orgainzation's properties blows up the MMC.
    turnpin
    Tuesday, April 10, 2012 9:26 AM