1

When upgrading to SharePoint 2013, should the SharePoint 2010 content database have all site collections using the 2010 Visual Upgrade? We currently have a few sites that are still running on the 2007 user interface.

I have done some testing with performing the db attach without upgrading the 2007 ui to 2010 and haven't had any issues in the new SharePoint 2013 farm. Are there any potential issues that could arise if the Visual Upgrade to all SharePoint 2010 sites is not completed prior to migrating to 2013?

2

it makes no difference.

When migrating from 2007 to 2010, the content db is migrated and so is the ui settings as it resides within the content db.... i think its just xml and xslt content. The only reason that i could see to change the UI would be for UI testing to make sure everything from 2007 to 2010 is properly migrated over (custom UI wise).

You should disregard the 2010 ui as there are some features in 2007 that dont exist in 2010 and in 2010 that dont exist in 2013 so you might have some errors on pages where the webparts failed as they dont exist. From a UI perspective it makes no difference as from 2007 to 2010 to 2013 as it will change on each upgrade and wasting your time ammending them!

like i said using 2010 is just the middle man to prepare the content database (layout of content within tables) for 2013. Its the content that i would be more worried about and the associations like alerts and workflows that should stay intact. The ui is interchangable and shouldnt cause any potential issues when fully migrated to 2013.

The biggest problem would be as noted the content, like checkout items and workflows showing pre checked out state (not updated) even tho looking in 2007 its uptodate!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.