Step by step: Installing CRM 2011 On-premise and Migrating from Dynamics CRM 4.0 (32 bits, on-premise).


I have been experimenting a little bit installing Dynamics CRM 2011 and in particular, migrating from a CRM 4.0 32 bits deployment and decided to share it with here the community, specially to show you how simple is the overall process.

Obviously there are complete guides downloadable here by Microsoft but they are sometimes not the best reference when you want to have a rapid and visual overview of the process, specially, about the most typical / simple case. Meaning a case where you have an existing on-premise organization with data + entities customizations and workflows.

So, I focused here on copy and pasting screenshots of a migration like that, including some brief comments and in case you need more details, I suggest you refer to installation guide.

Let's start. First of all..

Installing CRM 2011

In this case, I run SQL Server, Reporting Services and Dynamics CRM 2011 Server on the same box.

So, the step by step process was:

1. Fulfill pre-requisites by installing SQL Server 2008 / 2008R2 64 bits with SSRS. In my case this was on top of a Windows Server 2008 R2 64-bits machine.

(I am assuming you already have an Active Directory domain and the server is member of it. Also, you are administrator on local machine, domain admin or have the corresponding privileges to create new security groups in AD)

2. Start Dynamics CRM Installation by double-clicking SetupServer.exe located in Server\amd64 folder.

3. Enter the product key. For beta, use the following product keys :

· Microsoft Dynamics CRM Workgroup (5 CAL limit): FF2JM-QX9PG-HXT8M-MMHXG-4MF32

· Microsoft Dynamics CRM Server (no CAL limit): 4FDTK-3HYV2-D9CCJ-4MF9Q-QJ32X
Although the application may display a 90-day trial period, these trial product keys will expire after 270 days.
Microsoft Dynamics CRM Professional edition is no longer available with Microsoft Dynamics CRM 2011.

More on this here.


· Accept license agreement:


5. Click on 'Install' to automatically install required components.



6. Choose the installation directory:


7. Choose the server roles. In a simple, typical installation you may leave this as default ('Full Server' option) which installs all the server roles on your Dynamics CRM Server.


8. Indicate the SQL Server where you want to install Dynamics CRM databases.

You can choose between a new deployment or to upgrade an existing deployment.

Remember upgrading could be done in place in case we are talking about a CRM 4.0 64 bits installation on top of SQL Server 2008 64 bits. As we are covering here the CRM 4.0 32-bits scenario, we are going to select 'Create new deployment' and after installation, we are going to import the existing CRM 4.0 32-bits organization.


9. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed into. Microsoft Dynamics CRM security groups are created in this organizational unit.


10. Specify the account to be used to run Dynamics CRM Services.

It's recommended that you use an account with low privileges, dedicated to run this services (it must a member of the Performance Log Users security group).

In this case, I just selected built-in Network service account.


11. Next step, if IIS is not installed, setup will install it as part of the installation and what we need to specify is the website where CRM Web Front-end will be installed.

As a best practice, you would like to create a new separate website for this case and that's in fact the option I chose.


12. If you plan to install e-mail Router component, enter here the name of the computer where you are going to install it. This computer will be used to route Microsoft Dynamics CRM e-mail messages. If you will not install the E-mail Router you can leave this box blank.

In this case, I just left it blank


13. Specify the organization settings (name, base currency)


14. In the Next step, you must choose the reporting services server URL.


15. On next step you just choose if you want to participate on the customer experience program or not.


16. Next step is a great news from CRM 2011 and lets you use Microsoft Update to automatically check for updates for your Dynamics CRM components.

Clearly, choosing this option is the recommended practice.


17. On next step the setup performs a system verification:

If everything is right, setup allows to continue. If not, you may need to troubleshoot identified issues first.


18. Going on with the installation, the next steps is just informative about the services that may have to be stopped or

restarted during the setup.


19. Ready to install! This step displays a summary of all the parameters entered for installation.


20. By clicking on 'Install' , setup will start copying and installing files:


