Contents
If you failed to delete the web application’s root site database, you will get “Orphaned Sites” issue on running Test-SPContentDatabase cmdlet as part of migration process. This is because the root site collection exists in both content databases and leads to conflict!
Cleanup Before Migration – Clean up an environment before an upgrade to SharePoint 2013 – This includes deleting unused sites/site collections, removing unused features and solutions, Delete orphaned users and sites, Cleanup old document versions, removing features that are not supported by SharePoint 2013 (such as Web Analytics).
Can you install SharePoint 2010 on top of SharePoint 2013?
You can’t install SharePoint 2013 on top of SharePoint 2010 (as we can install SharePoint 2010 on top of SharePoint 2007) . So only migration is allowed in SharePoint 2013. You can’t re-use your existing Hardware for SharePoint 2013 (Also you can’t install both SharePoint 2010 and SharePoint 2013 on same machine).
How to backup a SharePoint 2010 web application?
Right Click your content database, Choose Tasks >> Backup Set the backup type to “FULL”, specify the backup destination and click on “OK” to start backup process Wait for the backup to complete. Repeat this procedure for All content databases of desired SharePoint 2010 web applications.
Step 10: Next Upgrade Site Collections to move to SharePoint 2013. By default, after migrating from SharePoint 2010 to SharePoint 2013, All migrated site collections will be on SharePoint 2010 format, retaining its old look and feel and other functionalities. We’ve to explicitly migrate all site collections to SharePoint 2013.
The Manage Content Database Settings page opens. If the content database does not appear in the list, it might be associated with another web application. To select another web application, on the Web Application menu, click Change Web Application.