Upgrading from Microsoft Dynamics CRM 4.0

The only supported upgrade path to Microsoft Dynamics CRM 2011 is from Microsoft Dynamics CRM 4.0. This section provides guidelines for preparing for an upgrade to Microsoft Dynamics CRM 2011. Performing these tasks in advance can help minimize system downtime and ensure a successful upgrade. Also, this section describes how Microsoft Dynamics CRM 2011 upgrades your current system and what happens to items such as existing reports, customizations, and solutions.

Microsoft Dynamics CRM 4.0 server roles are not compatible with a Microsoft Dynamics CRM 2011 deployment. Therefore, after you upgrade the first Microsoft Dynamics CRM 4.0 server, other Microsoft Dynamics CRM 4.0 servers that are running in the deployment will become disabled. As each server is upgraded, the corresponding server will be enabled.

You can upgrade Microsoft Dynamics CRM 4.0 server roles in any order. However, to have a fully functioning Microsoft Dynamics CRM deployment, all servers and server roles must be upgraded.

In This Topic

Upgrade options

There are three different upgrade options:

  • Migrate by using a new instance of SQL Server. We recommend this option for upgrading from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011. Although this option requires a different computer for Microsoft Dynamics CRM Server 2011 and a different instance of SQL Server, it provides the least amount of potential downtime for Microsoft Dynamics CRM users since the Microsoft Dynamics CRM 4.0 deployment can remain functioning until the upgrade is completed and verified.

  • Migrate by using the same instance of SQL Server. This option requires a different computer for Microsoft Dynamics CRM Server 2011, but will upgrade in-place the configuration and default organization databases using the same instance of SQL Server. If issues occur during the upgrade, you must roll back to Microsoft Dynamics CRM 4.0 to avoid significant downtime.

  • In-place upgrade. Although this option does not require a different computer for Microsoft Dynamics CRM Server 2011 or a different instance of SQL Server, it poses the greatest risk if upgrade issues occur because a roll back and reinstall of Microsoft Dynamics CRM will be required to avoid potential downtime.

For detailed procedures for each of these options, see the Upgrade from Microsoft Dynamics CRM 4.0 topics in the Installing Guide.

For the latest product information, see the Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online Readme.

ImportantImportant
Always run a full backup of the Microsoft Dynamics CRM databases before you upgrade to a new version of the product. For information about database backups, see Backing Up the Microsoft Dynamics CRM System in the Operating and Maintaining Guide.

During an in-place upgrade only the default Microsoft Dynamics CRM 4.0 organization is upgraded. If the Microsoft Dynamics CRM 4.0 deployment contains additional organizations, those organizations are disabled and are not upgraded. You must upgrade those organizations using Deployment Manager. For more information, see Deployment Manager Help.

For each organization that you upgrade, we recommend that the volume have free space that is at least three times the size of the organization database file (organizationName_MSCRM.mdf) and four times the size of the log file (organizationName_MSCRM.ldf). For example, if a single organization database and log file are located on the same volume where the mdf file is 326 MB and the ldf file is 56 MB, the recommended available space should be at least 1.2 GB to allow for growth ((326 x 3) + (56 x 4)). Notice that the database files that expand during upgrade do not reduce in size after the upgrade is complete.

Microsoft Dynamics CRM software and components not supported for in-place upgrade

The following products and solutions are not supported by Microsoft Dynamics CRM 2011 and will not be upgraded during Microsoft Dynamics CRM Setup. If you upgrade a Microsoft Dynamics CRM 4.0 system that includes the product or solution listed below, or you install these components after you install Microsoft Dynamics CRM, these products or solutions may not function correctly. We recommend that you uninstall or manually remove the component before you upgrade.

  • Microsoft Dynamics CRM Connector for Microsoft SQL Server Reporting Services

  • Microsoft Dynamics CRM Connector for Microsoft Dynamics GP

  • Microsoft Dynamics BizTalk Adapter

  • List Web part for Microsoft Dynamics CRM 4.0

ImportantImportant
Microsoft Dynamics CRM 4.0 32-bit versions are not supported for in-place upgrade. Because Microsoft Dynamics CRM 2011 is available only in 64-bit versions, 32-bit versions must be migrated. For more information, see Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook in the Installing Guide. For instructions, see Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server in the Installing Guide.

Microsoft Dynamics CRM 3.0 is not supported for upgrade. However, you can upgrade Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0 by using a trial product key, and then upgrade to Microsoft Dynamics CRM 2011. For instructions about how to migrate from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 2011, see Migrate from Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 2011 Server in the Installing Guide.

Upgrade product key

