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
I am aware that Microsoft recommends an upgrade from 2013 to Dynamics 365 by doing the upgrade to 2015 first. However since the solution import of 2013 is compatible with Dynamics 365 and if we need to move from Online to On-Premise and this would invariably involve data migration , could we not directly move into Dynamics 365 online from 2013 without needing a move into 2015 first. Am I missing something here ?
Thanks & Regards
I believe you'd need to upgrade from 2013 to 2015 etc if you were doing an inplace upgrade. If it's solution + datamigration, you can do it either way. Although, if you had 2016 on-prem, it would be better aligned with 365 online (in terms of attributes, for example), so that might mean you would need a bit less data conversions when migration the data.
Thanks, what I meant was if we have to move from 2013 on-premise to online(365) , since there is no inplace upgrade for this, even if we moved via 2015 it would still be solution+data migration from there hence I am not clear on the need for the move to 2015 step in-between as it does not add anything much to the move ?
To migrate your datas, I would recommand Kingswaysoft: www.kingswaysoft.com/.../Announcing-Migration-Starter-Pack-for-CRM-Online-and-CRM-On-Premise
And If you need like an integration with other services maybe Scribe is better.
That was for the data part. For your solution, the problem is that you can't import it from CRM2013 to Dyn 365. The easiest/quickest way is to create an empty CRM2013 organization, import your solution in it and do the CRM2013->CRM2015->CRM2016 solution migration. Then you can import your CRM2016 in Dyn 365.
Don't forget that you need to check your code, because some functions are deprecated(going from normal form to turboform)
I'm not sure where you see that recommendation to go through 2015 first. If you are referring to this link:
It applies to the on-prem upgrades (since, for instance, it's talking about the deployment of reporting extensions etc)
Business Applications communities