Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM 2011 migration to ...
Microsoft Dynamics CRM (Archived)

CRM 2011 migration to higher versions

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi,

We have a CRM 2011 on-premise organization and we are planning to migrate to CRM 2016. It can be done by following the path from 2011 to 2013, 2013 to 2015 and 2015 to 2016. We have a lot of customizations and some are unsupported. The customizations which will not work in the new environment can be identified using Custom Code Validation Tool.

Can anyone please suggest that where to use this tool? Using within CRM 2011 will highlight the customizations which will not support in CRM 2013. But can we check the unsupported customizations within CRM 2016 directly rather than checking within all the environments i.e 2011, 2013 and 2015?

*This post is locked for comments

  • Suggested answer
    Nick.Doelman Profile Picture
    Nick.Doelman 1,947 Most Valuable Professional on at
    RE: CRM 2011 migration to higher versions

    Here is what I would do:

    -Get a copy of CRM 2011 database, deploy it as another org and/or on test environment

    -Strip out offending javascript identified by custom code validation tool (delete libraries)

    -upgrade CRM 2011 database to 2013, 2015, 2016

    -manually add code back to CRM 2016, fixing the incompatibilities (look for ways Business Rules, Sync workflows, etc could be used instead)

    -create a solution with all the "fixed" code

    -On "go live" day, do the same thing for the prod database, strip out custom code, upgrade path and then import your "fixed" solution at the end.

    Obvious a lot more planning then just these steps, but that is the jist of it.

    Cheers

    Nick

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: CRM 2011 migration to higher versions

    Better approach will be to go through all the versions and remove unsupported script version by version. You can try your approach but I am not sure of this. Refer this.

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

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: CRM 2011 migration to higher versions

    Yes.. We have to migrate from CRM 2011 to CRM 2016. But we want to reduce our workload by changing the code according to CRM 2016 only. So, is it possible to change  the javascripts in CRM 2016 environment directly rather than all the way to CRM 2016?

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: CRM 2011 migration to higher versions

    If you are upgrading from CRM 2011 to CRM 2013 you have to install Custom Code Validation Tool for CRM 2013 in CRM 2011 environment and so on.

    dynamicscrmherald.wordpress.com/.../custom-code-validation-tool

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans