Planning MCMS 2002 Application Migration to SharePoint Server 2007
Collapse the table of content
Expand the table of content

Planning MCMS 2002 Application Migration to SharePoint Server 2007

Content Management Server

Microsoft Corporation

Published: November 2005
Updated: May 2006

Applies to:
    Microsoft Content Management Server 2002
    Microsoft Office SharePoint Server 2007

Summary:   This article is intended as a guide for technical decision makers who are considering migrating Microsoft Content Management Server (MCMS) 2002 applications to Microsoft Office SharePoint Server 2007. (7 printed pages)


Why Migrate from MCMS 2002 to SharePoint Server 2007
Two-Part Migration Process
Strategies for Migration
Phases in a Migration Project
Additional Resources

Why Migrate from MCMS 2002 to SharePoint Server 2007

Microsoft Content Management Server (MCMS) 2002 and Microsoft Office SharePoint Portal Server 2003 are truly integrated into a common architecture in Microsoft Office SharePoint Server 2007.

In Office SharePoint Server 2007, many tasks such as navigation, summary links, and scheduled deployment that an MCMS 2002 developer would perform can now be performed by users or IT professionals.

SharePoint Server 2007 is built upon Microsoft Windows SharePoint Services (version 3), which includes many features previously provided by MCMS 2002, such as workflow and authentication. In addition, because SharePoint Server 2007 is based upon Windows SharePoint Services V3, which is based upon Microsoft ASP.NET 2.0, you can use functionality such as master pages, authentication providers, and navigation providers in SharePoint Server 2007.

SharePoint Server 2007 and Windows SharePoint Services V3 offer significantly new functionality including the following:

  • Collaboration and tracking
  • Project task lists
  • E-mail integration
  • Extensible workflows
  • Richer authoring (on the Web and in Microsoft Office system applications)
  • Better multilingual support
  • Security API and extensible roles
  • Better content deployment tools
  • Web-based site management tools
  • No need for client installation
  • RSS feeds
  • Integrated search

These new features, combined with the ASP.NET 2.0 benefits in SharePoint Server 2007, enable you to build Web sites with less custom code, which means you need to do less work to maintain them.

Understanding ASP.NET 2.0 will really help your development team. An excellent place to view information about SharePoint Server 2007 and ASP.NET 2.0 is the Microsoft PDC 2005 presentations under the Office & SharePoint section.

Two-Part Migration Process

Office SharePoint Server 2007 provides functionality formerly found in MCMS 2002 functionality, however, the APIs are restructured and the Content Repository is changed to take advantage of the Windows SharePoint Services V3 core functionality.

There are two parts to the migration process:

  • Content migration   Content includes channels, postings, placeholder content, custom properties, resource galleries, resources, rights groups, users, template galleries, and template gallery items.
  • Code migration   Code includes ASPX template files, custom navigation controls, workflow customization, custom placeholder server controls, and any custom code that uses the MCMS Publishing API.
    Important   Many areas in MCMS 2002 required you to develop custom code. You can now remove that code and use the powerful functionality provided by SharePoint Server 2007 and great improvements in ASP.NET 2.0 instead. Using new SharePoint Server 2007 or ASP.NET functionality rather than trying to upgrade earlier MCMS 2002 code that performed a similar role can reduce the amount of custom code you need to write, and thereby ease code maintenance.

Content Migration

SharePoint Server 2007 has a built-in feature for migrating content from MCMS 2002. This feature is designed to migrate the following parts of an MCMS 2002 installation into an SharePoint Server 2007 site collection:

  • Channels, postings, and all placeholder content
  • Resource galleries and resources
  • Template galleries and template gallery items (not the ASPX files)
  • Rights groups and users
  • Custom properties

This feature produces a functional site with all the migrated content, provides an unbranded master page, and automatically generates unbranded page layouts for each template that you had in your source channel. You can customize these files to match your desired branding.

Note   For SharePoint Server 2007, we recommend that you use the content migration feature to migrate all of your MCMS 2002 content to a testing environment.

Content migration settings are contained in a migration profile. You can create migration profiles using the administrative user interface or using the object model. A migration profile contains information such as the source database, destination site collection, user credentials, and e-mail addresses for notifying administrators of job success or failure.

When you run a migration job, the job first analyzes the content you are migrating. If the job finds errors such as duplicate template names, you must correct those issues before re-running the migration job.

Running the Content Migration Feature

To run the content migration feature, you first create a migration profile, and then run the migration job based on that profile.

Important   To run content migration, your MCMS site must have MCMS 2002 SP2 installed.

To create a migration profile

  1. Click Start, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
  2. On the Central Administration page, click the Operations tab.
  3. Under Global Configuration, click Content Management Server Migration.
  4. On the Manage MCMS Migration Profiles page, click New Migration Profile.
  5. On the Create Migration Profile page, do the following:
    1. Type a Name.
    2. Type the Database server name.
    3. Select a Database name to migrate from.
    4. Select the Authentication type.
    5. Type the User name and Password of a user with rights to the MCMS Content Repository.
    6. Click Connect.

      After your connection succeeds, the text Connection succeeded appears beside Connect. You must have a successful connection before using your profile. If the connection does not succeed, verify the server name, user name, or password.

  6. Select a destination Virtual server.
  7. Select a destination Site collection.
  8. Select a Channel to migrate as the top-level site.
  9. Optional: In the Notification section, select Send e-mail when migration job succeeds and/or Send e-mail when migration job fails, and then type the e-mail address.
  10. Click Save.

To run a migration job

  1. On the Operations tab, click Content Management Server Migration.
  2. In the Manage MCMS Migration Profiles page, click your migration profile, and then click Run.

    You can view the status of your migration job while it runs or after it finishes by clicking the Status link.

Code Migration

After running the content migration tool, you will have a functioning SharePoint Server 2007 site with all of your content and a set of unbranded page layouts. To migrate your template code, edit each unbranded page layout. For more information, see Page Layouts and Master Pages ( ) in the Microsoft Office SharePoint Server 2007 SDK.

If you used ASP.NET 2.0 master pages in your MCMS 2002 site, you can upgrade them for your migrated SharePoint Server 2007 site. Otherwise, create a new master page and upload it to the site.

Add (and in some cases rewrite) custom controls you used in templates on your MCMS 2002 site to your new page layouts. Rewrite custom placeholder controls and placeholder definitions as SharePoint Server 2007 field controls, and then add them to your page layouts. If needed, rewrite customizations to the Web Author console by customizing the authoring console XML file in SharePoint Server 2007.

SharePoint Server 2007 provides a lot of default functionality that was not in MCMS 2002, so you should not have to rewrite 100 percent of your MCMS 2002 application. In general, the total amount of custom code required in an SharePoint Server 2007 site should be much less than in MCMS 2002.

Use the new SharePoint Server 2007 features, and only rewrite earlier application code using the SharePoint Server 2007 APIs where appropriate. The following table shows common custom code MCMS 2002 features that are default features in SharePoint Server 2007.

Table 1. Custom code MCMS 2002 features that are default features in SharePoint Server 2007

