Microsoft Dynamics crm planning Guide

Upgrading from Microsoft Dynamics CRM 3.0

For the latest product information, see the Microsoft Dynamics CRM 4.0 Server Readme (http://go.microsoft.com/fwlink/?LinkID=78157).

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 Microsoft Dynamics CRM 4.0 Operating and Maintaining Guide.

Microsoft Dynamics CRM software and components not supported for upgrade

• 
  Microsoft Dynamics CRM 3.0 Mobile
  
• 
  Microsoft Dynamics CRM Connector for Microsoft Dynamics GP
  
• 
  Microsoft Dynamics CRM Accelerator for Siebel
  
• 
  Microsoft Dynamics BizTalk Adapter
  
• 
  Microsoft Dynamics CRM 3.0 Data Migration Pack and Microsoft Dynamics CRM 3.0 Data Migration Framework
  
• 
  Microsoft Dynamics CRM 3.0 List Web Part
  
• 
  Microsoft Dynamics CRM 3.0 Exchange E-mail Router
  

Upgrade license key

For more information, see "Microsoft Dynamics CRM editions and licensing" in this document.

Also, verify that the license key that you will enter is valid for use during an upgrade. For detailed information, see KB Article 947272: Microsoft Dynamics CRM 4.0 Deployment Manager Error: "The license code entered is not valid for upgrade" (http://go.microsoft.com/fwlink/?LinkId=141545).

If you will be making any system changes that require changes to your existing Microsoft Dynamics CRM 3.0 licensing agreement, see How to buy Microsoft Dynamics (http://go.microsoft.com/fwlink/?LinkId=111388).

User permissions and privileges

• 
  Have an account in the same Active Directory domain as the server or servers that are being upgraded.
  
• 
  Be a member of the Microsoft Dynamics CRM System Administrator security 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 Microsoft Dynamics CRM 3.0 groups.
  

If you use pre-created groups together with a configuration file, the user who runs the upgrade does not have to have permission to create security groups. For more information, see "Server XML Configuration File" in the Microsoft Dynamics CRM Installing Guide.

Multiple Microsoft Dynamics CRM Server versions in the same domain

After you upgrade your Microsoft Dynamics CRM deployment, the earlier version is no longer available.

Sharing a SQL Server

If you want to host multiple organizations in a single Microsoft Dynamics CRM 4.0 deployment, see Multi-Tenancy: Use a single hardware group for separate data and processes (http://go.microsoft.com/fwlink/?LinkId=146765).

Because Microsoft CRM 1.2 and Microsoft Dynamics CRM 3.0 do not have a database named MSCRM_Config, you can configure the databases for these versions of the product to coexist on the same SQL Server as Microsoft Dynamics CRM 4.0 databases. However, to optimize performance we recommend that each version have its own SQL Server.

For detailed information about the options available for upgrading multiple Microsoft Dynamics CRM Server deployments that share a SQL Server, see "Upgrade Multiple Deployments of Microsoft Dynamics CRM 3.0 That Share an Instance of SQL Server" in the Microsoft Dynamics CRM Installing Guide.

Additional downloads and information resources

• 
  Update Rollup. Download the latest Update Rollup (http://go.microsoft.com/fwlink/?LinkId=146266) package for Microsoft Dynamics CRM 4.0.
  
• 
  Diagnostics Tool. Download the CrmDiagTool4 from Microsoft Dynamics CRM Support Tools Information (http://go.microsoft.com/fwlink/?LinkID=140354) so that it is available if you encounter problems during the upgrade.
  
• 
  Internet Facing Deployment Configuration Tool. If you plan to configure an Internet-facing deployment (IFD) of Microsoft Dynamics CRM, you can download the Internet Facing Deployment Configuration Tool to use during the upgrade. For more information, see KB article 948779: How to use the Internet Facing Deployment Configuration Tool (http://support.microsoft.com/kb/948779).
  
• 
  KB Articles. Before you start the upgrade, review the following articles:
  

• 
  947061: How to resolve common problems that may occur when you upgrade from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0 (http://go.microsoft.com/fwlink/?LinkID=122246)
  
• 
  946590: Error message when you try to upgrade Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0: "Action Microsoft.Crm.Setup.Server.InstallDatbaseAction failed" (http://go.microsoft.com/fwlink/?LinkId=146662)
  
• 
  947997: Error message when you try to reinstall Microsoft Dynamics CRM 3.0 after you uninstall Microsoft Dynamics CRM 4.0: "Microsoft.Crm.Setup.Server.ConfigureServiceVirtualDirAction failed" (http://go.microsoft.com/fwlink/?LinkId=146663)
  
• 
  952105: How to revert to Microsoft Dynamics CRM 3.0 if you cannot upgrade to Microsoft Dynamics CRM 4.0 (http://go.microsoft.com/fwlink/?LinkId=146664)
  

Test upgrade

What happens to reports?

The following items should be considered before you run Setup to upgrade your existing Microsoft Dynamics CRM 3.0 system.

• 
  During the upgrade, all report definition files (.RDL) will be modified to work with the new Microsoft Dynamics CRM Connector for SQL Server Reporting Services.
  
• 
  Some Microsoft Dynamics CRM 3.0 reports will not work correctly after the upgrade. This includes reports that have the following conditions:
  

• 
  Modification to use expressions for linking.
  
• 
  Modification to use stored procedures.
  

• 
  The report entity now supports views. During Setup, the following two new views seem to differentiate the reports:
  

• 
  Microsoft Dynamics CRM 3.0 Reports: Existing Microsoft Dynamics CRM 3.0 reports.
  
• 
  Microsoft Dynamics CRM 4.0 Reports: New Microsoft Dynamics CRM 4.0 reports.
  

• 
  During Setup, all reports, in both view categories, are created that have organization ownership and then are available to every Microsoft Dynamics CRM user.
  
• 
  Administrators who want to make the Microsoft Dynamics CRM reports available in views and forms must modify the properties for each report. For more information about how to modify report properties, see the Microsoft Dynamics CRM Help.
  
• 
  Any snapshot reports that are created by using the Report Scheduling Wizard (available from the Microsoft Download Center) will have the following ownership after the upgrade:
  

• 
  Snapshot reports that were available to the whole organization will have organization ownership.
  
• 
  Snapshot reports that were owned by individual users will have user ownership.
  

What happens to customizations?

During the upgrade process, Setup deletes all customizations that are not published. Therefore, we recommend that you review each unpublished customization and publish the customizations that you want before you run Microsoft Dynamics CRM 4.0 Setup.

In rare cases, an existing custom view may be renamed during the customization upgrade if it conflicts with a new system defined view.

What happens to workflows?

• 
  Microsoft Dynamics CRM 4.0 workflows do not support a post-URL action. As described in the Microsoft Dynamics CRM 3.0 SDK, the post-URL action was deprecated with that release. Because post-URL actions are deprecated, any workflows or workflow instances in the Microsoft Dynamics CRM 3.0 system will not be upgraded during Microsoft Dynamics CRM 4.0 Setup. During Server Setup, workflows that cannot be upgraded are recorded in the Setup log.
  
• 
  In Microsoft Dynamics CRM 3.0, workflows were executed in a predetermined order based on entity and event type. In Microsoft Dynamics CRM 4.0, a single workflow job now supports multiple events (create, update, and delete), the following behavior that occurs after upgrade should be considered:
  

The sequential order when a workflow runs cannot be configured. Therefore, Microsoft Dynamics CRM 3.0 workflows that are upgraded will do so without following a predetermined order of execution. If the workflow requires a strict order, we recommend that you redefine the workflow after the upgrade is completed.

• 
  Sales process workflows are upgraded as follows:
  

• 
  Sales processes that are inactive are upgraded without change to the original behavior of the workflow.
  
• 
  Sales processes that are active and that subscribe to a manual event are upgraded without change to the original behavior of the workflow.
  
• 
  If multiple sales processes exist on an opportunity create event and the sales processes belong to a single owner, particular transformation logic will be used to upgrade the sales processes. Although the logic of the upgraded sales process is similar, the definition structure of the sales processes will seem to differ from the original. For example, consider a Microsoft Dynamics CRM 3.0 sales process definition that has the following order of execution.
  

1. 
   Sales process 1 (gating condition --> C1)
   
2. 
   Sales process 2 (gating condition --> C2)
   
3. 
   Sales process 3 (gating condition --> None)
   

1. 
   Sales process 0 (This is a new workflow definition automatically created as part of the upgrade process) with the following logic:
   
2. 
   If C1 is not true then call sub-process P1'
   
3. 
   ElseIf C2 then call sub-process P2'
   
4. 
   ElseIf Null then call sub-process P3'
   
5. 
   P1' --> Sales process 1 without C1
   
6. 
   P2' --> Sales process 2 without C2
   
7. 
   P3' --> Sales process 3
   

Sales processes that contain multiple active processes on an opportunity create event, and are owned by multiple users, will be deactivated during upgrade. Therefore, to run these sales processes after the upgrade is complete you must manually publish them. However, after the upgrade, these sales processes may not function as expected and may require redefinition.

In a multi-server configuration of Microsoft Dynamics CRM 3.0, it is possible to have unique workflow rules and workflow assemblies on each server. Similarly, each server may have active workflow instances. However, the upgrade process for Microsoft Dynamics CRM 4.0 only upgrades workflow rules, workflow assemblies, and workflow instances for one server.

To make sure that there are no active workflow instances on these additional servers during the upgrade process, shut down the additional servers before you start the upgrade to Microsoft Dynamics CRM 4.0. To make sure that any unique workflow rules or workflow assemblies are also upgraded, copy them from the additional servers to the primary server that will be upgraded.

What happens to Microsoft Dynamics CRM 3.0 Mobile?

----------------------- Send Feedback About This Chapter ----------------------

We appreciate hearing from you. To send your feedback, click the following link and type your comments in the message body.

Note

The subject-line information is used to route your feedback. If you remove or modify the subject line, we may be unable to process your feedback.