21. When finished, you may see a window similar to the following one:


22. If the Reporting Server instance that you specified during this Setup points to the local computer where Microsoft Dynamics CRM is installed, Setup provides an option to invoke Microsoft Dynamics CRM Reporting Extensions Setup.

You must install the Microsoft Dynamics CRM Reporting Extensions to create, run, and schedule reports in Microsoft Dynamics CRM and it has to be installed on same machine SQL Server Reporting Services is installed.

In my case, as everything is on the same box, I checked on the option in order to install the extensions:


23. At this point we can see that Windows Update jump into scene in order to check if there is any update available before installing CRM Reporting Extensions.


If you choose 'Get updates for Microsoft Dynamics CRM (recommended)' and click on 'Next', setup will check for updates and in case there isn't any, the following dialog may appear:


24. By clicking on 'Next', Dynamics CRM Reporting Extensions files start to be copied:


25. Accept the agreement.

26. Specify the SQL server that stores the CRM Config database.

In this case, as it's everything on the same box, this points the same server.


27. Specify the SSRS instance. Probably you will just accept the default values.


28. Select the installation location


29. By clicking 'Next', the System Checks start. At the end you should a dialog similar to the following:


The warning in this case is because the CRM server and the SSRS Web site are installed on the same computer. Therefore, the CRMAppPool application pool and the ReportServer application pool are both running under the network service account.

In our environment, this is not a problem at all, so just go ahead.

30. Going on with the installation, the next steps is just informative about the services that may have to be stopped or

restarted during the setup.


31. Ready to install CRM Reporting Extensions!


32. When installation finishes, setup will display the following dialog:


At this point, we have CRM 2011 successfully installed!!.

You can try it and play a little bit if you want :) … Let's go on by..


Upgrading from Dynamics CRM 4.0 32 bits.

33. Get a full backup of your current Organization SQL Server database on Dynamics CRM 4.0.

34. Restore the DB backup on the new SQL Server instance used for Dynamics CRM 2011.


35. Open Deployment Manager console (Start->All Programs->Microsoft Dynamics CRM->Deployment Manager)


36. Within Deployment Manager, go to Organizations->Import Organization…


37. Select the SQL Server instance and the Organization database to import. This corresponds to the restored DB on the SQL Server 2008/2008R2 instance used for Dynamics CRM 2011.

If everything is on the same box as this case, you may already have the values automatically inferred.


38. Then, the Import Organization Wizard will ask for some parameters regarding to the organization itself, such as the display name we want to use.



39. After setting the above parameters we will be asked about users mappings, this is, how the users which are present on the organization to be imported are mapped to CRM accounts.

If you are migrating from a Dynamics CRM 4.0 deployment which is on the same domain (as it is this case), you would prefer just to allow CRM 2011 to automatically map the users and create the new users as needed.

For doing so, just click on the first option and press 'Next'.


40. The result of the auto-mapping:


41. If the domain user account you are running the application is not mapped with any user with the System Administrator security role, you will be prompted with the following message:


This means you will have to manually map one of the accounts to the current user you are logged on. Do this by just selecting the user and clicking on 'Browse...' to specify the current user account.

42. On next step, some system checks are carried out again:


43. The 'Ready to Import' dialog comes up!. Just click on 'Import' to start the migration!.


44. The import runs (it takes some time, depending on the amount of data and customizations)...


45. When the import process finishes successfully, it displays the following message:


46. If you want to set this imported organization as your default one, just get back to Deployment Manager->Organizations , refresh data (if you had the app open while importing) and then right click the imported organization and select 'Set as Default Organization'


If you are not going to use the default organization created during the CRM 2011 installation, I would suggest to delete it, also by right-clicking on the organization name.

47. Now , just enter the URL on Internet Explorer and verify your data and customizations!:


At this point, you already installed CRM 2011 and successfully migrated an existing CRM 4.0 32-bits organization.


I could see that all the data and customizations have been successfully migrated.

Nevertheless, if your scenario includes ISV customizations (i.e. new .aspxs, javascripts, plugins code) I guess you may need to make some adjustments in order to make it work successfully on CRM 2011.


  • Can I run a parellel environement for beta version of CRM 2011 along with CRM 4.0?

    What steps are involved for this?

  • Look, as stated on CRM 2011 implementation guide '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'

    However, I have heard about the following 'workaround' that may be useful for demo / test environments: first install CRM 4.0, then upgrade to CRM 2011, then install CRM 4.0 again and use a different SQL Server instance.

    Honestly I havent tried it but if you do, please tell us your experience.

    Hope it helps, thanks for visiting and asking,

  • Great Article... thanks.. it is really helpful for those who are looking forward to step in new CRM 2011... keep it up mate

  • Excellent blog Pablo, very relevant to people planning their CRM 4.0 upgrades.

  • This is great. Thank you.

    One quick question - I'm running into a problem when importing my CRM4 organization. When mapping users, it returns an error saying that another user is already mapped to the AD account. In the CRM 2011 beta forum, MSFT says it's because the install is on Windows Server 2008 R2.

    It states here that you did this using W2008R2 but you didn't get that error. Any thoughts? Or did you use W2008 (no R2)?


  • Hi,
    Nice article. I have a question. While migrating, will the date stamps( records modified by) remain the same as CRM 4.0? And also, while there be a creation new GUIDs while migrating? Any help would be appreciated.


  • Very good article. It helped me lot

  • @Dhivya Siva:

    I honestly didn't pay attention to that but sent this questions to other MVPs. These are the answers I got:

    While migrating, will the date stamps( records modified by) remain the same as CRM 4.0?

    Yes – they retain both the modified on and created on remain ok after upgrading.

    And also, while there be a creation new GUIDs while migrating? Any help would be appreciated.

    When we checked major entities such as accounts/contacts/leads they retained the same GUID as before.

    Hope it helps, thanks for asking.

  • Step 27 fails on my installation. I can 'browse' to my SSRS instance, but it does not show up in step 27 and I can't type into the field.

    Am wondering if this is because EVERYTHING is running on one server (that includes EVERYTHING, like Domain Controller, DHCP, DNS, SQL Server......) and it's not Small Business Server.....

    I'm intrigued why you would look for Updates for Dynamics CRM 2011 BETA that came out.....yesterday......

  • Thanks for your response pablop!

  • Is there an ER diagram for the database available anywhere? I have not installed it yet or I'd use SQL Server to generate the diagram.

  • Anthony,
    AFAIK there isnt any ER diagram. You can generate a diagram within SQL of course, but remember that you 'should not' write / add / edit any stuff in the DB.
    It's unsppported. Only querying the filtered views it provides to you (for reporting purposes i.e.)
    Hope this help,

  • I'll have to wait until install then. I dont have it installed.

  • Anthony,
    sorry for the question but why do you need a diagram of the DB? What for?
    If it really makes sense for you maybe I can generate one for you, np. It's that DB is supposed not to be touch at all, except just querying filtered views.
    Look fwd to your comments,

  • Hi Pablo,

    Thanks for your gr8 artice. I am also upgrading in a similar way but during import i am getting error of 'Violation of PRIMARY KEY constraint' in system check.

    Cannot insert duplicate key in object 'dbo.#CRMUserColumns' and also in 'dbo.#CRMDefaultValues'. Thanks!

  • Hi CRM user,
    You are migrating to RTM? RC?
    Any log info?
    If you can send to me enough info I can share it with other MVPs in order to help you out. I honestly haven't faced that error before.

  • Thanks Pablo,

    Please find the error log
    Error| Check SqlDefaultValueConstraintValidator : Failure: Violation of PRIMARY KEY constraint 'PK__#CRMDefa__59D492777599EE02'. Cannot insert duplicate key in object 'dbo.#CRMDefaultValues'.
    Error| Check SqlColumnValidator : Failure: Violation of PRIMARY KEY constraint 'PK__#CRMUser__59D492775DC26471'. Cannot insert duplicate key in object 'dbo.#CRMUserColumns'.


  • CRM User:
    You are migrating to RTM? RC?
    Could you please provide more context info about the environments?
    thanks in advance.

  • Thanks for the article it was very helpful. I am having one issue. After I successfully imported my CRM 4.0 Org I can see all of my previous data and all of the charts are working. When I click on the settings page I get a 404 error. Has anyone seen this or know how to fix it?

  • CRM_User
    I will go over this issue with other MVPs.
    BTW, how did you solve previous issue? I appreciate your comments on this so as to help other people who may experience same problem.

    thanks in advance.

  • CRM_User:

    Do you have any unsupported changes to the database like triggers or some other customization that will cause the upgrade to fail?

    I also suggest you post the question to the CRM forum, here:
    There are several collegues and friends of mine always willing to help there.

    Hope it helps.

  • do you know if windows 2003 and ms sql 2005 support MS 2011 ON -PREMISE? OR DO i NEED A LATER VERSION?

  • Hi pearse,
    You DO need Windows 2008/2008 R2 and SQL 2008/2008R2 64 bits :).

  • Thanks for the article, it was really very helpful. Nevertheless I am having one issue.
    After I imported my CRM 4.0 Org I cannot access it because it is in PENDING state, and the update appear NOT AVAILABLE.

    Has anyone seen this or know how to fix it?

    Thanks so much

  • Hi

    I have the same issue as CRM_User.
    I did not changed the database but there are many customizations.

    see log :

    128: UnresolvedAddress
    17:11:22|Verbose| DatabaseAction execution time; Bin\Microsoft.Crm.DataUpgrade.dll:RunV4DeletionService; 00:00:04.1533203
    17:11:22| Info| Clean up extension tables
    17:11:22| Info| CrmAction execution time; UpgradeDatabaseAction; 00:00:11.6064453
    17:11:22| Error| Installer Complete: OrganizationUpgrader - Error encountered
    17:11:22| Error| Exception occured during Microsoft.Crm.Tools.Admin.OrganizationUpgrader: Action Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction failed.
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.
    at System.Data.SqlClient.SqlBuffer.get_String()
    at Microsoft.Crm.DataUpgrade.CleanUpExtensionTables.RetrieveAndCleanUpTables()
    --- End of inner exception stack trace ---

  • Hi @DomJal,
    Do you have any unsupported change in the DB?
    BTW, have you took a look at this thread and this same error (but for tfs installation)?

    hope it helps,

  • Hi Pablop,

    Thks for your reply. I did not changed the database, but there is many custo on the CRM.
    I have a VM with CRM4.0, having my customized organization and a default organization.
    I have a new VM with CRM2011 working fine, on witch I try to import my customized organization.
    => On this new VM, "SELECT @@SERVERNAME" replies non null value ("WIN-A6T75\DEVCRM" for ex).
    => On this new VM, the default organization works fine
    => On this new VM, import customized organization ends with error

    I would try to import an organization having no custo, just to test.
    It goes further, but it ends with error.

    An error occurred when trying import and upgrade organization database System.Data.SqlClient.SqlException (0x80131904): The login already has an account under a different user name.

    MS says to try with SQL Srv2008 non R2 (

    Anyone know another way to make import work on Sql2k8R2?

  • Hi @DomJal,
    Seems to be a PITA :( ...

    According to the beta readme you need to run Dynamics CRM 2011 on Windows Server 2008 instead of Windows Server 2008 R2.

    It seems the issue is with the OS and not SQL.
    Anyway, it's a PITA.

    BTW, I also recommend you to post this issue to the forums, here:
    Maybe someone else faced this in the past and could drive to other better solution.

    Hope it helps,

  • Please i am trying to install CRM Server 2011 on a Windows Server 2008 which is a primary domain controller.

    The setup keeps crashing, please what can i do?

  • Hi @Tola Anjorin,
    Installing CRM on a DC is not supported. This may be the issue.
    It's only supported if the server is a Small Business Server which I guess it's not your case.

    My suggestion is that you move the installation to another box/VM and if this is not possible for you, think in a hosted or online setup.

    Tell me if you need any help, regards,

  • Hi,
    During installation of CRM 2011 i am getting an error:
    Action Microsoft.crm.setup.server.grantconfigdbdatabaseaccessaction failed.Windows NT user or group 'domain\sqlaccessgroup{1d27bdf3-5302-4b4c-9c00-6c7cc5e00f6b} not found.check the name again.

    Pls Guide me....

    Thanks in Advance,

  • Hi @Jeriesh
    Are you sure you are running this with a domain admin account?
    Have you tried installing this hotfix?

    Also, have you took a look at this thread?

    Hope this helps, please let me know your results,

  • Hi, I had CRM 2011 installed on multi servers enviroment. However, the offline feature for outlook 2003 32x never works for me. During going offline process, all records (17000 something) imported to local database, but at the Syncrozization step, it failed.

    Error: Invalid Argument

    Please help


  • Hi @h,
    BTW, have you applied latest rollup? I mean, RU 2 both on server and client. I know it resolves a lot of issues.
    If still does not work, I strongly suggest you post your question in the CRM forum so many other experts can help you ut.

    Hope it helps,

  • Hey Pablo,

    My company already upgraded to crm 2011 and we had on issue. When we make a new service ticket crm 2011 decides to make a whole new contact for that ticket even though the contact is already in the system. Any ideas how to prevent this? Thanks.

  • Hi Sara,
    Honestly haven't heard that before.
    Maybe you can put the question on the CRM Forum with more detailed info on the steps and customizations you may have.

  • (scuse for my english)
    I've a problem after import organization. My organization from CRM 4.0 appear well on Deployment manager but the statut is on failure, and the Version is still on "4.0"
    Have you an idea?

  • This a part log

    12:26:43| Info| Mise à jour xml des métadonnées : premier passage
    12:28:29| Info| CrmAction execution time; UpgradeDatabaseAction; 00:03:07.4133272
    12:28:29| Error| Installer Complete: OrganizationUpgrader - Error encountered
    12:28:29| Error| Exception occured during Microsoft.Crm.Tools.Admin.OrganizationUpgrader: Échec de l'action Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction.
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Violation de la contrainte PRIMARY KEY 'XPKLocalizedLabel'. Impossible d'insérer une clé en double dans l'objet 'MetadataSchema.LocalizedLabel'.
    L'instruction a été arrêtée.

    i've done a test with an empty data base from CRM4.0 (i've juste create a nex organisation), and i've the same log.
    I'don't understand why crm want to insert something int he table "MetadataSchema.Localized", cause this table is already empty before i started the upgrade.....

  • Great guide Pablo.

    However at step 11 when I run the installer I get an error message stating -
    "Setup was unable to retrieve settings from the IIS metabse"

    Do you know of any fixes?

  • Slt crm!
    Je viens d'installer crm mais j'ai reçu quelques problèmes au niveau de la sql serveur 2008 R2. Et je fais à nouveau d'installer le SQL.
    Mon problème est alors se base sur la déploiement de la crm2011, le MSCRM_SQL.CONFIG n'est pas trouvé.
    Est-ce pouvez me donner des aides!(Sil vous plaît)

  • Bonjour,
    J'ai connu quelques problèmes sur le déploiement de la crm 2011.
    Je viens de faire une reinstallation de la SQL server 2008 R2 car au cours de la déploiement j'ai reçu le message:"Impossible d'accéder à la base de données MSCRM_CONFING.SQL Server n'existe pas ou n'est pas accessible".
    Alors que dois-je faire pour résoudre cette problème?
    Merci d'avance pour votre conseil

  • This info is worth everyone's attention. How can I find out more?

  • Thank you Odum.
    You may want to take a look at the crm field guide. Http://

  • Thank you Odum.
    You may want to take a look at the crm field guide. Http://

Comments have been disabled for this content.