none
upgrae question

    Question

  • So we r still on server 2010 (...), I finally got the go-ahead to plan... From what I read is  there is no direct upgrade path to 2016. I'm wondering if anyone is in the same boat and what approach they r taking.

    This is our intranet so we have customizations (farm solutions to change the UI mainly), some 3rd party add-ons and many content DBs... so lots to do for the upgrade and many things to test... so to me it is too risky to combine two upgrade together. Any one can offer any advice? Much appreciated!

    TIA!


    wc

    Friday, November 10, 2017 3:00 PM

All replies

  • Hi,

    As per Microsoft there is no direct upgrade path from SharePoint 2010 to SharePoint 2016 if you are using Content DB detach-attach . Reference :

    NOTE Site collections provisioned in backward compatible SharePoint 2010 (14) mode, must be upgraded to 2013 prior to upgrading to SharePoint Server 2016.  For additional information on upgrading site collections to SharePoint 2013 see also https://technet.microsoft.com/en-us/library/jj219650.aspx.

    However you may use third party  tools like Metalogix, Avepoint or ShareGate to do the migration directly from SP 2010 to SP 2016. This is the only way to do it directly skipping SharePoint 2013.

    Metalogix - How to Migrate From SharePoint 2010 to SharePoint 2016

    Avepoint - Migration path for SP 2016

    ShareGate - Direct Upgrade

    Regards,

    Priyan


    Please Up Vote and Mark this as Answer if it helps.


    Saturday, November 11, 2017 8:34 AM
  • The process of upgrading your existing SharePoint 2010 farm to SharePoint 2016. Just like it has been the case with the last 3 product release cycles, there are no In-Place upgrade paths for SharePoint 2016. You basically have to build a new SharePoint 2016 SharePoint Farm, and then bring your content databases over

    Check below blogs: 
    http://nikcharlebois.com/upgrade-from-sharepoint-2010-to-sharepoint-2016/
    https://technet.microsoft.com/en-us/library/cc303420.aspx
    http://www.microsoft.com/en-us/download/details.aspx?id=30370
    https://technet.microsoft.com/en-us/library/cc303420(v=office.16).aspx

    Regards

    Prasad Tandel


    Saturday, November 11, 2017 9:42 AM
  • You have lots of excellent resources to work with.  Study the TechNet resources to upgrade to 2013 and then to 2016 here:

    Basically, the process goes like this (presuming everything's in the same domain and that you have a 2016 farm already deployed):

    1. Setup a small temp 2013 farm
    2. perform database attach 2010 to 2013 on temp farm
    3. perform claims upgrade, migrate users
    4. perform database attach 2013 to 2016 on 2016 farm
    Saturday, November 11, 2017 7:48 PM
  • Step by step guide to upgrade from SharePoint 2010 to SharePoint 2016:
    http://expert-advice.org/sharepoint/upgrade-from-sharepoint-2010-to-sharepoint-2016/
    Monday, November 13, 2017 11:04 AM
  • I appreciate all answers... I understand how the upgrade process will go as I've been SP admin for many years however it is the risk I'm worrying about when combing two upgrade with customization/3rd party add-on/amount of data. If it is just some team sites sure no problem staging it... however this is the intranet we are dealing with which not only has hundreds of collaboration sites but also the intranet portal with UI customization. Without the whole thing running on 2013 I do not feel comfortable going to 2016 to be honest. I wish MS could provide direct upgrade path...

    wc

    Monday, November 13, 2017 2:15 PM
  • Scale is not a factor here in upgrade so much as configuration.  Separate things out. Don't be daunted by the size.  Decompose the problem into smaller portions.

    You can test site collection scope customizations by just deploying that one site collection to your test farms and then testing the upgrade path.  Customizations in one site collection should not be impacting other site collections.  Even the master pages are different.  Uploaded site collection scope solutions only impact the site collection they're uploaded to - not any others.  Test the potentially problematic site collections individually.  Or maybe a few together at a time.  So:

    Similarly, if you have farm-level custom solutions, these should apply equally whether you have one user site collection in the farm or a 100.  Test farm solutions in a similar manner.  Just migrate one or two site collections through the pathway that employ the farm solution , and then test the farm solution after each upgrade to see how it performs.

    Monday, November 13, 2017 4:29 PM
  • You are right. As of now direct upgrade is not an option unless we use a third party migration tool. If you have found an answer, you may post it here or you may close the thread by marking the helpful post as an answer so that users facing similar issue will find it useful. 

    Regards,

    Priyan


    Please Up Vote and Mark this as Answer if it helps.

    Monday, November 13, 2017 5:56 PM