locked
Upgrade Strategy RRS feed

  • Question

  • Hi All,

    Please provide help in different upgrade strategies in order to upgrade to SharePoint Server 2016.

    Example:

    SP2013 ->SP2016

    SP2010 ->SP2016

    MOSS2007 ->SP2016


    MCP & MCTS [WSS 3.0/MOSS/SharePoint 2010] Visit: http://yagyashree.wordpress.com/

    Wednesday, March 30, 2016 3:54 PM

Answers

  • So this is for your general knowledge rather than any particular case at the moment.

    Generally for a single version hop the safest and lowest total cost move is to do a database attach migration.

    When you go to two hops then database attach can be made to work however it is often better to use a third party tool as there also tends to be significant transformation work needed.

    With three hops you should not bother trying a database attach, the underlying platform and assumptions have changed too much and a third party tool is a strong recomendation.

    Beyond those rules of thumb it has to be judged on a case by case basis.

    It is not possible to do an in-place upgrade of SharePoint 2010 to 2013, nor is it possible to do one for 2013 to 2016. It has never been a good idea, now it's flatly impossible. 

    • Marked as answer by Yagya Shree Thursday, March 31, 2016 12:31 PM
    Thursday, March 31, 2016 11:37 AM

All replies

  • Hi

    SharePoint 2016 was built on 2013 technology;
    This is because SharePoint 2016 only supports upgrades from SharePoint 2013, not from older versions such as SharePoint 2010, 2007 or 2003.

    sharepoint 2013 only support upgrades from sharepoint 2010 not from older version sharepoint 2007


    SharePoint 2010 databases need to be upgraded to SharePoint 2013 before continuing the upgrade to 2016


    so the upgrade strategy should be:

    1. SharePoint 2007 to SharePoint 2010

    2. SharePoint 2010 to SharePoint 2013

    3. SharePoint 2013 to SharePoint 2016

    karim

    Please remember to mark your question as answered, if this solves your problem.


    • Edited by karimSP Thursday, March 31, 2016 6:38 AM u
    Thursday, March 31, 2016 6:32 AM
  • Agreed with above suggestion, please find the below resources might helps you to get in detailed:
    SharePoint 2007 >>2010 >> 2013 >> 2016

    Use the database-attach method to upgrade from SharePoint Server 2007 to SharePoint 2013.

    Get help from this article to plan, prepare, and perform an upgrade to SharePoint 2013 from 2010.

    Learn how to upgrade content databases from SharePoint 2013 to SharePoint Server 2016:
    https://technet.microsoft.com/EN-US/library/cc263299%28v=office.16%29.aspx

    Gear up for SharePoint 2016 – What you need to know for your next SharePoint Migration

    SharePoint 2016 Upgrade Approach Ignite Update:
    http://www.enjoysharepoint.com/Articles/Details/sharepoint-2016-upgrade-approach-ignite-update-21142.aspx

    Migrating to SharePoint 2016

    https://www.itunity.com/bloglive/n2-upgrade-fine-sharepoint-2010-server-2016-2013-1878

    Hope this helps!

    Thursday, March 31, 2016 7:19 AM
  • Thanks Karim/nick,

    i am looking more in terms of minimum downtime and low budget migration strategy.

    Example: Existing environment matching all the hardware requirements as well as software requirements.

    Any other method we have like custom tool, Inplace, etc.?



    MCP & MCTS [WSS 3.0/MOSS/SharePoint 2010] Visit: http://yagyashree.wordpress.com/

    Thursday, March 31, 2016 8:29 AM
  • Hi,

    What is your current hardware and software requirements and what is the version of SharePoint you are using..

    inplace upgrade is not supported for SharePoint 2013. The database-attach upgrade method offers more flexibility, more control, and a better success rate..

    for your reference:

    https://technet.microsoft.com/en-in/library/ee617150.aspx

    karim


    Please remember to mark your question as answered, if this solves your problem.

    Thursday, March 31, 2016 9:43 AM
  • Hi Karim,

    Please note the ask here is to reach SP2016 from any other version of SharePoint Server.

    I am more interested in upgrading SP2013 to SP2016 using inplace method.

    Do you have any literature on that?

    Thanks

    Yagya Shree


    MCP & MCTS [WSS 3.0/MOSS/SharePoint 2010] Visit: http://yagyashree.wordpress.com/

    Thursday, March 31, 2016 9:50 AM
  • So this is for your general knowledge rather than any particular case at the moment.

    Generally for a single version hop the safest and lowest total cost move is to do a database attach migration.

    When you go to two hops then database attach can be made to work however it is often better to use a third party tool as there also tends to be significant transformation work needed.

    With three hops you should not bother trying a database attach, the underlying platform and assumptions have changed too much and a third party tool is a strong recomendation.

    Beyond those rules of thumb it has to be judged on a case by case basis.

    It is not possible to do an in-place upgrade of SharePoint 2010 to 2013, nor is it possible to do one for 2013 to 2016. It has never been a good idea, now it's flatly impossible. 

    • Marked as answer by Yagya Shree Thursday, March 31, 2016 12:31 PM
    Thursday, March 31, 2016 11:37 AM
  • Thank you all for the response!!

    Appreciated!!

    Monday, September 12, 2016 11:49 AM