Recently, my organization is planning for SharePoint 2010 upgrade. We decide to go with Database content migration as it is less impact with down time due to hardware and software requirement (64 bit) in SharePoint 2010.
We have a sub-site which contains a lot of customization such as master page, custom list, web parts and a lot of content. There is also a solution was built for that sub-site as well. However, as the time past by there quite a few update and manual creating
from power users which concern to me that the solution package that we have does not up to date that can be use for SharePoint 2010 upgrade.
I am planning to re-package the solution for the upgrade with all the changes users made for SharePoint 2010. But the question is how do I migrate the content of existing site when we upgrade to 2010? It is also possible that they want to change the sturction
of the site when migrate eg: make this new upgrade site as top site collection instead of sub-site.
Another concern is what happen after I finish making re-package the solution but during the re-package period users might make more change to the existing site?
I would greatly appreciate for any ideas, suggestions as well as best methodology I should take.
View Complete Post