SharePoint Migration Recommendations

Rate this item
(0 votes)

Working of migration of SPS to MOSS 2007 in these days and would like to share my experience about number of small tricks, which really annoy you if you don’t know them, and which could save hours during your next migration

  1. Make sure that you have latest SP installed for your SharePoint 2003
  2. Run PRESCAN tool to find out potential issues
  3. Check that SharePoint 2003 doesn’t have Orphans. There are several ways for this
  4. Remove EXE, MSI, DLL extension from blocked types, because these files could exist in your collection and your can’t export such sites. (I usually remove everything from there)
  5. Check source web.config to migrate all 3rd party Web Parts into new environment (use –haltonwarning in stsadm –o export to find the pages with missed Web Parts and then navigate to source pages to export DWP from there)
  6. Export with –incluseuseonwers attribute (take into account that export of publishing subsites is not supported)
  7. Change the maximum upload file size: Central admin ->Application management ->Web Application General Settings. Set 250mb for example, or the size of the biggest file
  8. Set yourself as secondary admin(stsadm –o siteowner –url <site> –secondarylogin <user_name>), because export wont work against content if you are not admin on target site collections
  9. Before making export make sure that you are site owner for the sites you are going to export (stsadm –o siteowner –url <site> –secondarylogin <current_account>). Otherwise you can’t create any sub-sites during importing and will get strange errors.
  10. Use STSADM –o export with cabsize 1024, otherwise you silently miss some files in your export package if your site size more that 25Mb (default value)

 

Be very careful with renaming database, because if you will do it wrong way you DB is completely screwed, and there is no way to return it back. Refer to this document http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx about the right process how to rename database

Check your publishing pages (if you have any) by trying to edit them. Sometimes they can be broken after migration. You need to use these approaches – one and two to fix it.

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.