Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hope some one can answer in case if they have come across similar upgrade. We are trying to move from 2013 on premise to dynamics 365.
We are not going to intermediate version but I was able to import the 2013 solution to latest 365 environment and all the customizations are imported. I was planning to Take the backup of _MSCRM database from old 2013 server and restore it on the new database server.
I have below questions on the data migration.
1. I don't want to touch the config database. I just need the customizations and data. Restoring only _MSCRM will work or we run into any issues? Do I need to import two databases or one? If I import other database I believe it will over write all the CRM 365 latest metadata and all system related configurations that are installed with Dynamics 365 installation. I just need to bring in the data.
Can you please suggest the steps that I need to perform to import the data from Sqlserver without impacting any other things..
Hi, There are a few versions of difference between 2013 and 365, so there are always issues which you might encounter.
I would say you can do one of two things to test this out:
1. Create a backup of your 2013 database and restore it in the 365 database server.
2. Copy the mdf and ldf files from the 2013 and add them to the appropriate locations of the 365 database and add the database to the server.
After the database is on the new server and restored, on the CRM Server in Deployment Manager, Import organization and see that it is imported successfully.
You should be able to test it out after that.
Hope this helps.
Thanks Levin. I was planning for the same but I was hesitant whether to import 2 databases or one ? As per my knowledge if we import config db it will break on first step. I believe I just need to import _MSCRM db only and try ?
The Microsoft FastTrack for Dynamics 365 customer success service provides guidance on steps for data migration to Dynamics 365 Customer Engagement. Microsoft provides guidance for you by offering a combination of tools and documentation and by performing configuration tasks where applicable and feasible. This is available for all eligible customers with Dynamics 365 services for Customer Engagement Online who are invited into the program. Microsoft Dynamics CRM 2013 (On-premises) is supported for this migration process so take advantage of it if you can. Read this article for more information on Microsoft FastTrack for Dynamics 365.
There are three main upgrade options when upgrading to Dynamics 365 Server, version 9.0 (on-premises). Migrating by using a new instance of SQL Server, Migrating by using the same instance of SQL Server, and In-place upgrade. Check out my blog post which explains the benefits, drawbacks, and differences between the three approaches and ranks the upgrade options accordingly.
Business Applications communities