none
SharePoint 2010 to 2013 Migration Limitations RRS feed

  • Question

  • Hi All,

    I would like to know what all are the limitations that we have to face while migrating content from sharepoint 2010 farm to Sharepoint 2013 farm. I know there are two approach for this 1) Using DB Attach Detach and 2) Using Tools like avapoint or sharegate etc. My question is what is the difference between these two, what is the limitations of these two process. I know i few differences like, Using DB Attach detach process, the content and the workflows will be migrated but the customly coded wsps will not be migrated. Whereas while going for the Tools, the custom components can be migrated, but the workflows cannot be migrated. So i need to know the complete limitations,pros and cons of these two methods. Also let me know about the infopath migration as well.

    Thursday, October 10, 2013 8:19 PM

Answers

  • I think the other guys sum this up well, in that there are a lot of variables that'll come into play here.  In regards to the freebie tools, I'd draw your attention to the pre-upgrade checker and the sort of issues that'll report.  The literature can be seen here http://technet.microsoft.com/en-us/library/cc262231(v=office.14).aspx

    And the specific points that you may encounter have been documented here http://blogs.msdn.com/b/subbu/archive/2012/05/20/fixing-test-spcontentdatabase-warnings.aspx

    Paid tools convey the massive benefit of being platform agnostic and may save you some heavy lifting.  Alex mentions that these have a cost implication but this may be quantifiable against the value of the time lost when using the native tools.

    I'd aslo encourage you to carry out a brief audit before attempting any migration piece.  You may find some stuff that can stay where it is.

    • Marked as answer by Lindali Thursday, October 17, 2013 11:03 AM
    Tuesday, October 15, 2013 12:09 PM
    Answerer

All replies

  • its depend upon the alot of things, amount of content, size of farm, amount of customization, etc

    check the this Best practices http://technet.microsoft.com/en-us/library/cc261992.aspx

    check this white paper as well: http://www.metalogix.com/Libraries/Product_Collateral/Best_Practices_For_A_Successful_SharePoint_Migration_or_Upgrade.pdf


    Thanks -WS SharePoint administrator, MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog *Please remember to mark your question as "answered"/"Vote helpful" if this solves/helps your problem.*

    Thursday, October 10, 2013 11:07 PM
    Moderator
  • thanks for reply .but the links which you have provided are for successfull migration. My actual question was what are the pros and cons of migrating farm from 2010 to 2013 using 1) DB attach detach Process and 2) using a third party tool.....
    Monday, October 14, 2013 10:26 AM
  • Unfortunately; It Depends

    I would by default look at the OOB tools first of all. The main advantages are that it's free, massively documented and has lots of communal knowledge if you hit issues. The main downside is that it only allows upgrading from the previous version (ie. 2010 -> 2013).

    If you've gone for heavy customisations or have complicated re-structuring or modifications that you want to perform as part of the migration then a third party tool starts to become worth while. If you're on an earlier version (2007 or worse, 2003) then a third party tool can cut down the pain significantly. The main down side is obviously that it costs money.

    There are a myriad of pros/cons for each of the third party tools compared to the OOB upgrade approach. It wouldn't be a bad idea to read through the DB attach model and to perform a test upgrade (this is part of the process). If you hit a million issues doing that then pause and see if a third party tool is better suited, if there are no issues then there's no need for the third party tool.

    Or, if your farm is unusual in some way, let us know the details and we might be able to advise.

    Monday, October 14, 2013 11:33 AM
  • I think the other guys sum this up well, in that there are a lot of variables that'll come into play here.  In regards to the freebie tools, I'd draw your attention to the pre-upgrade checker and the sort of issues that'll report.  The literature can be seen here http://technet.microsoft.com/en-us/library/cc262231(v=office.14).aspx

    And the specific points that you may encounter have been documented here http://blogs.msdn.com/b/subbu/archive/2012/05/20/fixing-test-spcontentdatabase-warnings.aspx

    Paid tools convey the massive benefit of being platform agnostic and may save you some heavy lifting.  Alex mentions that these have a cost implication but this may be quantifiable against the value of the time lost when using the native tools.

    I'd aslo encourage you to carry out a brief audit before attempting any migration piece.  You may find some stuff that can stay where it is.

    • Marked as answer by Lindali Thursday, October 17, 2013 11:03 AM
    Tuesday, October 15, 2013 12:09 PM
    Answerer
  • I would suggest to proceed your migration using third party tools. Migrating manually will be very tedious and consumes more time. Also, chances of success in migration is not guaranteed. You may have to do some post migration tasks to make it successful.

    Where as third party migration tools will ease your migration and you can  migration very easily to which ever destination platform in few clicks. You can try Vyapin Dockit Migrator as it comes with so many ootb features. Know more about Vyapin SharePoint Migration Tool

    Wednesday, September 18, 2019 7:11 AM