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 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
in our company we have dynamics crm 2011 and we need to update our CRM to dynamics crm 365 on premise V9.0
i've read several articles about the steps and i found two options:
direct migration option from 2011 to dynamics 365
cumulative upgrade from 2011 to 2013 to 2015 to 2016 then to dynamics 365
but unfortunately, i'm note able to decide which is the best way and how to implement it. For that please i need your help with this matter
Thanks in advance
You can't just upgrade from 2011 to D365 directly. To do that you will have to manually recreate all customizations and write scripts to migrate the data.
I believe that doable path for you is the step by step migration - 2011 -> 2013 -> 2015 -> 2016 -> 9.0. That would not require manual customization and data migration.
Thank you for your prompt response,
what do you mean by recreate manually?do you mean we have to export solutions from the existing instance and re-import them to the new server ? and we have to use a migration tool to migrate the data because the schema of the database has been changed from the 2011 to v 9.0?
i'm thinking about the migration option because the second option is risky a little bit
You will not be able to export solutions from 2011 and import to 9.0 because there is no direct compatibility.
With manual recreate I mean that you will have manually recreate entities, fields, forms and so on.
For me path 1 is more risky than 2.
I did upgrades from 2013 to 9.0 and I had no issues with it.
could you please share with me the steps that you did during the upgrade process? specially on the server level
because our crm installed on the windows server 2012 and we need to install the 9.0 on windows server 2016
have you duplicated the existing instance before you start the upgrade plan? just in case anything happen during the upgrade?
In order to do that migration I created separated installation for every version - 2013, 2015, 2016 and migrated DB in sequent way. For every installation I use supported versions of Windows Server and SQL server.
okay it's very clear now.. so i can use the migration option sequentially from 2011 to 2013 and so on until we upgrade to V9.0
So from 2011 to 2013 there is no compatibility issues with export and import the solutions .
but what about the database schema between 2011 and 2013 this will not make any issue during the migration phase
and about the product keys have you used the trial versions between 2013, 2014 and 2016?
Thank you so much for your help
Organization import should fix all differences in DBs, bring new entities and so on.
For migration I used trial keys that are available by the same url as packages. For example 2013 - www.microsoft.com/.../details.aspx under details section you have trial key - CQWW3-TNXBF-HRQWC-CVTW9-M968H
I have done this upgrade from Dynamics CRM 2011 to Dynamics 365.
What you need to follow is;
-> Consider compatibility of Windows Server and SQL server before upgrading Dynamics application.
-> You can setup a separate server for each version, or everything can be handled in-place in one server.
Thank you Erhan,
And how did you upgrade from version to another? Database export and import to new installation and import organization? Or using the installer??
If we need a new server we have to use data migration and not in place upgrade as we talked above
I would not recommend doing in-place upgrade because once you upgraded inline you can't back up.
I would recommend to create a dedicated server for every of transit versions.
Thank you again Andrew
So i will create separate servers for each versions with trial key. Then i will backup crm databases and restore them and finally import organization using deployment manager and so on for each installation
Thank you for your help
Some upgrades happened in-place, some in separate servers due to operating system requirements. For the separate servers, we used organization import.
There are pros and cons, there is no right and wrong for the upgrade methodology. We took snapshots for each step to be able to revert back.
Can you please share the approach finally which you have used. Becuase in our company we have dynamics crm 2011 and we need to update our CRM to dynamics crm 365 on premise V9.0.
If you will share it, it would be veru help ful for us.
Business Applications communities