OneDrive for Business to OneDrive for Business or OneDrive for Business (Private Cloud) Migration Guide

Introduction

The Source and Destination must be OneDrive for Business - not the personal OneDrive version.

If you are migrating to an Office 365 Small Business Tenant account, the processes will be very similar. However, you will not be able to use admin credentials for your Destination endpoint, and will, instead, be using end user credentials.

Note that OneDrive data may not be accessible for a few days after migration, due to OneDrive's crawling and indexing process. We suggest having your users log in immediately after migration, but warn them that their data may not be available immediately. For this reason, it may be best to complete the migration on a Friday so the indexing can happen over the weekend.

Important: MigrationWiz is not a sync tool. Items updated at the source mid-migration will not be updated at the destination with additional migration passes.

Notes:

  • Due to versioning, storage usage on destination OneDrive may be increased when migrating with permissions.
  • We no longer support migrations to or from GoDaddy hosted OneDrive.

Endpoint Change Notification

Microsoft is changing its connectors. SharePoint and OneDrive v1 destination endpoints will now be heavily throttled. To avoid migration slowdowns, BitTitan is updating the default endpoint to v2 for destination endpoints. BitTitan only supports v1 for source endpoints.

V1 destination endpoints are now only available to private cloud users, and will be displayed as Private Cloud and Private Cloud for SharePoint.

V2 destination endpoints will now be displayed as SharePoint and OneDrive For Business.

If you are currently migrating on v1, complete your migration as soon as possible with the v1 endpoints. Any future migrations, unless you are on private cloud, should utilize the new v2 endpoints. This will prevent you from being throttled during your migration.

This change will only occur in MigrationWiz. MSPComplete will not be changed,

To change your endpoint

Important: If the migration has been started, you must pause it before changing the endpoint. Ensure that all item statuses are set to Stopped or Not Started before following the steps below.

  1. Navigate to your My Projects page

  2. Select Edit Project

  3. Select Destination Settings

  4. Select New

  5. Enter new endpoint name.

  6. Select endpoint type Sharepoint or OneDrive for Business.

  7. Enter administrative credentials.

  8. Select Azure storage requirement. Note: We recommend using your own Azure account for this process. Please review the How do I create an Azure Storage Account? article.

  9. Save Project to commit change.

Preparing the Source

Create an Administrator Account

The easiest approach to follow is to use the global administrator account that was set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This will then need to have a license assigned that includes OneDrive for Business and be granted Site Collection Administrator privileges. 

Important: We strongly recommend that you use an administrator account that isn’t one of the users being migrated, as it can cause issues with missing shared permissions.

Process:

  1. Create a user in Office 365 and assign a license that includes OneDrive for Business. For step by step instructions, see the Microsoft article Add users individually or in bulk to Office 365.
  2. Set the administrator privileges. Grant one of the permission levels listed below. 

After you perform these steps, the specified user will be visible in the Office 365 administrator center. Full provisioning of the user account can take up to 24 hours.

Export Users

Export the list of OneDrive for Business user accounts to a CSV file. This can be used when adding users on the Destination, and when adding the users to the project in MigrationWiz.

Set up the app-based authentication in both the Office 365 tenants

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

Step 1:

Visit the following URL and sign in as the administrator user:

https://login.microsoftonline.com/common/adminconsent?client_id=e7c20566-14a7-4722-acd1-396f7268ea1a&state=12345

Do this for both Source and Destination tenants.

Step 2:

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.  

Preparing the Destination

If you are leveraging a OneDrive V2 destination endpoint follow the 'Prepare Azure Environment' steps below. If you are not using the V2 endpoint, skip this step and navigate to the 'Create an Administrator Account' section. 
Important: While there is an option to use Microsoft-provided Azure storage, we recommend that you use your own Azure storage instead. The security token generated for the Microsoft-provided storage expires after just a couple of days and that expiration will cause the migration to fail.

Prepare Azure Environment

Note: If using Microsoft-provided Azure storage, you can skip this section.

  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==”

Create an Administrator Account

The easiest approach to follow is to use the global administrator account that was set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This new account will then need to have a license assigned that includes OneDrive for Business and be granted either Global Administrator permissions or SharePoint Administrator privileges.

Important: We strongly recommend that you use an administrator account that isn’t one of the users being migrated, as it can cause issues with missing shared permissions.

Process:

  1. Create a user in Office 365 and assign a license that includes OneDrive for Business. For step by step instructions, see the Microsoft article Add users individually or in bulk to Office 365.
  2. Grant the new user Global Administrator permissions or SharePoint Administrator rights in Office 365.
  3. Ensure that the administrator account is set to use Basic authentication rather than Multi-Factor authentication.

After you perform these steps, the specified user will be visible in the Office 365 administrator center. Full provisioning of the user account can take up to 24 hours.

Licensing

Licenses are required to run a migration project in MigrationWiz. To obtain license pricing information, or to purchase licenses, click the Purchase button in the top of your MSPComplete or MigrationWiz dashboard.

Payment: We accept credit cards, and wire transfer in certain situations.  

  • When purchasing with a credit card, payment is immediately processed during checkout. If successful, licenses are granted to your account instantly.
  • Wire transfers are available for purchases of 100 or more licenses. If you are purchasing at least 100 licenses, you will be presented an option to purchase via wire transfer during checkout. A wire transfer checkout will generate an invoice with wiring information for your accounts payable department and bank. Once the funds are received by our system, the licenses are granted to your account immediately. 

For this project type it is recommended to use our User Migration Bundle licenses. 

  • These licenses enable you to perform multiple migrations of User mailboxes, documents, and in-place archives, and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration.
  • Further information on User Migration Bundle Licenses:
    • User Migration Bundle Licenses have unlimited data available per license.
    • User Migration Bundle Licenses are applied to the customer's users, for whom you'll be performing migrations, and are valid for one year.
    • Read Apply User Migration Bundle Licenses to the Customer's Users for more information about how to apply the licenses to Users for migrations.

Create A Document Project

To create a new migration project, follow the steps below.

  1. Sign in to your MigrationWiz account.
  2. Click the Go to My Projects button.
  3. Click the Create Project button.
  4. Click on the type of project that you wish to create.
    1. Document: Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.

      Note: See What items are migrated with MigrationWiz? for a more detailed list of what items are migrated in each migration type.
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select a Source Endpoint from the Endpoint dropdown menu.
    Note:
    1. 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.
  9. Select a Destination Endpoint from the Endpoint dropdown menu.
  10. 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.

Setting Endpoints

  1. When creating the project on your Source Settings or Destination Settings tab, click New.
  2. 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.

Add Items To Project

To add the user accounts (also called "Line Items") that will be migrated into the project using the CSV file created in the Prepare Source section, click "Add" in the menu dashboard and select "Bulk-Add". 

  • NOTE: If you're also running a Mailbox Project for the users that will be migrated here, you can use the "Add from MSPComplete" option. Verify the users are licensed in MSPComplete or in the Mailbox project before adding them.

Important: The users Source and Destination address must be entered as the current username (User Principal Name) for their account in the O365 tenant. Read the Cannot Authenticate article for more information.

 

Run Migration

Set Project Advanced Options. Read the What project Advanced Options are available? article for more information.

  • For non-standard URL endpoints, add OneDriveProExportAdminUrl=<non standard URL> and OneDriveProImportAdminUrl=<non standard URL>. (Replace "<non standard URL>" with your custom URL.) 
  • 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.
    • IncreasePathLengthLimit=1 - Use this Advanced Option in MigrationWiz to enable the use of 400 characters for the file path name. Read the What would I use the Advanced Option IncreasePathLengthLimit=1 for? article for more information.
    • If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information, contact Support.
  • BitTitan has no limitations to the number of folders per migration.  Any folder limits will be set by Microsoft.
    Note: There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.
  • Set the Advanced Option to send a notification to end users after the migration pass completes. (This is optional.)
    • Notifications > Send successful migration and notification to: > Source email address (if users are still using the original Source Office 365 tenant) or Destination email address (if users are already using the Destination Office 365 tenant).
  • Customize notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
    Note: Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-Stage migration strategy, only set this up prior to the final Full (Delta) pass.

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

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click on the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.
  5. Once complete, the results of the verification will be shown in the Status section.

Notify Users

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

  1. Click on the name of the Project you want to run.
  2. 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.
  3. 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.
  4. 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.
  5. Click Start Migration.

Remove the Authentication App

To remove the BitTitan Enterprise app, perform the following steps:

  1. Launch PowerShell.
  2. Connect PowerShell to Office 365.
  3. Enter the command: Connect-AzureAD
  4. Enter the admin credential 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>

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.

 

Post-Migration Steps

  1. To prevent users from inadvertently logging in and using their Source accounts, decommission their Source OneDrive for Business user accounts, or change their passwords.
  2. Notify users once the migration has completed.
    Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion. Assist them with setting up access to their OneDrive for Business accounts, and setting up their synchronization settings.
Was this article helpful?
0 out of 0 found this helpful