Migrate from Microsoft Content Management Server 2002 to Office SharePoint Server 2007
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
Web content management, as implemented in Microsoft Content Management Server 2002, is now fully integrated into Microsoft Office SharePoint Server 2007. Office SharePoint Server 2007 includes features previously provided by Content Management Server 2002, including workflows, authentication, and Web authoring. In addition, Office SharePoint Server 2007 includes additional features of use to content managers, including integrated search, records management, RSS Feeds, wikis, and the full set of document management and site management features provided by Windows SharePoint Services 3.0.
This article presents an overview of the tools and steps required to migrate a Content Management Server 2002 application to Office SharePoint Server 2007, and it includes recommended practices that will help make each phase of the migration more successful.
In this article:
Overview of migration from Content Management Server 2002 to Office SharePoint Server 2007
Considerations during migration
Overview of migration from Content Management Server 2002 to Office SharePoint Server 2007
You migrate a Content Management Server 2002 application to Office SharePoint Server 2007 in the following phases:
Planning the migration Assess the capabilities of Office SharePoint Server 2007 and determine how each feature of your current application maps to an Office SharePoint Server 2007 feature. Optionally, investigate new Office SharePoint Server 2007 features to incorporate. Download and use the CMS Assessment Tool, which reports on the template files and features in use in your Content Management Server 2002 application and provides statistics about your application's users, roles, resources, channels, and postings.
For an overview of Office SharePoint Server 2007 and information about planning, managing, and publishing Web content by using Office SharePoint Server 2007, see the guide Planning and architecture for Office SharePoint Server 2007. For information about using the CMS Assessment Tool, including download instructions, see Assessing and Analyzing Your MCMS 2002 Application for Migration (https://go.microsoft.com/fwlink/?LinkId=82386&clcid=0x409).
Preparing your channel for migration Upgrade to Content Management Server 2002 SP2, reduce the number of templates in use in your channel, and take other preparation steps recommended in Planning MCMS 2002 Application Migration to SharePoint Server 2007 (https://go.microsoft.com/fwlink/?LinkId=82392&clcid=0x409).
Migrating your channel Content migration from the Content Management Server 2002 application to Office SharePoint Server 2007 is implemented as a feature of Office SharePoint Server 2007 Central Administration. To run content migration, first create a migration profile by using the Create Migration Profile command, and then run the migration based on that profile. You can run the same migration multiple times; after the first iteration, subsequent iterations will only migrate new or changed content. For step-by-step instructions about creating a migration profile and running a migration job, see Planning MCMS 2002 Application Migration to SharePoint Server 2007 (https://go.microsoft.com/fwlink/?LinkID=82392&clcid=0x409).
Post-migration site editing and testing Running content migration in Office SharePoint Server 2007 produces a functional site containing all the migrated content, but using an unbranded master page and an unbranded layout page for each template in the source channel. You can customize these pages to match the branding you want. You can also implement and install any custom features required to match functionality in the source channel, configure site navigation, replace Content Management Server 2002 summary pages with appropriate Web Parts, and do other post-migration customizations. For guidance about post-migration site design and development tasks, see Planning MCMS 2002 Application Migration to SharePoint Server 2007 (https://go.microsoft.com/fwlink/?LinkID=82392&clcid=0x409) and Mapping MCMS 2002 APIs to SharePoint Server 2007 (https://go.microsoft.com/fwlink/?LinkId=82399&clcid=0x409).
Considerations during migration
When planning and implementing a migration from Content Management Server 2002 to Office SharePoint Server 2007, keep in mind the following recommended practices and tips:
Before the migration
In Content Management Server 2002, ensure that all pages and files you want to migrate are checked in. Only checked-in files are migrated.
Back up the Content Management Server 2002 database. You will run the initial migration by using the backed-up database.
Delete any channels in the backup database that are unused or empty, such as channels used for navigation.
Do not delete default postings. Note that, if you migrate a site with no default posting defined, the destination site will use the default Windows SharePoint Services 3.0 welcome page and master page.
Download and run the CMS Assessment Tool. Make any changes to your site based on the reports generated by the CMS Assessment Tool. For more information about using the CMS Assessment Tool, including download instructions, see Assessing and Analyzing Your MCMS 2002 Application for Migration (https://go.microsoft.com/fwlink/?LinkID=82386&clcid=0x409).
Some Content Management Server 2002 items may use characters or naming conventions that are not permitted in Office SharePoint Server 2007. Consult the following table and ensure that Content Management Server 2002 items conform to all Office SharePoint Server 2007 restrictions:
| These items… | Cannot… | The following |
|---|---|---|
Site URLs |
Contain |
\ / : * ? " < > | # { } % ~ & |
Site names |
Contain |
\ / : * ? " < > | # { } % ~ & |
Site names |
Start with |
_ |
Site names |
Start or end with |
. |
Site names |
Be |
wpresources |
Folder names |
Contain |
\ / : * ? " < > | # { } % ~ & |
File names |
Contain |
\ / : * ? " < > | # { } % ~ & |
File names and folder names |
End with |
.files _files -Dateien _fichiers _bestanden _file _archivos -filer _tiedostot _pliki _soubory _elemei _ficheiros _arquivos _dosyalar _datoteke _fitxers _failid _fails _bylos _fajlovi _fitxategiak |
Page definition names |
Contain |
\ / : * ? " < > | # { } TAB |
Page definition names |
End with |
. |
Page definition names |
Contain |
.. |
Page definition names |
Be longer than 128 characters |
N/A |
Placeholder names |
Contain non-alphanumeric characters |
N/A |
User names (for forms authentication) |
Contain |
: |
Rights group names |
Contain |
/ \ [ ] : | < > + = ; , ? * ' " @ |
User role names |
Contain |
/ \ [ ] : | < > + = ; , ? * ' " @ |
Run the initial migration
Schedule the initial migration and subsequent incremental migrations during a period of time with the lowest activity possible.
Run the initial migration by using the backed-up database.
After the initial migration
Run subsequent incremental migrations by using the live database.
For each migration job, an error log is created and is available through the migration profile; even successful migrations may result in issues being recorded in the log. After each migration, check the error log and resolve any issues that are recorded there.
Avoid renaming or deleting channels.
Avoid changing Content Management Server 2002 users' security settings or deleting users.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Office SharePoint Server 2007.
See Also
Concepts
Plan Web site structure and publishing (Office SharePoint Server)
Other Resources
Planning MCMS 2002 Application Migration to SharePoint Server 2007
Assessing and Analyzing Your MCMS 2002 Application for Migration
SharePoint Server 2007 for MCMS 2002 Developers
Mapping MCMS 2002 APIs to SharePoint Server 2007
MCMS 2002 CMS Assessment Tool
Migration and Upgrade Information for SharePoint Developers