logo banner

Metalogix Content Matrix Console - SharePoint Edition has the ability to copy MySites between SharePoint servers. Migration of folders and files in the Shared with me and Shared with everyone folders is supported, including all related permissions. The following are the supported source/target combinations for migrating MySites:

Note: When migrating SharePoint MySites to a SharePoint 2013 or 2016 target, a Local OM or a Remote OM connection can be used. However, due to some User authentication changes that were made in SharePoint 2013 that inadvertently restrict the creation of Site Collections (MySites are a type of Site Collection) using the SharePoint OM remotely, Content Matrix needs to use a set of elevated permissions to create Site Collections. In order for these elevated permissions to be used, the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on. A preliminary check will be made before elevation occurs to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. Creating Site Collections for a SharePoint 2013 or 2016 target with the Local OM connection type does not have this same restriction, but the same permissions are recommended in case elevated permissions are needed. Please see the Connecting to SharePoint page for more details on this connection types. For more information on this specific issue, please see the SharePoint 2013 and 2016 Site Collection Creation Issue page.

This same issue, for requiring elevated permissions, can be encountered in SharePoint 2010 environments if they are using Claims authentication.

Note that in order to view MySites when migrating to an Office 365 Tenant environment, the Include Office 365 tenant my site host connection checkbox must be enabled when the connection is created. The MySites are then displayed under their own top-level root node. For more information, please see Connecting to SharePoint O365 Tenant.

On this page:

Required Permissions for Migrating MySites

Migrating MySites requires slightly higher permissions than other copy actions. The basic permissions needed to migrate MySites are as follows:

These basic permissions allow for the creation and migration of MySites (personal sites) on the target, use of personal features, management of user profiles, and management of permissions (these can all be accessed through the Shared Services Provider (SSP) in Central Administration).

These permissions will also allow for any default or custom User Profiles to be migrated with the MySites. User profiles can later be converted into audiences. When migrating MySites, any custom User Profile properties will only be migrated if the following conditions are met:

Note: When migrating User Profiles to an Office 365 Tenant target, there are the following limitations:

Additional permissions may be required depending on the target connection type. In cases where users are connected using the Local OM connection they would also require: Farm Administrator, and Read/Write access to the content Database (DB). These are all standard permissions in order to migrate general content using Content Matrix Console - SharePoint Edition. Alternately, if a Remote OM connection is being used for the target through the use of the Metalogix Extensions Web Service, then any additional permissions that would be required will already be set using the Extensions Web Service.

Setting Permissions in Shared Services

Setting permissions in Shared Services is one of the most common issues when migrating MySites. These permissions must be set to correctly copy MySites, and they are not enabled by default, even if the migrating user is set with "Full Control" permissions over the web application.

Setting Shared Services Permissions in SharePoint 2007 (MOSS)

  1. Navigate to the MOSS environment's Central Administration.

  2. Select the SharedServices1 link under the Shared Services Administration link in the left-hand quick launch navigation instead (provided this has not been changed from the default). In MOSS 2007, this is the best way to reach the required page.

  3. Next, select the Personalization services permissions option under the User Profiles and MySites heading.

  4. If the user account is not already listed, Add them. Give the user account the Manage user profiles permission.

  5. Click Save to finish.

Setting Shared Services Permissions in SharePoint 2010

SharePoint 2010 does not use the same Shared Services Provider (SSP) that SharePoint 2007 uses. Instead, it uses the User Profile Service.

  1. Navigate to SharePoint 2010's Central Administration.

  2. Select Application Management and go to Manage service applications under the Service Applications heading.

  3. Highlight the User Profile Service Application line to open the Ribbon menu. Select the Administrators button in the ribbon to open the Administrators for User Profile Service Application dialog.

  4. If the user account is not already listed, Add them. Give the user account the Manage Profiles permission from the list. This user account only needs the Manage Profiles permissions, and does not need Full Control.

  5. When finished, add any other required user accounts and/or permissions and click OK to finish.

Migrating MySites

When migrating MySites, the target side connection must be a Web App or Farm connection type, using the Local or Extensions Web Service connections for on premise installations of SharePoint. For Office 365 target environments, the Office 365 Tenant connection type must be used.

It is recommended that the "Web App" or "Farm" connection types be used on the source side as well. Other connection types can be used on the source, such as the Database connection. However, this will have some limitations. If these other connection types are used on the source, MySites can still be migrated to the target, but they will be migrated as Site Collections (not using the MySite template), and as a result, will not include some of the User Profile data and other data that the normal MySite migration will preserve.

Note: When migrating MySites into a target SharePoint 2013 or 2016 environment that uses OneDrive/SkyDrive, Content Matrix will use a slightly different method to migrate some of the content. Any documents on the source that are in the MySite Shared Documents or Personal Documents library will be migrated into a Shared with Everyone folder in OneDrive/SkyDrive. This is done instead of migrating the documents into Document Libraries of the same name. As a result, this can cause some navigation copy issues because the Shared and Personal document libraries will not exist on the target, and because they do not exist, they cannot be added to the navigation.
Additionally, web parts that exist on landing pages in SharePoint 2007/2010 will not be migrated to SharePoint 2013 or 2016.
  1. In the Explorer View tab, navigate to the source server ("Farm" or "Web app") connection that you want to copy MySites from.

  2. Select the server node, right-click it, and click Copy MySites.

  3. Navigate to the desired target server connection node and select it. Right-click the node and then click Paste MySites followed by the desired MySite copy type:

    • Paste MySites (Admin Mode) - This mode is the standard MySite copy mode and requires the set of migration permissions described above (at the top of the page). This will migrate any selected MySites, including any User Profiles and other content (documents, images, etc.) that exists on the selected MySite.

      This is the only option that is available when migrating into an O365 environment, using the Office 365 Tenant connection type.

    • Paste MySites (Self Service Mode) - This mode is for use with the "Self Service" feature that is available in 2007 and 2010 versions of SharePoint. The Self Service mode allows for MySites to be created, even if the user does not have the set of migration permissions as described above (at the top of the page) on the target. In order for this option to work there are two conditions that must be met. The first is that the "Self Service" feature must first be enabled on the target side, and the second is that that target connection must be made to the MySite host site address using a Web App connection type (please see the Connect to SharePoint page for more details on the Web App setting).

      This option is not available for the MySite Options tab when migrating to Office 365 Tenant environments.

      Note: To activate this feature in SharePoint 2007, go to Central Administration > Application Management > Application Security > Self Service Site Manager and ensure that the option is set to On.
      To activate this feature in SharePoint 2010, go to Central Administration > Application Management > Manage Web Applications, select the desired web application, and then select the Self-Service Site Creation option in the ribbon. Ensure that the option is set to On.

      This feature is most commonly used when migrating to Microsoft Online (Business Online Productivity Suite) or to Office 365 and is set to "On" by default.

    Once the mode is selected, the Configure Site Copying Options dialog box appears and the desired MySite options can be selected.

  4. The Configure Site Copying Options dialog box appears. The MySite Options tab can be used to determine the MySite set-up options.

    Note: The Available MySites section of the MySite Options tab will only display MySite Site Collections that are using a MySite template (such as SPSPERS#0) and that the current user account has access to. Any MySites that do not meet these requirements will not be displayed. It is also possible that a MySite might not appear because it has run into a timeout issue, but if a Refresh is done for the server, the MySite may then be displayed.
  5. Set all the MySite Options as desired.

  6. Select any other desired migration options. Click Run when ready to start the migration.

    Alternatively, click Save to save the copy settings to a job file in SharePoint Edition's Job List section. From here, the job can be run at a later time.

    Note: Because language packs are not included in the migration action, the base language setting of the MySite being migrated must already be installed on the target environment. If it is not, an error message containing the language code of the missing language pack will be displayed.
  7. When the migration starts, a status dialog box will appear. The migration logs can be viewed (in progress or after the migration is finished) by clicking Details>>. The Status section of the status box will list a live count for the number of successes, warnings, failures, etc. for the migration. The Progress section of this dialog will list any completions and the type of completion (Sites, lists, items, users, groups, etc.). A Migration Completed message will appear when finished. Click Close to exit the status dialog.

MySite Migration Options

This section will review the available options in the MySite Options tab. These options are only available when migrating MySites.