Migrate Microsoft Dynamics 365 (online) to Microsoft Dynamics 365 (on-premises)

Dynamics CRM 2016
 

Updated: November 28, 2016

Applies To: Dynamics 365 (online), Dynamics CRM Online

This document describes the steps needed to migrate from an instance of Microsoft Dynamics 365 (online) to a Microsoft Dynamics 365 on-premises deployment. To complete the migration, follow the steps provided here in the order presented.

System_CAPS_importantImportant

This document assumes that you already have a deployment of Microsoft Dynamics 365 on-premises. For information about how to deploy Microsoft Dynamics 365, see Microsoft Dynamics CRM Server installation.

To migrate from Microsoft Dynamics CRM Online 2016 Update to Dynamics 365 (on-premises), you must have Microsoft Dynamics CRM 2015 or a later version.

Before you migrate from Microsoft Dynamics CRM Online 2016 Update to Microsoft Dynamics 365 on-premises, be aware of the following behaviors or issues. These characteristics will appear after you import a Microsoft Dynamics CRM Online 2016 Update organization into a Microsoft Dynamics 365 on-premises deployment.

All managed solutions that have a dependency on a feature introduced in Microsoft Dynamics CRM Online 2016 Update will be removed from the organization that is prepared for migration. For example, this applies if the solution includes one or more of the following features:

  • A rollup field that uses the AVG operator or aggregates data across all activities related to a record.

  • A calculated field that computes the difference between two dates by using DIFFINDAYS, DIFFINHOURS, DIFFINMINUTES, DIFFINMONTHS, DIFFINWEEKS, or DIFFINYEARS.

Additionally, you can’t export record creation or update rules from Microsoft Dynamics CRM Online 2016 Update to Microsoft Dynamics 365 on-premises. More information: Help & Training: Set up rules to automatically create or update records in Dynamics 365

Any field in an unmanaged solution that includes a feature introduced in Microsoft Dynamics CRM Online 2016 Update will be removed from the organization. For example, this applies if the field includes one of the following features:

  • A rollup field that uses the AVG operator or aggregates data across all activities related to a record.

  • A calculated field that computes the difference between two dates by using DIFFINDAYS, DIFFINHOURS, DIFFINMINUTES, DIFFINMONTHS, DIFFINWEEKS, or DIFFINYEARS.

Additionally, these behaviors appear:

  • You can’t export record creation or update rules from Microsoft Dynamics CRM Online 2016 Update to Microsoft Dynamics 365 on-premises. More information: Help & Training: Set up rules to automatically create or update records in Dynamics 365

  • Records with date and time fields having values earlier than January 1, 1900 are considered invalid and will return an error message, such as “Invalid Date/Time The date/time format is not valid, or the value is outside the supported range.” When this issue occurs you can’t open forms, view lists, or process workflows from an entity record that has a date and time value that’s before January 1, 1900.

During the import of the Microsoft Dynamics 365 (online) database into your Dynamics 365 (on-premises) deployment, you must provide the organization database encryption key used for your instance of Microsoft Dynamics 365 (online).

  1. Sign in to the instance of Microsoft Dynamics 365 (online) that you want to migrate as a user with the system administrator security role.

  2. Go to Settings > Data Management.

  3. Choose Data Encryption.

  4. In the Data Encryption dialog box, select Show Encryption Key, in the Current encryption key box select the encryption key, and copy it to the clipboard.

  5. Paste the encryption key in to a text editor, such as Notepad.

    System_CAPS_warningWarning

    By default, Microsoft Dynamics 365 generates a passphrase that is a random collection of Unicode characters. Therefore, you must save the system-generated passphrase by using an application and file that supports Unicode characters. Some text editors, such as Notepad use ANSI coding by default. Before you save the passphrase using Notepad, select Save As, and then in the Encoding list, select Unicode.

  6. As a best practice, save the file that contains the encryption key on a computer in a secure location on an encrypted hard drive.

To request a backup of your Microsoft Dynamics 365 (online) database contact Microsoft Customer Support Services for Microsoft Dynamics 365 (online). For contact information, see Contact Technical Support.

The backup of your Microsoft Dynamics 365 (online) database must be restored by using a server running the same or a later version of Microsoft SQL Server as the database you receive.  You will be able to request the version you need before you receive the database.

Restore the copy of the Microsoft Dynamics 365 (online) database to a computer running SQL Server in the target Dynamics 365 (on-premises) deployment. To do this, follow the steps here.

System_CAPS_importantImportant

Your Microsoft Dynamics 365 (online) database may be encrypted with a certificate. For more information, see “Cannot find server certificate with thumbprint” error message when you try to restore a Dynamics 365 organization database later in this topic.

Restore a Microsoft Dynamics 365 (online) organization database to SQL Server

  1. Open Microsoft SQL Server Management Studio, and then connect to the appropriate instance of SQL Server.

  2. In Object Explorer, right-click Databases, and then click Restore Database.

  3. Type the name of a new database in the To database open text box. The database name must include _MSCRM in the name. For example the database name is Contoso_MSCRM.

  4. On the General page, in the Source section, click Device.

  5. Click the browse button in the Device option. This opens the Select backup devices window.

  6. In the Select backup devices window, click Add to open the Locate Backup File window.

  7. Select the file you want to use for the restore operation, and then click OK.

  8. Click OK to close the Select backup device window.

  9. Mark the checkbox in the Restore column next to the backup set option.

  10. Click OK to begin the restore process.