Before the upgrade, obtain the product key that you will enter during the upgrade. In Microsoft Dynamics CRM 2011, the server and client keys are combined so that you enter only one key.

For more information, see Microsoft Dynamics CRM 2011 editions and licensing in this guide.

If you want to make system changes that require changes to your existing Microsoft Dynamics CRM licensing agreement, see How to buy Microsoft Dynamics.

User permissions and privileges

To perform a successful upgrade, the user who runs Microsoft Dynamics CRM Setup must:

  • Have an account in the same Active Directory domain as the server or servers that are being upgraded.

  • Be a member of both the Deployment Administrator Role and the Microsoft Dynamics CRM System Administrator Role.

  • Have administrator rights on the SQL Server and Reporting Services associated with the deployment that is being upgraded.

  • Have sufficient permissions to create new security groups in the Active Directory organizational unit that contains the existing Microsoft Dynamics CRM groups.

Multiple Microsoft Dynamics CRM Server 2011 versions in the same domain

Microsoft CRM 1.2, Microsoft Dynamics CRM 3.0, and Microsoft Dynamics CRM 4.0 can coexist in the same Active Directory domain. However, each version must be installed on a separate server. We recommend that you associate each version of Microsoft Dynamics CRM with a separate Active Directory organizational unit. This can prevent confusion if you have to add users or troubleshoot Active Directory issues.

Sharing a SQL Server

Only one Microsoft Dynamics CRM deployment per instance of SQL Server is supported. This is because each Microsoft Dynamics CRM deployment requires its own MSCRM_CONFIG database, and multiple instances of the MSCRM_CONFIG database cannot coexist on the same instance of SQL Server. If you have multiple SQL Server instances running on the same computer, you can host the databases for multiple Microsoft Dynamics CRM deployment on the same computer. However, this might decrease system performance.

Because Microsoft Dynamics CRM 3.0 does not have a database named MSCRM_CONFIG, you can configure the databases for this version of the product to coexist on the same SQL Server as Microsoft Dynamics CRM 2011 databases. However, to optimize performance we recommend that each version have its own computer that is running SQL Server.

Tips for a successful upgrade

The following issues, if applicable to your current Microsoft Dynamics CRM 4.0 deployment, should be resolved before you start the upgrade.

Maximum number of attributes exceeded

If you have more than 1023 attributes defined for an entity, you must delete the additional attributes before you run the upgrade. The upgrade will fail with the following message if you have more than 1023 attributes.

CREATE VIEW failed because column 'column_name' in view 'view_name' exceeds the maximum of 1024 columns.

Remove custom database objects

The Microsoft Dynamics CRM databases often change from one major release to the next because of database redesign. For example, the deletion service changed significantly from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011 and Microsoft SQL Server procedures or database objects that depend on the Microsoft Dynamics CRM 4.0 deletion service job will not work after the upgrade.

We suggest that, if you have added custom database objects such as triggers, statistics, stored procedures, and certain indexes, you remove those objects from the configuration and organization databases. In many cases, Microsoft Dynamics CRM Server Setup displays a warning when these objects are detected.

Remove the ignorechecks registry subkey

If you have manually added the ignorechecks registry subkey on the Microsoft Dynamics CRM Server 2011 remove it before you start the upgrade. For more information, see You cannot deploy Microsoft Dynamics CRM 4.0 by using an account that does not have local administrator permissions on Microsoft SQL Server.

Plug-in registration verification

Before upgrading from Microsoft Dynamics CRM 4.0, you must verify that the same plug-in assembly has not been registered multiple times with the same or different metadata fields (AssemblyName, MajorVersion#, MinorVersion#, PublicKeyToken, Culture).

You can use the Plug-in Registration Tool for Microsoft Dynamics CRM 2011 to verify plug-in assembly registration information. The Plug-in Registration tool is provided as a source code sample in the Tools folder of the Microsoft Dynamics CRM SDK download. Review the instructions provided in the Tools/PluginRegistration/Readme.docx file for more information about the tool and how to build it.

For more information about the Plug-in Registration Tool for Microsoft Dynamics CRM 2011, view the following Microsoft MSDN article:
Using the Plug-in Registration Tool for Microsoft Dynamics CRM 2011

You can also query PluginAssembly, PluginTypes in the organization database and perform Reflection on the PluginAssembly to determine plug-in assembly registration information. For more information about verifying plug-in registration, please contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the Microsoft Help and Support Contact webpage.

See Also

Send comments about this article to Microsoft.

© 2013 Microsoft Corporation. All rights reserved.

Community Additions

ADD
Show: