Migrating from Sharepoint 2 to 3

Associate
Joined
19 Jun 2003
Posts
1,680
Location
West Yorks, UK
Hi all,
I've got a Sharepoint site using version 2, and have just discovered I can download and install version 3 (after i've done all the work!!). What's the best way to export my lists and documents into the new version?

Matt
 
Ive done this but what i recommend is that you do a test run first,

Install sharepoint 2 on another machine along with whatever version of SQL you are using, get it setup and running and upgrade the default IIS site with sharepoint.

Then restore a copy of your sharepoint content database to this server, make sure you have an account with appropriate access to the database. Open sharepoint admin and remove the current content database, then add the content database you just restored (make sure you tick that your adding an existing database). viola you now have a functional copy of your sharepoint 2 setup to work with.

From there on in install sharepoint 3. Now you have 2 options gradual or immediate upgrade.

I tried gradual and wasnt impressed with the result, the method for upgrading is using the web interface and on a 50gb content database it would time out almost consistently (after around 2hr), you have to do an entire top level site at a time... you cant do your subsites bit by bit and gradual is only if you have several top level sites as you can do them one by one. If you do use gradual then look into using the command line version of the upgrade process believe me when i say its much more reliable! Gradual will also create 2 top level sites and sites not upgraded will autoforward to the old versiom attaching a sharepoint 2 database to the sharepoint 3 site will automatically upgrade it btw

If you only have 1 top level site then what i recommend is going through the immediate upgrade process, i believe this uses the more reliable command line upgrade and you less likely to waste your time.

IMO the most important thing about upgrading to sharepoint 3 is having your users try it and play with it, once you have it running on your test upgrade system demo it to a few people (this includes yourself, lots of new options to play with for the person administering), end users get used to something and hate it when you change things, they might love it after a few weeks compared to the old version but you will have a backlash at first if you spring it on them. the new features are great but you need to check all the sites still function correctly, document any permission changes you need (permissions actually work properly in sharepoint 3, no automatic backdoor for domain admins, only full access account by default is the service account if i remember rightly) and by far the thing you need to find out most is just how long the upgrade process takes on your database, dont wander idly into it to find out your content upgrade will take 9 hours and your sharepoint is out for an entire day

Lastly, when you do this on your live system make sure you make a backup :p

Hope this is helpful
 
Hi,
Thanks for taking the time to write such a detailed reply.

I think my situation might be a little different, and I didn't explain this very well in my opening post. I've only got about 2 days work in the original Sharepoint site I setup, but this involved a lot of laborious data cleaning. There are only about 2 lists and 1 document library I need to transport. Is there an easier way to do this than the method you documented?

Matt
 
In your case id be tempted to just copy the data out and install it fresh as v3, im fairly sure you can export your lists to excel although i dont know about getting them back in.

I only really admin sharepoint, i dont actually use it since i loath the thing, i did however put the work into the upgrade because v2 had some big issues, like restoring a single file from a document library meant restoring a previous copy of the whole database which im glad to say they sorted in v3, im comin round on v3 but peoples sharepoint issues tend to occupy my time at work when i quite often have bigger priorities
 
Back
Top Bottom