You must apply the latest Dynamics 365 (on-premises) updates before you import the Dynamics 365 (online) database. More information: Microsoft Dynamics CRM 2016 Updates and Hotfixes

How long it takes to complete the import of the organization database depends on several factors. These factors include the size of the database you are importing, the number of users, and the hardware you use to complete the import.

System_CAPS_noteNote

The procedure described here uses Microsoft Dynamics 365 Deployment Manager. Deployment Manager is an MMC snap-in that is included with Microsoft Dynamics 365 Server. Alternatively, your can run Windows PowerShell commands to complete the import. More information: Import-CrmOrganization

To import an organization, you must have the Deployment AdministratorMicrosoft Dynamics 365 role.

Import an organization database using Deployment Manager

  1. On the Microsoft Windows Server running the Microsoft Dynamics 365 ServerDeployment Tools server role, start Deployment Manager (DMSnapin.msc).

  2. Start the Import Organization Wizard. Right-click Organizations, and then click Import Organization.

    System_CAPS_noteNote

    You will receive a message if you attempt to import into a Dynamics 365 (on-premises) version that allows only one organization per deployment. The message notifies you that proceeding will deactivate, but not delete, the existing organization.

  3. Select the SQL Server and database. In the Select SQL Server window, select the Microsoft SQL Server where the organization database is restored in the SQL Server list, and then select the organization database in the Organization database list. Click Next.

  4. Specify the organization name. Enter the display name and name for the organization in the Specify the Organization Settings window. The Display name will appear in Microsoft Dynamics 365 applications. The Unique Database name will be used as the database name in SQL Server and will also be used to construct the URL for client applications. Notice that the values you enter don’t need to match the names that you used with Microsoft Dynamics 365 (online). Click Next.

  5. Specify the Microsoft SQL Server Reporting Services server. In the Specify Reporting Services Server window, type the Reporting Services server URL for the organization in the Report Server URL field. Click Next.

  6. Select the method for mapping users. Map users from the Microsoft Dynamics 365 (online) deployment to the Dynamics 365 (on-premises) deployment. Users must already exist in Active Directory for the Dynamics 365 (on-premises) deployment. The Import Organization Wizard does not create the users automatically. To complete the mappings, the user running the import operation must be mapped to a user in Microsoft Dynamics 365. For more information about how to map users, see Import an organization.

  7. In the System Checks window you receive the results of several environment diagnostic checks. If you receive a red alert, the issue must be resolved prior to completing the wizard. If you receive a yellow warning, you may proceed with the import. Click Next.

    Due to versioning differences between Microsoft Dynamics 365 (online) and Dynamics 365 (on-premises), you may receive a warning. This warning is expected and in most cases shouldn’t prevent the import from completing. After you successfully complete the steps in this document, the versioning will be correct.

  8. Begin the import. In the Ready to Import window, verify that the information is correct, and then click Import.

  9. Complete the import. After the import is complete, the Import Organization window appears. Click View the log file to view the log file that is created during the import. If the import is successful, click Finish.

    The import log is stored in the C:\Documents and Settings\\Application Data\Microsoft\MSCRM\Logs folder.

  10. Activate encryption

    1. As a user with System Administrator security role privileges, sign-in to the organization that was just imported, then go to Settings > Data Management.

    2. Choose Data Encryption.

    3. In the Activate Encryption Key box enter the encryption key that you copied earlier, and then select Activate.

    4. Select OK in the confirmation message and then choose Close to exit the Data Encryption page.

    5. We recommend that you copy the key to a safe place.

When you try to restore a Microsoft Dynamics 365 organization database, you may receive the following error message.

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Additional Information: Cannot find server certificate with thumbprint.

This error message occurs because the database that is to be restored is using Transparent Data Encryption (TDE). A certificate must be present to restore the database.

To resolve this issue, follow these steps.

  1. Obtain the certificate. Microsoft Dynamics 365 (online) customers receive the certificate as part of the power of choice backup of your database. Additional instructions may also be included.

  2. Execute the following SQL statements in the order specified to import the certificate where:

    • CustomerGeneratedStrongPassword is the password you want to use to create the master key.

    • DomainName, GUID, .cer, .pvk, and Certificate secured password provided are values that are included in the information sent to you from Microsoft for importing the TDE certificate.

    use master
    GO
    
    /* Check if DMK (##MS_DatabaseMasterKey##) exists. */
    select * from sys.symmetric_keys
    GO
    
    /* If key does not exist, create database master key */
    CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<CustomerGenerated-StrongPassword>'
    GO
    
    /* Verify that the database master key is created */
    select * from sys.symmetric_keys
    GO
    
    /* Import the certificate provided for TDE Database backup. TDE certificate name will also be provided in email */ 
    CREATE CERTIFICATE LTOP_<DomainName>_<GUID> FROM FILE = 'D:\<>_1.cer' WITH PRIVATE KEY (FILE = 'D:\<>_1.pvk', DECRYPTION BY PASSWORD = '<Certificate secured password provided>')
    
    
  3. Restore the organization database. To do this, see Restore the Microsoft Dynamics 365 (online) database.

System_CAPS_importantImportant

We strongly recommend that you store your TDE certificate in a secure location. If the certificate is lost and the database is encrypted, you will lose your data. For more information about TDE encryption, see TechNet: Move a TDE Protected Database to Another SQL Server.

© 2016 Microsoft Corporation. All rights reserved. Copyright

Community Additions

ADD
Show: