SharePoint Site Migration Manager Supported Features

Last Updated: May 17, 2010. SSMM Build: 3.6.38

Note: The "Service" column indicates whether the features require installing the Metalogix Extensions Service (the service ships with SharePoint Site Migration Manager). Most features that use the service require that it to be installed on the target SharePoint server.

Metalogix SharePoint Site Migration Manager will copy the default.aspx page, as well as all non-web part page files that are stored on the root of a SharePoint site.

Your input is valuable to us. If you have a feature suggestion or request, please e-mail them to support@metalogix.com.

Comments

Metadata
You can copy documents and many types of list items to a target machine that does not have the Metalogix service installed, but the four edit information fields will not be preserved. The four edit information fields are:
Created: The date and time that the list item was created.
Modified: The date and time that the list item was last modified.
Created By: The user who created the list item.
Modified By: The user who last modified the list item.
back to table

Document Library and List Version History
Versions of custom list items are now supported when migrating from Microsoft Office SharePoint Server (MOSS) 2007 to MOSS 2007. Versions of documents in document libraries are also supported. The number of versions to migrate can also be set, so that the last "x" number of versions will migrate.
back to table

Alerts
Alerts may only be copied to MOSS 2007 sites. Site users who have alerts copied over will receive email notification(s) that the copied alert(s) have been created on the target site. We advise that alerts not be copied to lists/libraries that have been modified/created within five minutes of the alert copy. Doing so increases the risk that users will receive unnecessary alert e-mails pertaining to the list modifications made prior to the alert-copy. This feature requires that the latest version of the extension service be running on both the source and target servers. The evaluation version of SharePoint Site Migration Manager cannot migrate alerts.
back to table

Global Navigation
SharePoint Site Migration Manager can copy both the Global Navigation (the top bar navigation) as well as the Quick launch navigation. We recommend copying the navigation after the content has been migrated because, in some instances, areas of the site can have their navigation copied before the rest of the site, resulting in incorrect navigation. Performing the navigation cope after the site copy eliminates this issue. This requires the latest version of the extension service running on both the source and target servers.
back to table

Issue Lists
When copying an Issue list (from a SharePoint 2003 source) that has versioning, the content approval settings for each list item will be set to "Pending," and all approver comments will be retained. If versioning is not turned on for Issue lists (from a SharePoint 2003 source) then the "Approved" and "Pending" status of items will be preserved. However, any "Rejected" items will have their status changed to "Pending." Once Issue lists are copied users won't be able to migrate new or modified items to the list, or append items to it. The Issue list would have to be copied again using the "Overwrite existing lists" option.
back to table

Audiences
Audience settings of SharePoint V2 web parts can be mapped when they are being copied to MOSS 2007. MOSS 2007 audience settings are also mapped.
back to table

Discussion Boards
Discussion boards cannot preserve item ID's during a migration, and as a result incremental copies (or new and updated item copy) cannot be performed. Incremental migrations use the item/document ID field to identify, and match, existing items to be updated, but since SSMM doesn't preserve item ID's for discussion boards, that field cannot be used to update any existing items. If a discussion board is updated, and this update needs to be migrated to the target site or server, the entire discussion board would have to be re-migrated.
back to table

User Created Document Library Views and List Views
Calendar views need to be manually configured.
back to table

Column Mapping
Column mapping is available during item-level copy operations -- other options are coming soon.
back to table

Content Types
SharePoint Site Migration Manager will associate custom content types if they have been created on the target server.
back to table

Custom Site Columns
SharePoint Site Migration Manager does support the copy and creation of custom site columns, but only has this ability at the item level. It is possible to add a column to the Base Columns group with this ability, however, users should be very careful when doing so, as they can be extremely difficult to remove, and these added columns can impact the target server greatly. It is also possible to migrate site column contents, above the item level. However,the custom site columns must first be created on the target server or site, then SSMM can then map and migrate the content of these custom columns.
back to table

Folders
Folders created under MOSS 2007 Custom Lists are now supported. Folder Metadata can also be migrated, but the four main Metadata edit information fields (Created, Created By, Modified, Modified By) will not be preserved unless the Metalogix Extension Service is installed. It is also possible to map columns during a Folder level migration.
back to table

Users
If the SIDs do not match, SharePoint Site Migration Manager will attempt to map by string. Migrating all user information from MOSS 2007 to MOSS 2007 requires having the Metalogix service on both the source and target servers.
back to table

Cross Domain Users
If you want to migrate users across domains without a trust, please contact Metalogix for more information.
back to table

Security Groups
When migrating from SPS 2003 to MOSS 2007, site groups will map to MOSS permissions and cross site groups will map to MOSS security groups. Permission levels can also be migrated, either seperately as a pre-migration step, or as a part of a site or site collection migration.
back to table

MySites
MySite copying requires the Metalogix service on the target and source servers.
back to table

Publishing Sites
Master pages are now supported.
back to table

Multi-tabbed Meeting Workspaces
Migration of custom tabs in multi-tabbed meeting workspaces is supported. SharePoint Site Migration Manager migrates Web Parts on the default tabs.
back to table

Recurring Meeting Workspaces
Recurring meeting workspaces based off of recurring calendar items, must be re-created manually in order to get the left-side date navigation. Content can be migrated over accurately.
back to table

Site Collection Browsing
Source-side site collection browsing is supported if the Metalogix SharePoint Extensions Service is installed and running on the source server.
back to table

Bucket Web Link Correction
This is supported as a site copy option, and works in almost all cases. However, there are a few exceptions (e.g., bucket web links inside content editor web parts).
back to table

Custom Templates
This includes conversion to custom site definitions.
back to table

Template Mapping
SharePoint 2003 custom/default site templates can be mapped to SharePoint 2007 custom/default templates.
back to table

Web Parts
Custom (third-party) Web Part binaries must be installed on the target server prior to migration.
back to table

Web Part View Customizations
SSMM will preserve list view web part views when copying web parts. SharePoint Site Migration Manager cannot preserve view type, but this is a rare case (e.g., with calendar views that are not common).
back to table