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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Upgrade from CRM 2011 to Dynamics 365

(0) ShareShare
ReportReport
Posted on by

We are planning to upgrade our CRM instance from Dynamics 2011 to 365 On prem.  Can  some one please let me know how much time these projects typically take. We have very few customizations.  We need to upgrade Dev, Test and Production. Any help, or project plan is really appreciated. 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi Harsh,

    as you are need to do On-Premise to On-Premise upgrade, it would be straight forward (provided you don't need any customization enhancement in 365). You may also need to discuss & plan if you want to go for inplace uprade or migration.

    Refer this link: technet.microsoft.com/.../hh699716.aspx

    The only think you need to think about is... do you have any unsupported customization, javascript or any HTMl/ silverlight web resource which may not work post upgrade?

    There are already so many links/ resources available n the approach etc.

    refer the following-

    community.dynamics.com/.../234673

    community.dynamics.com/.../214564

    community.dynamics.com/.../183370

    Hope this helps.

  • Suggested answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Just noticed that you are looking for the time it take. I would say it depneds upon the approach you opt for and then how much unsupported stuff you have which you need to remove/ replace.

    To estimate the time, you first need to decide on the approach and a review of you 2011 environment so that you can come up with the estimate.

    For example, if you have a silverlight web resource then you would probably either want to drop t or rereate it with HTMl web resource. And the time to recreate would depend upon the complexity of the component.

    Hope this helps.

  • Suggested answer
    John Clark Profile Picture
    400 on at

    Hi,

    The only way to truly estimate your timescales is to test. I’d strongly recommend setting up migration VMs, one each for CRM 2013 and CRM 2015, and then the final Dev, Test and Production set of CRM 2016/365 machines. You can include SQL Server in the migration VMs if you want. You should then go through at least one trial migration of each of your orgs, noting the time and testing your customisations.

    Even though you say you have very few customisations, going all the way from CRM 2011 to D365 there with be things that can be implemented in a different (and better) manner. There are also some elements of core functionality that work differently, so you many need to make some changes to accommodate these changes.

    Do not commit to a Production migration until you are 100% clear on where you stand and what needs to be changed/updated during the migration.

    Cheers,

    John

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans