SharePoint Products >
SharePoint Products and Technologies Forums
>
SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010)
>
How to migrate content from exisitng MOSS 2007 to new MOSS 2007 server?
How to migrate content from exisitng MOSS 2007 to new MOSS 2007 server?
- Hi,
My company has 5 intranet portals built using MOSS 2007. They are not designed well and information retrieval as well as navigation is a hassle. I am asked to re-architect these portals and deploy them - i.e., do information architecture, do new MOSS 2007 installation on new virtual server, and migrate the content (as well as meta data) of 5 old MOSS 2007 intranet sites.
I have seen lot on info on how to migrate from WSS3.0-to-MOSS 2007 but none on MOSS 2007-to-MOSS 2007 servers. Is it as simple as migrating the data of databases of old MOSS 2007 to new MOSS 2007. Or is there more to it? Any inputs to links/material on this is helpful.
Thank you
Pullet- Edited byMike Walsh MVPMVP, ModeratorTuesday, December 01, 2009 6:22 AM"Need inputs on " deleted from Title. Not a problem description
Answers
- If you are going to "re-architect" then I would not move entire databases. You will be moving individual libraries, folders and even documents into a new structure. There are a few third party tools to do this. Here's one that will let you open two applications and drag and drop items between them: http://www.metalogix.net/products/sharepoint-site-migration-manager
There are many other similar tools. Maybe someone else will answer here with their experiences with similar tools.
So at what level are you going to "re-architect"? Reorganize sites (new hiearchy)? Move libraries from one site to another? Rearrange documents into assorted new libraries and folders?
Mike Smith TechTrainingNotes.blogspot.com- Marked As Answer byPullet Tuesday, December 01, 2009 1:35 AM
- Unmarked As Answer byPullet Tuesday, December 01, 2009 1:35 AM
- Marked As Answer byPullet Tuesday, December 08, 2009 1:01 AM
- Unmarked As Answer byPullet Tuesday, December 08, 2009 1:06 AM
- Marked As Answer byPullet Tuesday, December 08, 2009 1:07 AM
After new MOSS 2007 installation, you can migrate the content databases with stsadm -o addcontentdb command. You may follow the steps listed in http://technet.microsoft.com/en-us/library/cc263299.aspx . Since you just migrate database without upgrade, you don’t need to run the pre-upgrade scan tools mentioned in the article.
After database migration, you can re-organize your document libraries and lists by saving them as templates with content and then create new instance based on the templates saved.
- Marked As Answer byPullet Tuesday, December 08, 2009 1:01 AM
- Hi,
I would suggest you the steps which i had followed-
1> create a new server farm with the SQL databases and WFE. The central administration page up and running...
2> take a backup of the content databases and other databases related to the web applications from the old sql server... Also get the custom solutions that were installed in the solution management. if possibel check for other files, which needs backup..
3> Go to the new server farm.. then restore the content db and other db backups to the new sql server..
4> once the backup are restored, attach the content dbs to the new web applications created using STSADM or through the UI.
5> Then go ahead and install the custom solutions present..
6> once that is done, restore the SSP using the database backups from the old server..
I guess, that should be it.... Hope this helps...- Marked As Answer byPullet Tuesday, December 08, 2009 1:00 AM
All Replies
- If you are going to "re-architect" then I would not move entire databases. You will be moving individual libraries, folders and even documents into a new structure. There are a few third party tools to do this. Here's one that will let you open two applications and drag and drop items between them: http://www.metalogix.net/products/sharepoint-site-migration-manager
There are many other similar tools. Maybe someone else will answer here with their experiences with similar tools.
So at what level are you going to "re-architect"? Reorganize sites (new hiearchy)? Move libraries from one site to another? Rearrange documents into assorted new libraries and folders?
Mike Smith TechTrainingNotes.blogspot.com- Marked As Answer byPullet Tuesday, December 01, 2009 1:35 AM
- Unmarked As Answer byPullet Tuesday, December 01, 2009 1:35 AM
- Marked As Answer byPullet Tuesday, December 08, 2009 1:01 AM
- Unmarked As Answer byPullet Tuesday, December 08, 2009 1:06 AM
- Marked As Answer byPullet Tuesday, December 08, 2009 1:07 AM
- Mike, Thanks for the input. I got some direction with your reply. As part of re-architecture, I have to do a new sharpoint server installation on new virtual server as existing MOSS 2007 server is slow and has other servers installed on this machine. So on new MOSS 2007 server, I plan to
- use new site templates
- move libraries but shuffle some of them to different new sites as I move them (for better relevance)
- add more meta data to existing content to improve sharepoint search
- migrate site permissions, calender content, image content, etc
- migrate version history
- migrate third-party database data - example: Issue Tracker App will be rebuilt as Sharepoint intranet application with webparts that emulate IssueTracker functionality. This Sharepoint intranet application will use data migrated from Issue Tracker App database (3rd-party database).
If there is a Microsoft-released/Codeplex-released tool or some other reliable freeware/cheap tool, please let me know. Also, if someone can explain the process of doing it without using tools or give some pointers to web links that have this info, that would be great.
Thank you,
Pullet After new MOSS 2007 installation, you can migrate the content databases with stsadm -o addcontentdb command. You may follow the steps listed in http://technet.microsoft.com/en-us/library/cc263299.aspx . Since you just migrate database without upgrade, you don’t need to run the pre-upgrade scan tools mentioned in the article.
After database migration, you can re-organize your document libraries and lists by saving them as templates with content and then create new instance based on the templates saved.
- Marked As Answer byPullet Tuesday, December 08, 2009 1:01 AM
- Hi,
I would suggest you the steps which i had followed-
1> create a new server farm with the SQL databases and WFE. The central administration page up and running...
2> take a backup of the content databases and other databases related to the web applications from the old sql server... Also get the custom solutions that were installed in the solution management. if possibel check for other files, which needs backup..
3> Go to the new server farm.. then restore the content db and other db backups to the new sql server..
4> once the backup are restored, attach the content dbs to the new web applications created using STSADM or through the UI.
5> Then go ahead and install the custom solutions present..
6> once that is done, restore the SSP using the database backups from the old server..
I guess, that should be it.... Hope this helps...- Marked As Answer byPullet Tuesday, December 08, 2009 1:00 AM
- Thanks GuYuming and ssm225in. Your answers are very helpful. I will start my migration process. if I get into any issues, I will post here again. Thank you.