MCMS 2002 Feature SharePoint Server 2007 Feature
Navigation ASP.NET–based navigation provider model.
Search For more information, see Searching in Office SharePoint Server 2007 (
Summary pages Summary Links, Content by Query, and Table of Contents.
Deployment scripts Built-in content deployment user interface.
Form login screen ASP.NET–based authentication provider model.

Strategies for Migration

If your MCMS installation is dedicated to a single Web site, you must migrate the entire application at one time. In this scenario, you create a single migration profile and specify the root MCMS channel in the profile.

Ideally, you first run migration so that you can use the data from your old site to develop your new site, especially your new page layouts. When you are satisfied that the new site works properly, run the same migration job again as an incremental migration to migrate any content created since the first migration.

If you have multiple sites in independent top-level channels of your MCMS 2002 installation, you can choose to migrate them one at a time, or all at once. Choose one top-level channel as a pilot project for migration, learn the migration process, and then apply your findings to the remaining channels. This means that you must run both MCMS and Office SharePoint Server 2007 until you finish migrating all MCMS sites.

In this scenario, you create migration profiles for each top-level channel. As each new SharePoint Server 2007 site is tested and approved, your IT department can redirect users from the old MCMS site to the new site. You can use the same incremental migration strategy as for a single Web site for each individual top-level channel.

Important   You can run SharePoint Server 2007 on the same computers as MCMS 2002; however for Beta 2, we recommend you run them on separate computers.

Migration can take time, especially if you are developing new master pages and page layouts, or writing new custom controls. The content migration feature of SharePoint Server 2007 is designed to accommodate this by allowing an initial migration that can then be followed by incremental migrations. In this way, you can develop and test your new page layouts and master pages using the content of your site, while continuing to publish through your existing MCMS 2002 site.

After you finish development on the new site, perform a final incremental content migration, and then move the new site into production.

The first step to a successful migration project is to aim for functional equivalence. Functional equivalence means migrating your MCMS 2002 site to an SharePoint Server 2007 site with equivalent functionality before adding new features.

You may be tempted to modify your site during migration to take advantage of the new features available in SharePoint Server 2007, but it is better to focus first on migrating to a functionally equivalent application, which offers the following benefits:

  • You can list the features of the existing application to produce a full set of requirements for the new application.
  • You can compare the functionality of the new application to that of the existing application to determine when the migration is complete.

Phases in a Migration Project

  1. Planning
    • Stop developing new code on the MCMS 2002 site, and limit structural changes during migration, for example, avoid extensively changing page definitions, channel hierarchies, or site security.
    • If you use third-party components, determine if you can use them with SharePoint Server 2007, if there is an equivalent component available for SharePoint Server, or if you can use SharePoint Server functionality instead.
    • An MCMS 2002 farm may contain many Web sites. Determine the order in which to migrate sites. Consider choosing a single site to migrate first as a pilot project.
    • Run the SharePoint Server content migration tool on your site. It reports items in the MCMS 2002 Content Repository that you need to change before you migrate to SharePoint Server 2007.
    • Run the CMS Assessment Tool to produce reports you can use in your planning, such as the number of postings per template. Heavily-used templates are a high priority. The tool also checks the Content Repository for potential migration issues.
  2. Preparing Your MCMS 2002 Site for Migration
    • Upgrade your application to MCMS 2002 SP2, which adds support for Microsoft SQL Server 2005, Microsoft Visual Studio 2005, and Microsoft .NET Framework 2.0.
    • Modify your application to use ASP.NET 2.0 features. For more information, see Designing Your MCMS 2002 Solution for Reusability.
    • Minimize the number of templates. You can implement most sites with fewer than 30 templates.
    • Use ASP.NET master pages in your MCMS 2002 templates to encapsulate styles, layout, and other site branding artifacts.
    • Modify your navigation controls to use ASP.NET navigation provider based on the MCMS 2002 Publishing API.
    • If your site uses ASP.NET forms authentication, use ASP.NET authentication provider.
    • Move business logic code out of template files and encapsulate calls to the MCMS 2002 Publishing API into a data abstraction layer. To display information from one of your business applications, create server controls to contain the logic. Then place the server controls on your template file.
    • Perform test migrations of the MCMS 2002 Content Repository, and try to resolve the issues you find before performing a final content migration.
    • Develop test scripts for the most used features of your site to determine functional equivalence and provide a good user transition.
  3. Upgrade
    • Use the Content Migration feature to migrate your content to a new SharePoint Server site.
    • Apply your master pages to the new site to add branding.
    • Update or replace the unbranded page layouts generated by the content migration tool to match your desired layouts and branding.
    • Migrate custom placeholder controls and other controls, remembering that you may be able to replace custom controls with the default functionality in SharePoint Server.
    • Debug the page layouts to make them operational.
    • Change providers for your navigational controls.
    • Migrate code in the data abstraction layer.
  4. Testing
    • Run the test scripts designed in the preparation phase.
    • Correct all bugs detected until sites are stabilized.
  5. Deployment
    • Test your deployment.
    • Deploy your application.
  6. Advance
    • Enhance your application to take advantage of more features in SharePoint Server 2007.


You have many factors to consider when you migrate your MCMS 2002 applications to Microsoft Office SharePoint Server 2007. Most applications will benefit from migration to SharePoint Server 2007 because of the significant enhancements it can offer. With good planning, a successful migration can lead to a foundation for your applications upon which you can build for many years to come.

Additional Resources

© 2016 Microsoft