Test Drive Metalogix
award-winning products today.

Resources

Click here to learn more about Metalogix products.

Newsletter

Comments

Multiple Adapter Connection Types

Multiple connection types can be made with Migration Manager for SharePoint. Connections can be made to the SharePoint Object Model (OM), to a SharePoint Database (DB), and to the SharePoint Native Web Service (NWS)/SharePoint 2010 Client Object Model. And an additional connection to the server-side OM can be made for remote instances of SharePoint using the Metalogix SharePoint Extensions Web Service. The Extensions Web Service can be deployed, as a SharePoint solution file, and can be installed on any WSS 3.0, MOSS 2007, SharePoint Foundation 2010, or SharePoint Server 2010 installation. It has also gone through Microsoft's extensive testing and has been certified to be installed on Dedicated versions of BPOS (BPOS-D) or Office 365 dedicated, by request.

MySites

MySites can be copied from a SharePoint server connection to another SharePoint server connection. User Profiles can be migrated with MySites and compiled into audiences. The web application and managed path can both be set as a part of a MySite migration.

Wikis

Wiki site in MOSS 2007 can be migrated into the new Wiki template (Enterprise Wikis) for SharePoint 2010.

Versions

Versions for SharePoint Lists and Document Libraries can be migrated using Migration Manager for SharePoint. Users can also set the migration so that only the last "X" number of versions will be copied to the target.

Workflows

Workflows (including SharePoint Designer workflows) can be migrated with Migration Manager for SharePoint.

Migration Logging

Migration Manager for SharePoint provides comprehensive logging for migration actions. A log file will be created and stored for each migration action, and can be viewed at any time, even during the migration itself. These logs will give a breakdown of all actions that took place during a migration. This data can also be copied and exported into other applications on the system.

Master Pages

Migration Manager for SharePoint has the ability to copy the Master Page Gallery from one SharePoint site to another. In order to enable this feature an Object Model (OM) connection or Native Web Service (NSW) connection can be used on the target machine.

Web Parts

Migration Manager for SharePoint has the ability to migrate web parts from one SharePoint instance to another. In order for web parts to be correctly migrated they must first exist on the target server, so if any third part web parts are used, then they need to be installed on the target before migration. Migration Manager for SharePoint can migrate web parts for landing pages (default.aspx pages), web part pages, and publishing content pages.

Alert Copying

Migration Manager for SharePoint can migrate Alerts, however, we can only migrate alerts through an Object Model (OM) connection. For best results, alerts can be migrated separately, after the site, lists, or items, have been migrated. This is to prevent unnecessary emails being sent to users.

Navigation (Global and Quick-Launch)

Migration Manager for SharePoint can migrate the global and quick-launch setting of a SharePoint site, but not the actual node structure of the SharePoint site. This means that if the SharePoint navigation structure has been modified (and does not inherit from the parent site) then Migration Manager for SharePoint will not be able to preserve these navigation changes. This feature is still being reviewed for further development.

Views

Migration Manager for SharePoint has the ability to migrate SharePoint list/library views and web part views. Personal views are not available through the SharePoint API, so we do not copy them.

Audience Copying

Migration Manager for SharePoint has the ability to migrate SharePoint list/library views and web part views. Personal views are not available through the SharePoint API, so we do not copy them.

Incremental Migration

Migration Manager for SharePoint has the ability to do incremental migrations. Incremental migration actions are created from existing migration logs (log files). Any selectable migration setting can be re-configured for the incremental copy. It is recommended that Item ID's be preserved when running an incremental migration. If the Native Web Service (NWS) connection type is used on the target side, then Migration Manager for SharePoint will not be able to preserve Item IDs, so changes made will be appended as new items within lists. In this case, Document Libraries will be fine as Migration Manager for SharePoint uses the document metadata for determining what to copy and update.

Preserving Document/Item IDs

List item ID's can be preserved as a part of a migration. For information on preserving document ID's, please contact Metalogix Support. 

Using Migration Manager for SharePoint with PowerShell

Migration Manager for SharePoint has the ability to use PowerShell to run migration. There are two snap-ins that come packaged with Migration Manager for SharePoint, which allow the application to work with PowerShell. By default the Migration Manager for SharePoint installer will also install a PowerShell icon on the desktop that already has these plug-ins and snap-ins configured, so PowerShell is ready to be used in conjunction with Migration Manager for SharePoint. Additionally Migration Manager for SharePoint can generate PowerShell script for any existing log or batch file within Migration Manager for SharePoint's Job List section. The ability to use PowerShell with Migration Manager for SharePoint gives the application a much greater range of flexibility as users can create their own custom migration scripts.

Permissions Migration

Permissions for SharePoint sites, list, folder, and items can be migrated using Migration Manager for SharePoint. When dealing with any custom permission levels, these permissions must first be created on the target, in order for them to be migrated correctly.

Role Mappings

Role Mappings, or permission level mappings, can be edited when migrating with Migration Manager for SharePoint, and this mapping can be set conditionally. For example, the "Full Control" permission can be mapped to the "Administrator" permission for any lists that start with the name "Project."

Copying of Deleted Active Directory Users

In the case of migrating users that no longer exist in the source/target Active Directory (AD), Migration Manager does have a workaround method that can be used. This case is generally encountered for any users that have left an organization, and the host organization still wants to preserve their metadata. For more information on this feature, please contact Metalogix Support.

Ghosted/Un-Ghosted Pages

Migration Manager for SharePoint has the ability to migrate both ghosted and un-ghosted pages. This action is done mainly behind the scenes, with the exception of one option that allows for any pages within the scope of a migration to become ghosted. When migrated, ghosted pages will stay ghosted, and un-ghosted pages can either stay un-ghosted or become ghosted, depending on the circumstances.

Content Types

Content type can be copied as a part of any site or site collection level migration, and can also be copied as a separate action. All of the content types within the scope of the migration will be migrated.

Column Mapping

Column Mappings can be set during a migration, however, this option is available when migrating items between two lists. This is most likely to be done when running an incremental migration. Any columns existing between the source and target list can be mapped to each other, including any site or list columns. new columns can also be created, and mapped to, on the target side.

Auto-Mapping Metadata (Authorship fields)

When migrating to a remote SharePoint connection (when the Migration Manager for SharePoint application, or the Extensions Web Service is not installed) Migration Manager for SharePoint has the ability to copy and migrate the four main Authorship columns (Created, Created By, Modified, Modified By). These four fields are copied into four other metadata columns, and then migrated to the target remote SharePoint instance.

Link Correction

Links for content within the scope of the migration will be corrected, but only site, list, page, and web part links will be corrected. Links within documents will not be corrected.