locked
SharePoint Migration RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    So the story so far:

    I have a client who uses SharePoint on there windows small business server 2008. We are migrating them into our enterprise environment and would like to move there SharePoint site to a new server preferably 2012 R2 but 2008 R2 would be fine. 
    We are going to be using the foundations version of SharePoint. 

    I am looking for some direction on how to do this. 

    I have tried to do the following:

    STSADM.EXE -o export -url https://URL/ -filename c:\test\test1 -overwrite -includeusersecurity -force -verbose

    and then 

    Import-SPWeb -Identity "http://URL/ -path "C:\xxxx\xxx" -Force -Verbose

    But this gives me an error:

    Import-SPWeb : The version of the package 12.0.10.0 is different from the current version this program supports, 15.0.0.0.

    I looked into this and asked a question but did not really understand the answer.

    http://social.technet.microsoft.com/wiki/contents/articles/22063.direct-import-spweb-from-wss-3-0moss-2007-to-sharepoint-2013.aspx

    I have also tried:

    stsadm -o backup -url http://oldportal -filename C:\oldportal.dat

    take the .dat to the new server, create a new WebApplication with a Blank Site Collection

    stsadm -o restore -url http://newportal -filename C:\oldportal.dat -overwrite

    I received this at the end of the command: <nativehr>0x80070003</nativehr><nativestack></nativestack>

    The site still does not work.

    IF anyone could help that would be awesome.

    Thanks!!


    Thursday, July 24, 2014 3:28 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    you aren't just moving to an enterprise farm, you are jumping versions.  SharePoint doesn't even handle export/import or backup/restore between service pack levels, let alone major build versions.

    To upgrade, you either need a 3rd party tool, or a database attach upgrade.

    there is no direct path 2007-2013 without a tool.  it would be 2007 -> attach the content database(preferably a backup/restore from SQL) to a 2010 farm -> attach content db to the 2013 farm.

    there is a lot of testing and work that may need done here as this is a serious move.

    check these out to get started:

    upgrading to SP2010 - http://www.microsoft.com/en-us/download/confirmation.aspx?id=3837

    http://technet.microsoft.com/en-us/library/cc303420(v=office.14).aspx

    upgrading to SP2013 - http://technet.microsoft.com/en-us/library/cc303420(v=office.15).aspx

    http://www.microsoft.com/en-us/download/details.aspx?id=30371

    fyi, if they are only using foundation and running SBS to this point, it should be fairly painless (as much as it can be for SP upgrades)  if they don't have any custom code, you may just buy a tool to do this.  it would probably still be cheaper than the time to stand up farms and do both migrations for this particular scenario.  ShareGate is pretty dang good and really cheap (migration products range up to over 100k in price).  since its a basic farm, I would definitely stick with them.  I don't like recommending 3rd party tools, but it sounds like you might want to look into it for this one http://en.share-gate.com/

    you could also check with Metalogix, avepoint, dell, lots of company's have migration tools for skip-level upgrades.

    Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

    Thursday, July 24, 2014 7:28 PM