When it comes to SharePoint 2007 migrations, Microsoft has plenty of different ways to approach them…well…actually only two different ways. And of course, when I sat down to perform our migration, the feasibility of each of these paths quickly evaporated. Here is the tail of my migration woes and the twisted path down which I had to travel to get it to work.
Microsoft’s website, like I said, outlines two different ways to upgrade a SharePoint 2003 portal to 2007.
The details are here.
If you detected any sarcasm or bitterness so far, it’s because of one simple little thing Microsoft didn’t really advise us on: what if we didn’t exactly have access to our SharePoint 2003 server? What then? Our 2003 environment was hosted externally, and in conjunction with SharePoint 2007’s release, our firm was getting larger and it was in our best interest to host it ourselves. So I went to the aforementioned website, and quickly found that the two simple “migration strategies” did not apply to us.
So how was I going to pull this off? Keep in mind, as I’ve gone on and on about in all my blogs, that SharePoint is really just a web application. And more importantly, all of its data is stored in SQL server. So a SharePoint migration really is just a big database backup / restore. The problem is that the tools we use and the way we need to use them is a bit convoluted. So here we go…
And there you have it! Stsadm.exe will churn, and when it’s done, there magically will be your externally hosted 2003 SharePoint portal living comfortably in your local 2007 environment. I will leave you with some considerations of this migration strategy.