Our client wants to change from SharePoint 2.0 to 3.0. Of course they need all the documents to be migrated too. I have some experience with 3.0 -> 3.0 migration, but that's all.

Main requirements are:

  • Document export from 2.0, import to 3.0
  • Migrate attributes too (CreateDate etc.)
  • Bulk mode

migrated from stackoverflow.com Mar 27 '12 at 21:58

This question came from our site for professional and enthusiast programmers.

  • just to note: we skipped automatic migration process. despite of this I'm open for other - and usable - migration tools. – boj Jun 26 '09 at 19:03

You can perform an upgrade install which will upgrade your existing 2.0 site to 3.0. It is outlined in this Microsoft document which should provide the info you need, and there is more information here as well. I have used this process in the past and it does keep the documents intact and is usually relatively pain free. Just make sure you make some site collection backups as well as DB and IIS backups before you start as the upgrade isn't easily reversed.

  • 1
    Be very careful about this if your site has any custom changes, or is an SPS installation. A migration like this should be carefully planned to avoid issues later on. – WebWires Apr 28 '09 at 15:17
  • Yes, that's my problem too. An export/import (only with document libraryies) were a cleaner solution. Where can I find tools for it? – boj Apr 28 '09 at 22:17

Using a tool like Quest's Migration Manager may be something to consider, especially if the 2.0 site needs to be live and updated during the migration process. It's not cheap, but it can handle changes that occur during and after migration while you are still waiting to make the new 3.0 site live.


I've had a lot of success doing this with Metalogix SharePoint Site Migration Manager. It migrates all the attributes you listed plus things like permissions and views. It can also run on the client with only a small server install and is very easy for an end user to manage (if that's of benefit to you).

Any process without using a third party tool tends to be pretty clunky and laborious. Save your sanity and use a third party tool.


I'm doing migration scenarios for a consultant firm based in Montreal.

Here's what we usually do :

  • Define governance for the new SharePoint platform
  • Define the new Information Architecture
  • Implement the new Information Architecture (build sites, lists, libraries, etc.)
  • Migrate the content over from 2.0 to 3.0

Tools such as Sharegate (www.share-gate.com) can help here.

Hopefully, this will help you!

Your Answer

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