web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / 2013 On Premise to CRM...
Microsoft Dynamics CRM (Archived)

2013 On Premise to CRM Online

(0) ShareShare
ReportReport
Posted on by VBDynamics 80

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

*This post is locked for comments

I have the same question (0)
  • ashlega Profile Picture
    ashlega 34,477 on at

    Hi,

     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.

  • VBDynamics Profile Picture
    VBDynamics 80 on at

    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 ?

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi,

    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)

  • Verified answer
    ashlega Profile Picture
    ashlega 34,477 on at

    Hi VBDynamics,

     I'm not sure where you see that recommendation to go through 2015 first. If you are referring to this link:

    technet.microsoft.com/.../hh699673.aspx

     It applies to the on-prem upgrades (since, for instance,  it's talking about the deployment of reporting extensions etc)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans