SharePoint to SharePoint Migration Guide

Introduction

This article outlines the complete workflow for the SharePoint to SharePoint. This migration type requires an Azure subscription, which it leverages to maximize speed and bypass throttling. This migration does not require licenses. Follow the steps below to prepare for your migration. Once you have completed these steps, you are ready to begin your migration.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

Note: Due to versioning, storage usage on SharePoint may be increased when migrating with permissions.

We are not able to support migrations with 2-factor or multifactor authentication. 

 

Preparing the Source

Save library templates. This step is only required if you want to apply templates from your Source libraries onto your Destination libraries. 

Important: the v2 connectors do not support invalid XML characters.  The list of sites will need to be checked for these characters and sites with invalid characters will either need to be renamed or migrated using a v1 connection instead of v2. The invalid characters are: < > " ' &

Enable App-Based Authentication

These are the steps to enable permission level at the source only. This authentication process gives you control over who is entitled to use the source.

  1. Ensure you are signed in as a Global Admin.
  2. Go to either MigrationWiz-SharePoint-ReadOnly or to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
  3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal. 
  4. Create new user.
  5. Add new user to previously created security group as a member.
  6. Create MigrationWiz project.
  7. When creating the endpoints, enter the new user credentials.
  8. Add support option UseApplicationPermission=1

Steps to remove these permissions are provided below in the Post-Migration section.  

Prepare Azure Environment

Note: If using Microsoft-provided Azure storage, you can skip this section. It is highly recommended to use your own Azure storage if the total amount of data being migrated for your project is more then 5 GB.

  1. Estimate Azure storage costs. This step is optional but is useful in order to provide the customer with upfront storage costs ahead of time. For more information, see Estimate Azure Storage costs for migrations.
  2. Buy an Azure subscription (or use the free one-month trial, and be aware that this option is only viable if you are performing a very small migration). For more information, see How do I buy an Azure subscription?
  3. See How do I create an Azure Storage Account​?to create your storage account.  You will need to set up a STORAGE (General Purpose v1 or v2) account rather than a storage blob. Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the Destination settings. We recommend that you create your Azure storage account in the same Microsoft data center as the Destination Office 365 tenant. There is no need to create any Azure containers for this migration.

Note: The access key information that is needed are these:

  • -accesskey – This is the Storage account name for the Blob – example “accountname”
  • -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”

 Prepare Destination Environment

  1. Create a SharePoint Online administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. More information about these can be found here.
  2. Create SharePoint site libraries and schema.
    Note: Make a note of the site URL where the document libraries are stored. This will be entered when creating your MSPComplete Destination endpoint.
  3. Create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint site, before beginning the migration project.
    Note: Refer to this Microsoft training video for more information on the steps: Create your document library.
  4. Set up the app-based authentication in the Office 365 tenant. 
    1. Ensure you are signed in as a Global Admin.
    2. Go to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
    3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal.
    4. Create new user.
    5. Add new user to previously created security group as a member.
    6. Create MigrationWiz project.
    7. When creating the endpoints, enter the new user credentials.
  5. Optional: Apply the Source library templates to your Destination libraries. This step is only required if you want to maintain the same look, feel, and design of your Source libraries on your Destination.

MSPComplete Steps

  1. Create the customer. For more information see View, Add, and Edit Your Customers
  2. Create the Source and Destination endpoints. For more information see View, Add, and Edit Customer Endpoints

    • For the Source endpoint:
      • Click EndpointsAdd Endpoint > Enter endpoint name > For endpoint type, select SharePoint.
      • Enter the URL for the top-level SharePoint site or sub-site. For more information on finding the URL for the SharePoint library, see How do I find the URL for my SharePoint Library or OneDrive for Business?
      • Enter the administrator username and password in the fields.
        Note:This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
    • For the Destination endpoint:
      • Click EndpointsAdd Endpoint > Enter endpoint name > For endpoint type, select SharePoint v2.
      • Enter the URL for the top-level SharePoint site or sub-site. For more information on finding the URL for the SharePoint library, see How do I find the URL for my SharePoint Library or OneDrive for Business?
      • Enter the administrator username and password in the proper fields.
      • Enter the Azure Storage Account Name and Azure Access Key or select Microsoft provided Azure Storage.
        Note:This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account

MigrationWiz Steps

  • Create the Document Migration project. Read the How do I create a new migration project?article for more information.
  • Add the Document Libraries that will be migrated to the project. For more information see How do I add items to my migration project?​​
    Notes:
    • This does not require the whole URL, just the name of the library. The name that needs to be entered under the library field for both Source and Destination will be the text that is at the end of the site URLs.
    • This field is case-sensitive.
    • This may be different than the actual name that has been set for the Document Library. The examples below help explain this:

      • If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.
      • If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/Shared Documents/", then the name of the document library that needs to be entered is Shared Documents. for more details.
      • See Finding SharePoint URL and Document Library for Migration for more details.
    • Note: ‘/' characters are not supported in the destination library name. Attempting to migrate any destination library with a '/' character will result in a migration failure.
  • Set the Project Advanced Options.
    • Under Support/Support Options add:
      • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. Read the Cannot get folders from My Drive article for more information.

Post-Migration Steps

  • Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. For more information see How do I request statistics for my migration project?
  • To prevent users from inadvertently using the Source SharePoint libraries, decommission the Source SharePoint server, libraries, or user accounts.
  • Delete all the Azure containers used for this migration. This will prevent incurring post-migration Azure costs for these containers. Be careful to only delete the containers created for this migration.

Remove App Permissions

  1. Remove the newly created user.

  2. Remove the MigrationWiz Security Group created in Step 3. 

  3. To remove the app from the source or destination, perform the following steps:

    1. Launch PowerShell.
    2. Connect PowerShell to Office 365.
    3. Enter the command: Connect-AzureAD
    4. Enter the admin credentials in the prompt.
    5. Enter the command:Get-AzureADServicePrincipal -SearchString Migration
    6. Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id>
Was this article helpful?
0 out of 5 found this helpful