Migrating SharePoint Objects
April 27, 2009
I like the notion of federating; that is, leaving information where it is and then pulling what’s needed without crating a duplicated source store. I was interested in this Web log post “Migrating SharePoint Content between Different Site Templates and Preserving all the Necessary Metadata” because the approach ran counter to my method. Migration is sometimes necessary; for instance, a merger requires that the acquired firm’s information be placed under the control of the purchaser’s information technology department. If you need a method to migrate SharePoint, you will want to navigate to Boris Gomiunik’s article here and download the steps. There are eight steps, and I did not see a quick and easy way to automate this set of procedures. Like much in the SharePoint environment, a human must enter values and make decisions. The approach is great for the billable SharePoint consultant and makes a SharePoint administrator a must-have headcount. But for the senior manager, the costs associated with this somewhat tedious procedures are likely to be an issue. In my experience, the more manual intervention in a method, the greater the chance for mistakes. SharePoint may be a candidate for the cloud because in today’s financial climate eliminating headaches, errors, and expenses may reduce on premises software installations magnetic appeal. There was no reference to what fixes had to be made to get the SharePoint search system to rebuild its index and point to the correct instance of the migrated and potentially duplicate content. I wonder if that requires another multi step process involving lots of human fiddling?
Stephen Arnold, April 26, 2009
Comments
-
- Subscribe to Beyond Search
Feature archive
News archive
-
