Skip to main content

5 Tips on Moving from Dynamics CRM On Premises to the Microsoft Dynamics 365 Cloud

Source: Microsoft Dynamics CRM (on-premises) to Microsoft Dynamics Online Migration Guide (microsoft.com)
Many customers are moving their Microsoft Dynamics CRM from traditional hosting on premises in their server facilities to the Microsoft Dynamics 365 cloud.  Migration to the cloud can be challenging, especially if you are still using an older version of Dynamics CRM.  You will not have the same control over the cloud environment that you have of your servers, and your data import performance may be throttled down by the cloud environment.  For instance, you cannot schedule restores from a Dynamics 365 backup on the cloud or make backup snapshots in the same way that you control these on your servers. 

Here are InfoStrat's top hints to make the transition easier for your organization.
  1. Upgrade to the latest version of Dynamics 365 on premises. Microsoft doesn't provide a smooth transition which allows you to skip versions, so you will need to upgrade to each of the successive versions or consider your new solution a clean break and migrate only the data.
  2. Switch your licensing to the subscription model and provision your cloud environments. The InfoStrat Dynamics 365 cost calculator can help you choose the plan that is right for you.  Microsoft allows you to run on premises with your cloud subscription, so there is no incentive to wait and no need to buy duplicate licenses/subscriptions for your users. You may be eligible for Team Member subscriptions for many of your users.  Create the production and non-production instances of Dynamics 365 so you can practice the process of promoting your solution from one environment to the next before you go live. Also be sure to check the storage requirements and perhaps archive data if appropriate rather than pay for additional storage of data you are not using. 
  3. Freeze development of your solution until the migration is complete.  Once you are upgraded to the latest version of Dynamics 365, focus on moving to the new environment rather than entertaining more changes to the solution.  Otherwise you may find yourself chasing a moving goal line.  
  4. Consider a data migration tool.  A data migration tool such as Scribe will save many hours of development and testing time for any upgrade or migration effort.  Scribe offers special migration bundles for 60-day or 180-day subscriptions.  By using Scribe, you can dramatically boost the import rate with additional clients as shown in the chart above. 
  5. Move to Office 365.  If you are not already on Microsoft Office 365, this is a good time to switch.  You can combine your user training and support changes. Dynamics 365 is administered from the Office 365 management console.
A typical migration effort involves more than one trial migration followed by testing until all migration issues have been addressed. Moving your data from on premises to the cloud takes longer than most customers expect, and you must avoid disruptions to the use of production systems. 

Contact InfoStrat or your favorite Microsoft services provider for migration services and to get answers to your questions. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan