This is the complete workflow for the SharePoint to SharePoint Migration Strategy Guide. This migration does not require licenses.
What is migrated in this scenario?
Document libraries and permissions are migrated; site logos and customization, task lists, custom tasks, newsfeeds, metadata, and versioning are not.
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
Set up the app-based authentication in the Office 365 tenant. BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Office 365 Groups (Documents) migrations, and Teams migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Office 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Office 365 tenants.
Important: This app must be added in both .microsoftonline.com tenants (Source and Destination) to reduce the throttling and failures due to Microsoft throttling policy changes.
If this app is not added on both tenants, MigrationWiz will attempt to create a temporary substitute app in the tenants to be used for authentication. We do not recommend relying on this substitute app creation, as this behavior will only be a temporary transitional behavior within MigrationWiz. To avoid potential interruptions or failures in migrations, it is strongly recommended to set the app up in the tenants.
Add the App to the tenant
Visit the following URL and sign in as the administrator user:
Do this for both Source and Destination tenants.
Authorize the App for both Source and Destination tenants.
Click on the Accept button.
Steps to remove these permissions are provided below in the Post-Migration section.
Prepare Destination Environment
- 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.
- 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.
- Create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint Online site, before beginning the migration project.
Note: Refer to this Microsoft training video for more information on the steps: Create your document library.
- Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.
- Optional: Apply the Source library templates to your Destination libraries.
Note: This step is only required if you want to maintain the same look, feel, and design of your Source libraries on your Destination.
Create A Project
To create a new migration project, follow the steps below.
- Sign in to your MigrationWiz account.
- Click the Go to My Projects button.
- Click the Create Project button.
- Click Document.
- Click Next Step.
- Enter a Project name and select a Customer.
- Click Next Step.
- Select a Source Endpoint from the Endpoint dropdown menu.
- If you are migrating from a Hosted Exchange provider, click the I know my service provider button. Select your service provider from the drop-down list. If it is not listed, select Exchange 2003+ as your Source and enter your OWA URL.
- Select a Destination Endpoint from the Endpoint dropdown menu.
- Click Save and Go to Summary.
Note: If setting up a Tenant to Tenant Coexistence mailbox project, check the box for Enable Tenant to Tenant Coexistence. Otherwise, leave that box unchecked.
- When creating the project on your Source Settings or Destination Settings tab, click New.
- Fill in the fields below. Once endpoint has been saved in the project, it will automatically be assigned to the customer that was selected in the Project Information tab when creating the project.
- Name: Type any name you want for the endpoint.
- Find My Service Provider: Use this control only if the endpoint you’re creating is hosted by a service provider and not a local endpoint. If you don’t know your server type, click this button and then click your provider in the drop-down list.
- Endpoint Type: Click the Endpoint Type drop-down, and then click the appropriate endpoint type in the list. Ensure you have selected the correct source and destination. When you select an endpoint type, the form will expand so that you can provide additional connection information and credentials for that endpoint type. These additional fields vary depending on the endpoint type.
- If an endpoint does not exist for the service that you want to connect to with MigrationWiz, then use the Generic endpoint type to generically store the web address for that service, a username, and password. This endpoint can still be used for Runbook execution.
- Provide credentials: Select Provide Credentials or Do Not Provide Credentials as needed.
- If you select Provide credentials, the form expands to present more fields for username and password. The credentials will be used by MigrationWiz to access the service selected. In most cases, you must provide credentials for an administrator account on those services, as this will enable MigrationWiz to have full access to the cloud service.
- If you select Do not provide credentials, then MigrationWiz will request credentials from end users before a migration can be started, or before a Runbook can be completed. This may slow your migration, as you are now dependent on the end users to provide these credentials.
- Domains: For migrations using G Suite Endpoints, this is the list of domains that you will be migrating to, or migrating from. This is not relevant to any other migration environment.
- Use SSL: For some endpoint types, there is an SSL check box at the bottom of the form. Select this check box if you want to secure your new endpoint with Secure Sockets Layer (SSL).
- Note that IMAP and POP endpoints include an SSL option (check box): If your provider uses SSL, you should select this check box and enter the SSL port number in the field provided. For IMAP endpoints, the default port number for SSL is 993. For POP endpoints, the default port number for SSL is 995.
- If your provider does not use SSL, do not select this check box, and enter the non-SSL port number in the field provided. For IMAP endpoints, the default port number for non-SSL is 143. For POP endpoints, the default port number for non-SSL is 110.
- Set a required Advanced Option.
- In the Advanced Options add the following to the Support Options:
Note: This is not supported when using On-Premises SharePoint as the source. This is required for SharePoint Online and requires the administrator account to be a Site Administrator or better.
- In the Advanced Options add the following to the Support Options:
- Add the accounts (items) that will be migrated to the project.
- 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/sites/SiteName/Documents/", enter Documents as the document library name.
- If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/sites/SiteName/Shared%Documents/", then the name of the document library that needs to be entered is Shared Documents.
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.
The following sections will guide you through setting up and launching your migration. Each header is one step, with its component steps below. Follow these steps in order, and read the notes for important information about dependencies or best practices.
Run Verify Credentials
- Open the Project containing items you wish to validate.
- Select the items you wish to validate.
- Click on the Start button in your dashboard.
- Select Verify Credentials from the drop-down list.
- Once complete, the results of the verification will be shown in the Status section.
Send out the final notification that the migration is beginning. Include when the migration will start, expected duration, any usage instructions during migration, and any expected steps or notifications for the post-migration timeline. Remind them to avoid modifying any documents at the Source, as this may cause corrupt data or and incomplete migration.
Perform the Migration
Perform the migration, using one of the following strategies:
- Full Migration strategy – Recommended for projects with fewer than 50 users:
- For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
- Pre-Stage Migration Strategy – Recommended for projects with more than 50 users
- Pre-Stage pass.
- Full (Delta) pass.
Launch the Migration
- Click on the name of the Project you want to run.
- Select one or more items to migrate by checking the box next to the item name.
Note: If you want to select all the items, click the checkbox to the left of Source Email.
- Click on the Start button and select the type of migration to run.
- Full - This migration selection will migrate all identified and supported items.
- Pre-Stage - This migration selection will migrate all identified and supported items before the selected date.
- Trial - This migration selection is used to test the migration server. It will migrate up to 10 items per folder or up to 5 MB of data per mailbox. A full migration will pick up where the trial left off.
- Verify Credentials - This migration selection will test to make sure that the credentials being used for migration are correct and will allow a successful connection. No data is migrated.
- Retry Errors - Free migration pass. Once a Full or Pre-Stage migration has completed successfully, Retry Errors can be run to retry only failed items.
- If you want to delay your migration, then select the checkbox marked "Automatically start the migration at", and enter the date and time to have the migration start.
Note: To start a migration immediately, you do not need to select the scheduling option.
- Click Start Migration.
Remove the Authentication App
To remove the BitTitan Enterprise app, perform the following steps:
- Launch PowerShell.
- Connect PowerShell to Office 365.
- Enter the command: Connect-AzureAD
- Enter the admin credential in the prompt.
- Enter the command: Get-AzureADServicePrincipal -SearchString Migration
- Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id>
- Click the bar 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.